Database Info

[Q] Brickety Brick

I couldn't leave well enough alone and I f'd up somehow trying to flash my pad to 4.2 stock from Cyanogen with TWRP. Now booting thru vol- and power brings up TWRP only. It asks me for a password, which it never has before. I hit cancel and it puts me into home screen. Only ray of hope I see is that ADB still recognizes it and interacts with it. I've tried pushing every ROM I can get my mitts on to the pad. When I try and install it fails after a few seconds. Then the files I just pushed are no longer on /sdcard. I don't have a clue.
Anyone, anyone? Bueller, Bueller...

dedalus2k said:
I couldn't leave well enough alone and I f'd up somehow trying to flash my pad to 4.2 stock from Cyanogen with TWRP. Now booting thru vol- and power brings up TWRP only. It asks me for a password, which it never has before. I hit cancel and it puts me into home screen. Only ray of hope I see is that ADB still recognizes it and interacts with it. I've tried pushing every ROM I can get my mitts on to the pad. When I try and install it fails after a few seconds. Then the files I just pushed are no longer on /sdcard. I don't have a clue.
Anyone, anyone? Bueller, Bueller...
Click to expand...
Click to collapse
Make sure you have flashed the correct version of TWRP. as there are three different versions on their website. If you are confident you have flashed correct TWRP version then you may need to downgrade to the previous version of TWRP. I had a similar issue I downgraded to 2.4.4.0 JB build. Hope this helps

"...you may need to downgrade to the previous version of TWRP."
I can't get into fastboot to install an earlier version. I think I'm screwed.
Theoretically I could use TWRP to totally wipe the pad and then ADB to push the system files back on, but... I don't have that kind of tech knowledge and I doubt anyone who doesn't work for ASUS does.
Edit: My mistake. You can use ADB to install TWRP. I'll give it a shot, though I'm pretty damn sure it's a long one.

dedalus2k said:
"...you may need to downgrade to the previous version of TWRP."
I can't get into fastboot to install an earlier version. I think I'm screwed.
Theoretically I could use TWRP to totally wipe the pad and then ADB to push the system files back on, but... I don't have that kind of tech knowledge and I doubt anyone who doesn't work for ASUS does.
Edit: My mistake. You can use ADB to install TWRP. I'll give it a shot, though I'm pretty damn sure it's a long one.
Click to expand...
Click to collapse
Hey dude just thought I make it easier to understand if you have 3 icons then you will pre load into fastboot if you have four icons then you will have to load fastboot. Lemme know if you run into problems. Happy to help mate.

anaschillin said:
Hey dude just thought I make it easier to understand if you have 3 icons then you will pre load into fastboot if you have four icons then you will have to load fastboot. Lemme know if you run into problems. Happy to help mate.
Click to expand...
Click to collapse
I don't get three or four icons. It boots directly into TWRP. ADB still recognizes the pad and I can still push files to /sdcard. I tried reflashing the ROM but it fails after just a couple seconds, shuts down and boots back into TWRP.
I'm going to get a flashcard reader today and format my external card FAT32 and see if I can't install a new ROM from that.

im in a different situation
i did a erase system in fastboot
now i can only go to fastboot with preload on it
or
apx
is there any wait i can fix it and bring it back to live

Update: Bought a card reader at local Discount Electronics. Plugged it into my PC and it promptly froze my computer and destroyed my $80 64G sd card. Can't catch a break here. So I need to get another card and reader before I can attempt to install rom from external card.
The card reader is by a company called Zeikos. http://www.amazon.com/electronics/dp/B001T9N0R6 You have been warned.

Sheena0220 said:
im in a different situation
i did a erase system in fastboot
now i can only go to fastboot with preload on it
or
apx
is there any wait i can fix it and bring it back to live
Click to expand...
Click to collapse
Can you flash a recovery...
if you manage to flash a recovery run the command: fastboot reboot recovery.

dedalus2k said:
I don't get three or four icons. It boots directly into TWRP. ADB still recognizes the pad and I can still push files to /sdcard. I tried reflashing the ROM but it fails after just a couple seconds, shuts down and boots back into TWRP.
I'm going to get a flashcard reader today and format my external card FAT32 and see if I can't install a new ROM from that.
Click to expand...
Click to collapse
adb reboot bootloader
or
fastboot -i 0x0B05 reboot-bootloader
or
from android terminal - you must be rooted for this to work
su
reboot bootloader

tobdaryl said:
adb reboot bootloader
or
fastboot -i 0x0B05 reboot-bootloader
or
from android terminal - you must be rooted for this to work
su
reboot bootloader
Click to expand...
Click to collapse
I'll give the first one a shot. I can't get into fastboot mode and the su command comes up an error even though I am rooted or was. I really can't figure out where it all went haywire.

YES! I'm in!
tobdaryl said:
adb reboot bootloader
or
fastboot -i 0x0B05 reboot-bootloader
or
from android terminal - you must be rooted for this to work
su
reboot bootloader
Click to expand...
Click to collapse
You are a god amongst men! Thank you sooooo much. If you don't mind...now what?
I get the following messages:
Key driver not found..Booting OS
Android cardhu-user bootloader <1.00e> released by "WW_epad-10.6.1.15.3-20130416" A03
Starting Fastboot USB download protocol
and then the three icons, RCK android and Wipe Data.
After this mishap I don't trust myself to weed through the mountains of info here again. I'm trying to reinstall 4.2.1 and keep it rooted. I'm assuming reinstall 4.2.1 and then reroot, yes? Would you mind terribly pointing me to a reliable post I can follow.
Thank You so much!!!

dedalus2k said:
You are a god amongst men! Thank you sooooo much. If you don't mind...now what?
I get the following messages:
Key driver not found..Booting OS
Android cardhu-user bootloader <1.00e> released by "WW_epad-10.6.1.15.3-20130416" A03
Starting Fastboot USB download protocol
and then the three icons, RCK android and Wipe Data.
After this mishap I don't trust myself to weed through the mountains of info here again. I'm trying to reinstall 4.2.1 and keep it rooted. I'm assuming reinstall 4.2.1 and then reroot, yes? Would you mind terribly pointing me to a reliable post I can follow.
Thank You so much!!!
Click to expand...
Click to collapse
You will have to reroot but with motochopper that is minor.
Unzip 10.6.1.15.3 till you have a blob file. Place the blob in the directory with fastboot.
Reboot into bootloader and wait for fastboot to start. (watch the upper left of the screen)
fastboot -i 0x0B05 flash system blob - wait for the flash to finish then
fastboot -i 0x0B05 reboot
Good Luck!

tobdaryl said:
You will have to reroot but with motochopper that is minor.
Unzip 10.6.1.15.3 till you have a blob file. Place the blob in the directory with fastboot.
Reboot into bootloader and wait for fastboot to start. (watch the upper left of the screen)
fastboot -i 0x0B05 flash system blob - wait for the flash to finish then
fastboot -i 0x0B05 reboot
Good Luck!
Click to expand...
Click to collapse
Grazie Mille! Gonna give it a go right now.
Should I bother with TWRP? I tried to update it before and that's the point it went to hell last time.

tobdaryl said:
You will have to reroot but with motochopper that is minor.
Unzip 10.6.1.15.3 till you have a blob file. Place the blob in the directory with fastboot.
Reboot into bootloader and wait for fastboot to start. (watch the upper left of the screen)
fastboot -i 0x0B05 flash system blob - wait for the flash to finish then
fastboot -i 0x0B05 reboot
Good Luck!
Click to expand...
Click to collapse
Okay. I did it. No joy.
erasing 'system'...
OKAY [2.544s]
sending 'system' <800927 KB>
OKAY [136.994s]
writing 'system'...
OKAY [3.151s]
finished. total time 142.707s
fire off the reboot command
rebooting...
finished. total time 0.551s
But the tab doesn't reboot. And that short "writing 'system'" time to me sounds mighty suspicious
Any ideas? I'm afraid to force reboot it.

dedalus2k said:
Okay. I did it. No joy.
erasing 'system'...
OKAY [2.544s]
sending 'system' <800927 KB>
OKAY [136.994s]
writing 'system'...
OKAY [3.151s]
finished. total time 142.707s
fire off the reboot command
rebooting...
finished. total time 0.551s
But the tab doesn't reboot. And that short "writing 'system'" time to me sounds mighty suspicious
Any ideas? I'm afraid to force reboot it.
Click to expand...
Click to collapse
Reboot into the bootloader. If you get into the bootloader cold boot - volume down on the first icon.
If your tablet fails to boot into android go back to the bootloader and reboot into recovery.
I'll wait for your response.

tobdaryl said:
Reboot into the bootloader. If you get into the bootloader cold boot - volume down on the first icon.
If your tablet fails to boot into android go back to the bootloader and reboot into recovery.
I'll wait for your response.
Click to expand...
Click to collapse
Done and no luck

dedalus2k said:
Done and no luck
Click to expand...
Click to collapse
No recovery either?
What happens in both cases - please explain.

tobdaryl said:
No recovery either?
What happens in both cases - please explain.
Click to expand...
Click to collapse
From off state it always boots into TWRP. I stupidly installed an older version on accident. 2.2.2
With your help I was able to boot into fastboot with the adb command. I've run installs of both the ROM and tried an update to TWRP. According to the console everything went fine but when I give it the reboot command nothing happens. Somewhere in there it looses connections with the tablet it seems.

dedalus2k said:
From off state it always boots into TWRP. I stupidly installed an older version on accident. 2.2.2
With your help I was able to boot into fastboot with the adb command. I've run installs of both the ROM and tried an update to TWRP. According to the console everything went fine but when I give it the reboot command nothing happens. Somewhere in there it looses connections with the tablet it seems.
Click to expand...
Click to collapse
Please explain what happens now. Can you get into the bootloader, recovery, etc?
If you get into the bootloader what happens when you cold boot?
When you boot now without any intervention does it still boot twrp?

tobdaryl said:
Please explain what happens now. Can you get into the bootloader, recovery, etc?
If you get into the bootloader what happens when you cold boot?
When you boot now without any intervention does it still boot twrp?
Click to expand...
Click to collapse
Excuse my noobishness.
I can get into bootloader with the adb reboot bootloader command you gave me
When I go to recovery, RCK right?, it freezes up.
From cold boot it goes directly into TWRP, which asks for a password which it hasn't ever before this mishap.
If I go to android from bootloader and it goes to TWRP as well

Soft bricked shield tablet PLEASE HELP!

So I bought my shield tablet back in March, used it until about may I think. Was browsing the internet then it suddenly crashed and got stuck on the Nvidia boot screen. tried to reboot several times. Nothing. So I forgot about it and thought I would just google the reset option later when I had time. Now since June I have tried everything! From factory reset to fast boot and adb my pc won't even recognize my tablet. Also I never turned on usb dbugging cause I didn't even know what that was. I even gave it to the IT guys at work and they couldn't fix it. Now after reading everything there is to read on this problem and trying to fix it myself I'm stuck on the no command screen with the dead android robot. And now I hear there is a recall do to the battery, I can't even check what type I have. So if someone can please help me I would be much appreciative. Also this happened after updating to the latest OS.

okay so i was able to unlock the bootloader and start flashing but from fastboot flash recovery.img and beyond it says failed to write. any ideas of why?

Ace0169 said:
okay so i was able to unlock the bootloader and start flashing but from fastboot flash recovery.img and beyond it says failed to write. any ideas of why?
Click to expand...
Click to collapse
Can you flash twrp and boot to it?

Ace0169 said:
okay so i was able to unlock the bootloader and start flashing but from fastboot flash recovery.img and beyond it says failed to write. any ideas of why?
Click to expand...
Click to collapse
Hello,
Did you use "Fastboot flash recovery.img" as your command line??
I believe it is "Fastboot flash recovery recovery.img"
If you were able to unlock bootloader you're on the right track.
Sent from a Locked Bootloader

Yes I used "fastboot flash recovery recovery.img" but every command after that keeps telling me "failed to write file"

danjull said:
Can you flash twrp and boot to it?
Click to expand...
Click to collapse
I'm a complete noob when it comes to this stuff, what is twrp? Haha

Ace0169 said:
I'm a complete noob when it comes to this stuff, what is twrp? Haha
Click to expand...
Click to collapse
TWRP (Team Win Recovery Project) is a custom recovery that you can flash on your device. You can flash it like the stock recovery over fastboot. With TWRP you can make full system backups, installing roms or other stuff, wipe partitions and more. Keep trying to install the drivers on your pc. Try to use another usb slot or boot your pc into test mode to install the driver. If you can still access the bootloader, you have really good chances to rescue your device.

Okay will try that. Thanks man.

Ace0169 said:
Okay will try that. Thanks man.
Click to expand...
Click to collapse
I see what your doing wrong. You probably don't even have the recovery img to flash. That's why it's giving you a write error.
There is a tutorial in the general section, that should have all the files and links, etc etc that you'll need to flash TWRP/CWM recovery and root the device if you want
Here is the link:
http://forum.xda-developers.com/shi...k-recovery-images-ota-library-guides-t2988881
Sent from my Nexus 5

Mojar7070 said:
I see what your doing wrong. You probably don't even have the recovery img to flash. That's why it's giving you a write error.
There is a tutorial in the general section, that should have all the files and links, etc etc that you'll need to flash TWRP/CWM recovery and root the device if you want
Here is the link:
http://forum.xda-developers.com/shi...k-recovery-images-ota-library-guides-t2988881
Sent from my Nexus 5
Click to expand...
Click to collapse
If your referring to the recovery images from Nvidia website I have dowloaded that, also the correct drivers. Maybe there is something else I'm missing?

Ace0169 said:
If your referring to the recovery images from Nvidia website I have dowloaded that, also the correct drivers. Maybe there is something else I'm missing?
Click to expand...
Click to collapse
First off, let me ask, what is your end result for the tablet?? Are you trying to just go a Complete stock tablet or are you trying to do anything custom (ex. Custom rom, recovery etc etc)
I'm assuming that since you unlocked your Bootloader, your trying to do something custom.
Sent from a Locked Bootloader

Ace0169 said:
If your referring to the recovery images from Nvidia website I have dowloaded that, also the correct drivers. Maybe there is something else I'm missing?
Click to expand...
Click to collapse
Those official nVidia recovery images come with smaller .img files such as recovery.img, system.img, etc. You'll need to flash those one by one ("fastboot flash recovery recovery.img", then run "fastboot flash system system.img", etc. etc.) or you can just run the flashall script that I think is included in the nVidia images.
Otherwise, if you want to flash TWRP, you'll need to download the TWRP recovery (you can rename it to "twrp-recovery.zip"). Then you'll need to "fastboot flash twrp-recovery.zip" in order to flash the twrp recovery to your tablet.

Mojar7070 said:
First off, let me ask, what is your end result for the tablet?? Are you trying to just go a Complete stock tablet or are you trying to do anything custom (ex. Custom rom, recovery etc etc)
I'm assuming that since you unlocked your Bootloader, your trying to do something custom.
Sent from a Locked Bootloader
Click to expand...
Click to collapse
I want my tablet to boot again, it's completely unusable in its condition I've heard re flashing will fix it.

Ace0169 said:
I want my tablet to boot again, it's completely unusable in its condition I've heard re flashing will fix it.
Click to expand...
Click to collapse
OK. Then the link I gave earlier should help flash stock software onto your tablet.
However, that guide is only to go back to factory "state" Operating System wise. It may not help with hardware. Once your flash everything correctly but device still doesn't boot, its probably not software related.
Sent from my Nexus 5

Mojar7070 said:
OK. Then the link I gave earlier should help flash stock software onto your tablet.
However, that guide is only to go back to factory "state" Operating System wise. It may not help with hardware. Once your flash everything correctly but device still doesn't boot, its probably not software related.
Sent from my Nexus 5
Click to expand...
Click to collapse
so ive followed the steps in the link, and ive executed all the commands but when i get to fasboot flash system system.img it says write failed. also all the commands beyond that one. ive got to be missing something. i have the image from nvidia developer, all the drivers, and my fastboot recognizes my device. has anyone encountered this before?

Ace0169 said:
so ive followed the steps in the link, and ive executed all the commands but when i get to fasboot flash system system.img it says write failed. also all the commands beyond that one. ive got to be missing something. i have the image from nvidia developer, all the drivers, and my fastboot recognizes my device. has anyone encountered this before?
Click to expand...
Click to collapse
After you unlocked the device but before trying to flash anything else on the device, try putting the shield into Fastboot mode. At the bootloader, select fastboot using the volume buttons.

koop1955 said:
After you unlocked the device but before trying to flash anything else on the device, try putting the shield into Fastboot mode. At the bootloader, select fastboot using the volume buttons.
Click to expand...
Click to collapse
Select "fastboot protocol"? Is that correct?

Ace0169 said:
Select "fastboot protocol"? Is that correct?
Click to expand...
Click to collapse
So i selected "fastboot protocol" it blipped for a second then brought me back to the bootloader. tried flashing again and once i reached the fastboot flash system system.img it said write failed again. did it not engage the "fastboot protocol"?

Bringing you back to the bootloader was expected behavior. The "write fail" is a mystery to me. Sorry, that is all that I can offer.

koop1955 said:
Bringing you back to the bootloader was expected behavior. The "write fail" is a mystery to me. Sorry, that is all that I can offer.
Click to expand...
Click to collapse
@Ace0169 Same, not sure what else to tell you. Sorry sir.
Sent from a Locked Bootloader

How can I root project spectrum?

Are there any tools around for rooting Spectrum on the R7Plusf?

W1F1 said:
How am I able to root project spectrum on the Oppo R7 Plus?
Thanks in advance!
Click to expand...
Click to collapse
Hello, W1F1. There is no way at this point in time to root Project Spectrum on Oppo R7Plus as TWRP isnt compatible. They changed a lot when they made Project Spectrum. For now there is no TWRP. So there is no way to root. It's Fastboot is also set to non-root access making is hard to use the command (fastboot flash recovery _TWRP-HERE_) but not impossible to flash the stock recovery and then ColorOS to get back to safety (by safety I mean CyanogenMod 14.1 [OFFICIAL] or AICP [UNOFFICIAL]). All you need to do is ask and I'll give you the links.

EximusCode said:
Hello, W1F1. There is no way at this point in time to root Project Spectrum on Oppo R7Plus as TWRP isnt compatible. They changed a lot when they made Project Spectrum. For now there is no TWRP. So there is no way to root. It's Fastboot is also set to non-root access making is hard to use the command (fastboot flash recovery _TWRP-HERE_) but not impossible to flash the stock recovery and then ColorOS to get back to safety (by safety I mean CyanogenMod 14.1 [OFFICIAL] or AICP [UNOFFICIAL]). All you need to do is ask and I'll give you the links.
Click to expand...
Click to collapse
Thanks for the reply! So I could use stock recovery to get back to a version of color os that has fastboot enabled, and then get TWRP and then cyanogen mod from there?

W1F1 said:
Thanks for the reply! So I could use stock recovery to get back to a version of color os that has fastboot enabled, and then get TWRP and then cyanogen mod from there?
Click to expand...
Click to collapse
Bingo my friend. If you want the links you need only ask. :good:

EximusCode said:
Bingo my friend. If you want the links you need only ask. :good:
Click to expand...
Click to collapse
The links would be fantastic, thanks so much!

W1F1 said:
The links would be fantastic, thanks so much!
Click to expand...
Click to collapse
Will post them ASAP

Thanks!

W1F1 said:
Thanks!
Click to expand...
Click to collapse
Recovery:http://goo.gl/1AdXkD
ROM:https://s3.amazonaws.com/public.opp...olorOS/Specified_ColorOS_R7plusf_full_014.zip
0. Move all files to external MicroSD card *rename the ROM to update.zip*
1. Flash the recovery.img to recovery partition. With (fastboot flash recovery "recovery.img) *remember to put the recovery.img file in the ADB and Fastboot file for easier transfer*
2. Reboot into the system recovery and select Update, then go to where you put your ROM and select it
3. Wait for it to flash and then reboot
4. Your reboot will hang. Leave it do that for about 5 minutes, then reboot into fastboot mode again.
5. Seeing as you are now on a ROM with an unlocked bootloader you will be able to now flash TWRP recovery with the command (fastboot flash recovery "TWRPRECOVERYNAME") *I used TWRPRECOVERYNAME as an example as to where the recovery file needs to go. You should also have this in the ADB and Fastboot folder*

EximusCode said:
Will post them ASAP
Click to expand...
Click to collapse
I'm sorry but I can't seem to download from app.box, even after creating an account. Could you please upload the recovery to somewhere else like google drive?
EDIT: Whoops disregard that I managed to download it.

W1F1 said:
I'm so so sorry but I can't seem to download from app.box, even after creating an account. Could you please upload the recovery to somewhere else like google drive?
Sorry again.
EDIT: Sorry disregard that I managed to download it.
Click to expand...
Click to collapse
Hope it works for you like it did for me :good:

EximusCode said:
Recovery:http://goo.gl/1AdXkD
ROM:https://s3.amazonaws.com/public.opp...olorOS/Specified_ColorOS_R7plusf_full_014.zip
0. Move all files to external MicroSD card *rename the ROM to update.zip*
1. Flash the recovery.img to recovery partition. With (fastboot flash recovery "recovery.img) *remember to put the recovery.img file in the ADB and Fastboot file for easier transfer*
2. Reboot into the system recovery and select Update, then go to where you put your ROM and select it
3. Wait for it to flash and then reboot
4. Your reboot will hang. Leave it do that for about 5 minutes, then reboot into fastboot mode again.
5. Seeing as you are now on a ROM with an unlocked bootloader you will be able to now flash TWRP recovery with the command (fastboot flash recovery "TWRPRECOVERYNAME") *I used TWRPRECOVERYNAME as an example as to where the recovery file needs to go. You should also have this in the ADB and Fastboot folder*
Click to expand...
Click to collapse
Ok I'm still having an issue. The flashing of the recovery goes through successfully but when I try to enter recovery mode it simply shows the Oppo logo and the screen goes black. Like it's been doing with all the recovery's that I've tried. If I try the "fastboot boot recovery.img" it has this error:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 0.485s]
booting...
FAILED (remote: dtb not found)
finished. total time: 0.553s

W1F1 said:
Ok I'm still having an issue. The flashing of the recovery goes through successfully but when I try to enter recovery mode it simply shows the Oppo logo and the screen goes black. Like it's been doing with all the recovery's that I've tried. If I try the "fastboot boot recovery.img" it has this error:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 0.485s]
booting...
FAILED (remote: dtb not found)
finished. total time: 0.553s
Click to expand...
Click to collapse
After flashing recovery, type (fastboot reboot) Before you press enter, hold down the Volume - button (on the phone) and simultaneously press enter. You should then be able to boot to stock recovery
JUST REMEMBER TO NOT BOOT BACK INTO SPECTRUMOS. This will reset the recovery partition as it locks it on boot

EximusCode said:
After flashing recovery, type (fastboot reboot) Before you press enter, hold down the Volume - button (on the phone) and simultaneously press enter. You should then be able to boot to stock recovery
JUST REMEMBER TO NOT BOOT BACK INTO SPECTRUMOS. This will reset the recovery partition as it locks it on boot
Click to expand...
Click to collapse
Sadly no all it does is show the Oppo logo, and then when it should show the recovery screen it just goes black. I think it's something to do with the DTB error before.

W1F1 said:
Sadly no all it does is show the Oppo logo, and then when it should show the recovery screen it just goes black. I think it's something to do with the DTB error before.
Click to expand...
Click to collapse
Please give me some more time. I will find some more info. I will be back to you as soon as I have found some more.

EximusCode said:
Please give me some more time. I will find some more info. I will be back to you as soon as I have found some more.
Click to expand...
Click to collapse
Thank you. I have looked around a lot and I believe creating a new recovery img using the dt from here might work: https://github.com/TeamWin/Team-Win-Recovery-Project/issues/716
Please let me know if you find something.

W1F1 said:
Thank you. I have looked around a lot and I believe creating a new recovery img using the dt from here might work: https://github.com/TeamWin/Team-Win-Recovery-Project/issues/716
Please let me know if you find something.
Click to expand...
Click to collapse
You could very well try that and it work. I have limited knowledge when it comes to development of ROMs and Recoveries so I'm not too sure how you will fair, it may take a bit of trial and error. Tell me how you go with it

EximusCode said:
You could very well try that and it work. I have limited knowledge when it comes to development of ROMs and Recoveries so I'm not too sure how you will fair, it may take a bit of trial and error. Tell me how you go with it
Click to expand...
Click to collapse
Update:
Bad news: Unfortunately my phone is now stuck in a boot loop.
Good news: Using a recovery provider by the user "Ricky" on the first page of this thread: http://community.oppo.com/en/forum.php?mod=viewthread&tid=46395&extra=&page=1 I have been able to flash the stock recovery and it is now working. Because of the boot loop problem I am reinstalling Spectrum through recovery to try and get out of that, then hopefully I will be able to flash back to Color OS if the boot loop stops.

W1F1 said:
Update:
Bad news: Unfortunately my phone is now stuck in a boot loop.
Good news: Using a recovery provider by the user "Ricky" on the first page of this thread: http://community.oppo.com/en/forum.php?mod=viewthread&tid=46395&extra=&page=1 I have been able to flash the stock recovery and it is now working. Because of the boot loop problem I am reinstalling Spectrum through recovery to try and get out of that, then hopefully I will be able to flash back to Color OS if the boot loop stops.
Click to expand...
Click to collapse
Is it just the boot animation continuously playing? If so, this is when you need to turn off your phone and right as the screen goes off press and hold the volume + button. This will put you back in fastboot. Once you are there flash the TWRP recovery. After that hold the volume - and type fastboot reboot. This will boot you to TWRP recovery

EximusCode said:
Is it just the boot animation continuously playing? If so, this is when you need to turn off your phone and right as the screen goes off press and hold the volume + button. This will put you back in fastboot. Once you are there flash the TWRP recovery. After that hold the volume - and type fastboot reboot. This will boot you to TWRP recovery
Click to expand...
Click to collapse
All good, I erased data in recovery and now it's working. Now to flash back to Color OS in recovery.

W1F1 said:
All good, I erased data in recovery and now it's working. Now to flash back to Color OS in recovery.
Click to expand...
Click to collapse
Okay, good luck

Bricked while trying to install TWRP

So I've had quite of a rough evening today, first of all: I'm not a rooting newbie, so I really thought I could work out all errors on my own.
Haven't rootet my GM1910 yet, so I wanted to do that. Downloaded the latest TWRP, unlocked the Bootloader, and after "flashing" the recovery, nothing worked anymore. Normally it just jumped into the recovery, now I only got the OnePlus logo with the Text "Fastboot Mode"
this was the errormessage:
"downloading 'boot.img'...
OKAY [ 0.166s]
booting...
FAILED (remote: Failed to load/authenticate boot image: Load Error)"
After some trying around and not getting it to work, I tried using this to get the device working again:
https://forum.xda-developers.com/oneplus-7-pro/how-to/rom-stock-fastboot-roms-oneplus-7-pro-t3931424
tried both flashall.zip and flash-all-partitions.zip.
Now I'm in the QUALCOM CRASHDUMP again with the message
"dm-verity device corrupted Force Dump
kernel_restart"
I've been looking through forms for hours but nothing seems to work for me (mainly the things I wrote above)
I'd really appreciate any help, kind of getting sweaty palms now

Maybe this? It's what I used to unbrick mine but I'm tmobile GM1915....
https://forum.xda-developers.com/oneplus-7-pro/help/how-to-convert-tmobile-op7-to-t3935947

Yup, thanks for the reply, that worked! I'm not trying to root my device anymore though :laugh:
Thanks for making my night sleepable today

If you're trying to root your device.. and you have a pc.. just patch the boot.img of your latest rom using magisk.. then flash it via adb.. ???

thaiten said:
Downloaded the latest TWRP, unlocked the Bootloader, and after "flashing" the recovery, nothing worked anymore. Normally it just jumped into the recovery, now I only got the OnePlus logo with the Text "Fastboot Mode"
this was the errormessage:
"downloading 'boot.img'...
OKAY [ 0.166s]
booting...
FAILED (remote: Failed to load/authenticate boot image: Load Error)"
Click to expand...
Click to collapse
What are the exact commands/steps did you us to flash TWRP? And why is "flashing" in quotes? You either boot TWRP.img and can just flash Magisk for root without flashing TWRP; or you boot TWRP.img, flash the TWRP installer zip, flash Magisk.
And why does it say "boot.img"? What file are you trying to boot exactly? You should be booting the TWRP.img
I suspect the condition may be due to wrong fastboot command or flashing the wrong file. But we'd need to know the details requested above to figure out what went wrong. What root guide were you following?
In any case, going to fastboot mode, the phone is most likely not bricked. Just stuck in a state that it can't boot into OOS. Probably can recovery using a fastboot ROM, or flash back to stock boot.img.

failed to load authenticate boot image load error twrp
Hi there,
This problem happened to me exactly to days ago and I'm struggling with it.
My last version of Oxygen OS was 10.3.0
Please people, tell us your Oxyygen OS version before the incident.
@redpoint73 as you may see in my attachment, this isn't an error or a mistype. It seems to be a real nasty problem

solid.snake said:
This problem happened to me exactly to days ago and I'm struggling with it.
My last version of Oxygen OS was 10.3.0
Please people, tell us your Oxyygen OS version before the incident.
@redpoint73 as you may see in my attachment, this isn't an error or a mistype. It seems to be a real nasty problem
Click to expand...
Click to collapse
Did you try changing the twrp img file name to "twrp.img" (or similar, just something less complicated) and copying into your fastboot folder?
I agree the error message that it is looking for a file "boot.img" is strange and disconcerting. My suggestion may not fix this, but it is worth a try.

redpoint73 said:
Did you try changing the twrp img file name to "twrp.img" (or similar, just something less complicated) and copying into your fastboot folder?
I agree the error message that it is looking for a file "boot.img" is strange and disconcerting. My suggestion may not fix this, but it is worth a try.
Click to expand...
Click to collapse
Already done, please look at my 1rst screenshot : twrp74.img

solid.snake said:
Already done, please look at my 1rst screenshot : twrp74.img
Click to expand...
Click to collapse
But in the same folder as fastboot.exe, so you don't need to give a path in the command? I know this shouldn't change anything (the way you did it should work). But just an idea. The command would simply be:
fastboot boot twrp74.img
Might be a quirk with 10.0.3 (as you seem to already be eluding) or the TWRP build (maybe try another, slightly older?). But again, just throwing out some ideas to try.

redpoint73 said:
But in the same folder as fastboot.exe, so you don't need to give a path in the command? I know this shouldn't change anything (the way you did it should work). But just an idea. The command would simply be:
fastboot boot twrp74.img
Might be a quirk with 10.0.3 (as you seem to already be eluding) or the TWRP build (maybe try another, slightly older?). But again, just throwing out some ideas to try.
Click to expand...
Click to collapse
Okay, i'll give a try and tell you.

redpoint73 said:
"flashing" in quotes?
Click to expand...
Click to collapse
Because I'm just booting into TWRP first and then install it I thought. And because it didnt work lol
redpoint73 said:
And why does it say "boot.img"? What file are you trying to boot exactly? You should be booting the TWRP.img
Click to expand...
Click to collapse
I am, not sure why it says boot.img
redpoint73 said:
I suspect the condition may be due to wrong fastboot command or flashing the wrong file.
Click to expand...
Click to collapse
I used
Code:
fastboot boot twrp.img
and
Code:
fastboot flash recovery twrp.img
If I'm not mistaken. Was a few days ago now

solid.snake said:
Please people, tell us your Oxyygen OS version before the incident.
Click to expand...
Click to collapse
Was on the latest OOS Beta. But since using the freshly installed ROM with the MSM Tool, my device feels way smoother and the FPS works way faster. I don't know if thats because I bought the Chinese Version of the phone and there where a lot of trojans running in the background /s
But seriously though, way smoother. Probably partly caused by the longer animation duration set by default, but no idea about the FPS

redpoint73 said:
But in the same folder as fastboot.exe, so you don't need to give a path in the command? I know this shouldn't change anything (the way you did it should work). But just an idea. The command would simply be:
fastboot boot twrp74.img
Might be a quirk with 10.0.3 (as you seem to already be eluding) or the TWRP build (maybe try another, slightly older?). But again, just throwing out some ideas to try.
Click to expand...
Click to collapse
Same result here

Getting root

Im on 11.02
if i boot a twrp via fastboot my phone hangs on fastboot and if i flash a patched bootfile the booting process does not end. It hangs on the bootanimation, though i can login te phone with adb shell and even get root. Im looking for a twrp that boots up in fastboot i guess. Anyone outhere that recognizes this and knows how to deal with this?

Zobat said:
Im on 11.02
if i boot a twrp via fastboot my phone hangs on fastboot and if i flash a patched bootfile the booting process does not end. It hangs on the bootanimation, though i can login te phone with adb shell and even get root. Im looking for a twrp that boots up in fastboot i guess. Anyone outhere that recognizes this and knows how to deal with this?
Click to expand...
Click to collapse
Hello, you should mention what TWRP exactly you're trying to boot

strongst said:
Hello, you should mention what TWRP exactly you're trying to boot
Click to expand...
Click to collapse
I'm away from my computer now but i tried 2
The latest 3.5 or something like that and 3.3 something
Is there a version recommended version?

Zobat said:
I'm away from my computer now but i tried 2
The latest 3.5 or something like that and 3.3 something
Is there a version recommended version?
Click to expand...
Click to collapse
I'm only aware of 3.4-10, maybe you have another one, please check the guide and the links to TWRP images which you have to boot: https://forum.xda-developers.com/t/...tloader-twrp-root-with-magisk-update.3954559/

strongst said:
I'm only aware of 3.4-10, maybe you have another one, please check the guide and the links to TWRP images which you have to boot: https://forum.xda-developers.com/t/...tloader-twrp-root-with-magisk-update.3954559/
Click to expand...
Click to collapse
Unfortunately the same result. If i boot this via fastboot my phone hangs on fastboot.

Zobat said:
Unfortunately the same result. If i boot this via fastboot my phone hangs on fastboot.
Click to expand...
Click to collapse
Which TWRP did you used in the past or is this the first time you want to install TWRP permanently?

strongst said:
Which TWRP did you used in the past or is this the first time you want to install TWRP permanently?
Click to expand...
Click to collapse
I upgraded to android 11. I lost twrp somewhere in the process. I miss the option to directly patch the running kernel/bootimage in magisk-manager. Maybe i should look for an older version of MagiskManager.

Zobat said:
I upgraded to android 11. I lost twrp somewhere in the process. I miss the option to directly patch the running kernel/bootimage in magisk-manager. Maybe i should look for an older version of MagiskManager.
Click to expand...
Click to collapse
Can you post the console output of your PC which shows the steps to boot the TWRP?
Which magisk version do you have in place?
Are you asked to enter a pin from the lockscreen security?

strongst said:
Can you post the console output of your PC which shows the steps to boot the TWRP?
Which magisk version do you have in place?
Are you asked to enter a pin from the lockscreen security?
Click to expand...
Click to collapse
downloading 'boot.img'...
OKAY [ 1.214s]
booting...
OKAY [ 0.123s]
finished. total time: 1.337s
Then it hangs in fastboot. I just removed the pinlock and flashed my magisk patched image again. I can login via adb and get root, but the setup does not finish.
I flash my unpatched boot.img again and all is well. No root off course.
Im using the latest magisk app: 22.1

Zobat said:
downloading 'boot.img'...
OKAY [ 1.214s]
booting...
OKAY [ 0.123s]
finished. total time: 1.337s
Then it hangs in fastboot. I just removed the pinlock and flashed my magisk patched image again. I can login via adb and get root, but the setup does not finish.
I flash my unpatched boot.img again and all is well. No root off course.
Im using the latest magisk app: 22.1
Click to expand...
Click to collapse
You used the command
Code:
fastboot boot twrp-3.4.0-10--guacamole-unified-Q-mauronofrio.img
?

strongst said:
You used the command
Code:
fastboot boot twrp-3.4.0-10--guacamole-unified-Q-mauronofrio.img
?
Click to expand...
Click to collapse
Code:
~/android$ fastboot boot twrp-3.4.0-10-guacamole-unified-Q-mauronofrio.img
downloading 'boot.img'...
OKAY [ 1.151s]
booting...
OKAY [ 0.123s]
finished. total time: 1.274s

I'm thinking about moving this discussion to: https://forum.xda-developers.com/t/...l-twrp-for-oneplus-7-7-pro-5g-stable.3932943/

Hey can someone share the Cons of root, because this is very first time when I will install Custom ROOM on my mobile phone, or another thing I wanna ask, is it compulsory to install custom ROOM after rooting my device, I just need root permission for some sort of APPS that needs root access. jbbattery spain

imranhashmi76 said:
Hey can someone share the Cons of root, because this is very first time when I will install Custom ROOM on my mobile phone, or another thing I wanna ask, is it compulsory to install custom ROOM after rooting my device, I just need root permission for some sort of APPS that needs root access.
Click to expand...
Click to collapse
Hey brp about the cons i don't have much idea but the second question, If you don't wanna install custom root then no problem you can still with your original Software, there is no any condition to install custom rom with root file.