Related
Hello,
i am just thinking i bricked my Galaxy Nexus.
But first i will describe what happened:
My device was running fine with 4.3 Cyanonogenmod Nighlty builds for a few days but yesterday in the car the device suddenly was stuck in a bootloop.
After arriving home i tried to fix that by removing the battery and give it a few minutes.
But my device was stuck in a bootloop after that.
I tried to reflash ROM and RADIO few times but nothing helped.
I was in TWRP Recovery and wanted to get CWM just to rescue some files via USB before flashing stock ROM.
So i got the toolkit and tried to flash a recovery and the script told me all worked, but there seems not to be any recovery on the device anymore.
When i boot into bootloader and select Recovery i am just getting the battery symbol and nothing more happens.
I flashed a stock ROM via toolkit without wiping userdata but this did not help, too.
Now i am stuck with a device that does not seem to have a recovery and does not boot behind the Google Logo.
Also the device only reacts to the power button anymore when on external power via USB wire, not on battery.
Any suggestions how to continue or just rescue my files from the "sdcard" ?
myxor said:
Hello,
i am just thinking i bricked my Galaxy Nexus.
But first i will describe what happened:
My device was running fine with 4.3 Cyanonogenmod Nighlty builds for a few days but yesterday in the car the device suddenly was stuck in a bootloop.
After arriving home i tried to fix that by removing the battery and give it a few minutes.
But my device was stuck in a bootloop after that.
I tried to reflash ROM and RADIO few times but nothing helped.
I was in TWRP Recovery and wanted to get CWM just to rescue some files via USB before flashing stock ROM.
So i got the toolkit and tried to flash a recovery and the script told me all worked, but there seems not to be any recovery on the device anymore.
When i boot into bootloader and select Recovery i am just getting the battery symbol and nothing more happens.
I flashed a stock ROM via toolkit without wiping userdata but this did not help, too.
Now i am stuck with a device that does not seem to have a recovery and does not boot behind the Google Logo.
Also the device only reacts to the power button anymore when on external power via USB wire, not on battery.
Any suggestions how to continue or just rescue my files from the "sdcard" ?
Click to expand...
Click to collapse
Drop the toolkit, learn how to do it proper or stop flashing stuff before you hurt your device.
beekay201 said:
Drop the toolkit, learn how to it proper or stop flashing stuff before you hurt your device.
Click to expand...
Click to collapse
I guess it's already to late
I just tried to install the CWM Recovery via fastboot
D:\gn\adt-bundle-windows-x86_64
sending 'recovery' (6214 KB)...
OKAY [ 0.631s]
writing 'recovery'...
OKAY [ 0.759s]
finished. total time: 1.392s
D:\gn\adt-bundle-windows-x86_64
rebooting into bootloader...
OKAY [ 0.007s]
finished. total time: 0.007s
Click to expand...
Click to collapse
But when i select Recovery from the bootloader menu i only get the charging battery icon.
Anything i can do?
I've never had a similar experience so but from reading several similar topics I will suggest that you flash a factory image. Not a STOCK ROM, but the actual factory image. It *should* re-lock the boot loader and default you to complete stock.Your files will be gone but assuming the files aren't overwritten you can still recover them per the instructions on this thread. As others have suggested, lay off the toolkit. Without it, you will be absolutely sure as to what is going on with your phone. Read, read, read, read before doing anything you're unfamiliar with.
iLeopard said:
I've never had a similar experience so but from reading several similar topics I will suggest that you flash a factory image. Not a STOCK ROM, but the actual factory image. It *should* re-lock the boot loader and default you to complete stock.Your files will be gone but assuming the files aren't overwritten you can still recover them per the instructions on this thread. As others have suggested, lay off the toolkit. Without it, you will be absolutely sure as to what is going on with your phone. Read, read, read, read before doing anything you're unfamiliar with.
Click to expand...
Click to collapse
Thank you for your advices but the results are not what i hoped for:
After flashing the factory image from https://developers.google.com/android/nexus/images#instructions with the following output:
Code:
sending 'bootloader' (2308 KB)...
OKAY [ 0.236s]
writing 'bootloader'...
OKAY [ 0.605s]
finished. total time: 0.841s
rebooting into bootloader...
OKAY [ 0.007s]
finished. total time: 0.009s
< waiting for device >
sending 'radio' (12288 KB)...
OKAY [ 1.233s]
writing 'radio'...
OKAY [ 2.590s]
finished. total time: 3.824s
rebooting into bootloader...
OKAY [ 0.007s]
finished. total time: 0.007s
< waiting for device >
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: PRIMEMD04
Baseband Version.....: I9250XXLJ1
Serial Number........: XXXXXXXXXXXXXXXX (censored by author)
--------------------------------------------
checking product...
OKAY [ 0.006s]
checking version-bootloader...
OKAY [ 0.008s]
checking version-baseband...
OKAY [ 0.007s]
sending 'boot' (4376 KB)...
OKAY [ 0.438s]
writing 'boot'...
OKAY [ 0.380s]
sending 'recovery' (4924 KB)...
OKAY [ 0.497s]
writing 'recovery'...
OKAY [ 0.761s]
erasing 'system'...
OKAY [ 0.013s]
sending 'system' (474180 KB)...
OKAY [ 46.800s]
writing 'system'...
OKAY [ 47.830s]
erasing 'userdata'...
OKAY [ 0.550s]
formatting 'userdata' partition...
Creating filesystem with parameters:
Size: 14539534336
Block size: 4096
Blocks per group: 32768
Inodes per group: 8144
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 3549691
Block groups: 109
Reserved block group size: 871
Created filesystem with 11/887696 inodes and 97200/3549691 blocks
sending 'userdata' (137559 KB)...
writing 'userdata'...
OKAY [ 25.975s]
erasing 'cache'...
OKAY [ 0.015s]
formatting 'cache' partition...
Creating filesystem with parameters:
Size: 452984832
Block size: 4096
Blocks per group: 32768
Inodes per group: 6912
Inode size: 256
Journal blocks: 1728
Label:
Blocks: 110592
Block groups: 4
Reserved block group size: 31
Created filesystem with 11/27648 inodes and 3566/110592 blocks
sending 'cache' (8832 KB)...
writing 'cache'...
OKAY [ 3.136s]
rebooting...
finished. total time: 126.458s
Press any key to exit...
the device is stuck in the Google Logo now for about 10 Minutes and nothing is happening :crying:
Was this issued using flash-all.bat?
Sent from my Galaxy Nexus using xda app-developers app
myxor said:
Thank you for your advices but the results are not what i hoped for:
After flashing the factory image from https://developers.google.com/android/nexus/images#instructions with the following output:
Code:
sending 'bootloader' (2308 KB)...
OKAY [ 0.236s]
writing 'bootloader'...
OKAY [ 0.605s]
finished. total time: 0.841s
rebooting into bootloader...
OKAY [ 0.007s]
finished. total time: 0.009s
< waiting for device >
sending 'radio' (12288 KB)...
OKAY [ 1.233s]
writing 'radio'...
OKAY [ 2.590s]
finished. total time: 3.824s
rebooting into bootloader...
OKAY [ 0.007s]
finished. total time: 0.007s
< waiting for device >
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: PRIMEMD04
Baseband Version.....: I9250XXLJ1
Serial Number........: XXXXXXXXXXXXXXXX (censored by author)
--------------------------------------------
checking product...
OKAY [ 0.006s]
checking version-bootloader...
OKAY [ 0.008s]
checking version-baseband...
OKAY [ 0.007s]
sending 'boot' (4376 KB)...
OKAY [ 0.438s]
writing 'boot'...
OKAY [ 0.380s]
sending 'recovery' (4924 KB)...
OKAY [ 0.497s]
writing 'recovery'...
OKAY [ 0.761s]
erasing 'system'...
OKAY [ 0.013s]
sending 'system' (474180 KB)...
OKAY [ 46.800s]
writing 'system'...
OKAY [ 47.830s]
erasing 'userdata'...
OKAY [ 0.550s]
formatting 'userdata' partition...
Creating filesystem with parameters:
Size: 14539534336
Block size: 4096
Blocks per group: 32768
Inodes per group: 8144
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 3549691
Block groups: 109
Reserved block group size: 871
Created filesystem with 11/887696 inodes and 97200/3549691 blocks
sending 'userdata' (137559 KB)...
writing 'userdata'...
OKAY [ 25.975s]
erasing 'cache'...
OKAY [ 0.015s]
formatting 'cache' partition...
Creating filesystem with parameters:
Size: 452984832
Block size: 4096
Blocks per group: 32768
Inodes per group: 6912
Inode size: 256
Journal blocks: 1728
Label:
Blocks: 110592
Block groups: 4
Reserved block group size: 31
Created filesystem with 11/27648 inodes and 3566/110592 blocks
sending 'cache' (8832 KB)...
writing 'cache'...
OKAY [ 3.136s]
rebooting...
finished. total time: 126.458s
Press any key to exit...
the device is stuck in the Google Logo now for about 10 Minutes and nothing is happening :crying:
Click to expand...
Click to collapse
4.3 first bootup times is much slower than previous versions. Let it boot until it reboots itself or something. If after 45min it still going at it, I think you have two options:
- my first suggestion is to return to the bootloader, and follow this thread's first post. No need to reflash bootloader or radio, as far as I can tell, nothing's wrong with those two. Erase, then format all the remaining partitions.
Code:
fastboot erase partition_name
fastboot format partition_name
Flash all the remaining partitions: boot, recovery (a custom recovery if you'd like, beware of 4.3 changes - not sure all the custom recoveries have updated accordingly, check dev section), system, userdata, cache.
Code:
fastboot flash partition /path/to/filename.img
- my second suggestion is that you search of a way to enable adbd, to see whats going on. That might require some extra steps, such as editing init.rc i believe.
Anyways, if you return to the bootloader, and try to
Code:
fastboot boot /path/to/cwm_or_twrp.img
What does it do? Can you use your custom recovery now?
beekay201 said:
4.3 first bootup times is much slower than previous versions. Let it boot until it reboots itself or something. If after 45min it still going at it, I think you have two options:
- my first suggestion is to return to the bootloader, and follow this thread's first post. No need to reflash bootloader or radio, as far as I can tell, nothing's wrong with those two. Erase, then format all the remaining partitions.
Code:
fastboot erase partition_name
fastboot format partition_name
Flash all the remaining partitions: boot, recovery (a custom recovery if you'd like, beware of 4.3 changes - not sure all the custom recoveries have updated accordingly, check dev section), system, userdata, cache.
Code:
fastboot flash partition /path/to/filename.img
- my second suggestion is that you search of a way to enable adbd, to see whats going on. That might require some extra steps, such as editing init.rc i believe.
Anyways, if you return to the bootloader, and try to
Code:
fastboot boot /path/to/cwm_or_twrp.img
What does it do? Can you use your custom recovery now?
Click to expand...
Click to collapse
I ran through the linked post and erased + formated all possible partitions.
Is it normal that o can not format some partitions like the recovery partition?
Code:
>fastboot format recovery
formatting 'recovery' partition...
Formatting is not supported for filesystem with type 'raw'.
FAILED ()
finished. total time: 0.009s
After that i flashed the partitions once by once per
Code:
fastboot flash partitions /path/file.img
with the files from the factory image.
Sadly no boot possible.
Then i tried to boot my recovery by
Code:
fastboot boot /path/to/cwm_or_twrp.img
but it happens the same as before:
after selecting to boot into recovery from fastboot mode the google logo appears for a few seconds then the screens goes black and returns with the battery charging symbol.
After turning the phone off and booting again into fastboot mode i can read in red letters: "FASTBOOT MODE - NO BOOT OR RECOVERY IMG".
This stays the same after flashing a recovery image via fastboot :crying:
myxor said:
I ran through the linked post and erased + formated all possible partitions.
Is it normal that o can not format some partitions like the recovery partition?
Code:
>fastboot format recovery
formatting 'recovery' partition...
Formatting is not supported for filesystem with type 'raw'.
FAILED ()
finished. total time: 0.009s
After that i flashed the partitions once by once per
Code:
fastboot flash partitions /path/file.img
with the files from the factory image.
Sadly no boot possible.
Then i tried to boot my recovery by
Code:
fastboot boot /path/to/cwm_or_twrp.img
but it happens the same as before:
after selecting to boot into recovery from fastboot mode the google logo appears for a few seconds then the screens goes black and returns with the battery charging symbol.
After turning the phone off and booting again into fastboot mode i can read in red letters: "FASTBOOT MODE - NO BOOT OR RECOVERY IMG".
This stays the same after flashing a recovery image via fastboot :crying:
Click to expand...
Click to collapse
Use omapflash to restore your bootloader. See this thread's post with useful links. http://forum.xda-developers.com/showthread.php?t=1812959
I sent in the device to the repair and got it back a few days ago.
Some "broken parts" were changed and i got a new battery.
Now my Galaxy Nexus works again like a charm
Don't really know what parts were broken but it seemed that it was a hardware failure.
Thanks to everyone who helped! :good:
So, I previously had a custom ROM but I wanted to switch to the new Dev Preview of P.
Running flash_all.bat gives no unusual error.
target reported max download size of 536870912 bytes
sending 'bootloader' (36380 KB)...
OKAY [ 0.107s]
writing 'bootloader'...
OKAY [ 0.382s]
finished. total time: 0.495s
rebooting into bootloader...
OKAY [ 0.004s]
finished. total time: 0.005s
target reported max download size of 536870912 bytes
sending 'radio' (60388 KB)...
OKAY [ 0.165s]
writing 'radio'...
OKAY [ 0.574s]
finished. total time: 0.742s
rebooting into bootloader...
OKAY [ 0.003s]
finished. total time: 0.004s
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'
Creating filesystem with parameters:
Size: 56946044928
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 13902843
Block groups: 425
Reserved block group size: 1024
Created filesystem with 11/3481600 inodes and 264598/13902843 blocks
Erase successful, but not automatically formatting.
Can't determine partition type.
FAILED (remote: GetVar Variable Not found)
--------------------------------------------
Bootloader Version...: TMZ20i
Baseband Version.....: g8998-00223-1804021619
Serial Number........: 711KPAE0759488
--------------------------------------------
checking product...
OKAY [ 0.009s]
checking version-bootloader...
OKAY [ 0.007s]
checking version-baseband...
OKAY [ 0.004s]
sending 'boot' (40960 KB)...
OKAY [ 0.119s]
writing 'boot'...
OKAY [ 0.368s]
sending sparse 'system' (524284 KB)...
OKAY [ 2.889s]
writing 'system'...
OKAY [ 2.435s]
sending sparse 'system' (524284 KB)...
OKAY [ 2.701s]
writing 'system'...
OKAY [ 2.427s]
sending sparse 'system' (524284 KB)...
OKAY [ 2.773s]
writing 'system'...
OKAY [ 2.440s]
sending sparse 'system' (521196 KB)...
OKAY [ 2.728s]
writing 'system'...
OKAY [ 2.420s]
sending sparse 'system' (107872 KB)...
OKAY [ 0.545s]
writing 'system'...
OKAY [ 0.504s]
sending 'vendor' (384712 KB)...
OKAY [ 1.080s]
writing 'vendor'...
OKAY [ 1.790s]
erasing 'userdata'...
OKAY [ 0.286s]
sending 'userdata' (140898 KB)...
OKAY [ 0.399s]
writing 'userdata'...
OKAY [ 1.488s]
erasing 'cache'...
FAILED (remote: Check device console.)
finished. total time: 27.493s
Press any key to exit...
Click to expand...
Click to collapse
And manually flashing using this tutorial gives the same result.
After the "device is corrupt" message I get a Google logo with the unlocked lock at the bottom. So before the ROM boots.
I've tried the May System Image also, but it returns the exact same result. What should I do?
(It is critically unlocked)
I have the same problem!!!
OK guys I'm lost.
I was on TWRP and SELFISH ROM.
But then today due to ANDROID P Beta I want to go to Beta.
I did put the phone into bootloader.
and installed previous IMAGE : walleye-opd1.170816.010-factory-63083164
After that I put new image : walleye-ppp2.180412.013-factory-6406b348
Instaled like below.
But I can not boot. It always goes to bootloader. even recovery does not work.
I done like,this:
Mode LastWriteTime Length Name
---- ------------- ------ ----
-a---- 09/03/2018 10:38 2604257 adb-linux
-a---- 09/03/2018 10:37 2581412 adb-mac
-a---- 09/03/2018 10:30 1784320 adb.exe
-a---- 09/03/2018 10:30 97792 AdbWinApi.dll
-a---- 09/03/2018 10:30 62976 AdbWinUsbApi.dll
-a---- 28/09/2017 12:38 39657472 bootloader-walleye-mw8998-002.0059.00.img
-a---- 09/03/2018 10:38 1265485 fastboot-linux
-a---- 09/03/2018 10:37 1380616 fastboot-mac
-a---- 09/03/2018 10:30 853504 fastboot.exe
-a---- 28/09/2017 12:38 990 flash-all.bat
-a---- 28/09/2017 12:38 861 flash-all.sh
-a---- 28/09/2017 12:38 808 flash-base.sh
-a---- 28/09/2017 12:38 1571219263 image-walleye-opd1.170816.010.zip
-a---- 02/06/2017 23:07 541322 mfastboot-linux
-a---- 02/06/2017 23:07 225100 mfastboot-mac
-a---- 02/06/2017 23:07 533353 mfastboot.exe
-a---- 28/09/2017 12:38 61878272 radio-walleye-g8998-00122-1708311414.img
PS C:\11> fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.001s]
finished. total time: 0.002s
PS C:\11> fastboot flash bootloader bootloader-walleye-mw8998-002.0059.00.img
target reported max download size of 536870912 bytes
sending 'bootloader' (38728 KB)...
OKAY [ 0.919s]
writing 'bootloader'...
(bootloader) Updating: partition:0 @00002000 sz=0000B000
(bootloader) Updating: partition:1 @0000D000 sz=0000B000
(bootloader) Updating: partition:2 @00018000 sz=0000B000
(bootloader) Updating: partition:3 @00023000 sz=0000B000
(bootloader) Updating: partition:4 @0002E000 sz=0000B000
(bootloader) Updating: partition:5 @00039000 sz=0000B000
(bootloader) Updating: cmnlib64 @00044000 sz=00049000
(bootloader) Updating: cmnlib @0008D000 sz=00038000
(bootloader) Updating: devcfg @000C5000 sz=0000F000
(bootloader) Updating: hyp @000D4000 sz=00040000
(bootloader) Updating: keymaster @00114000 sz=00046000
(bootloader) Updating: lockbooter @0015A000 sz=00016000
(bootloader) Updating: pmic @00170000 sz=0000D000
(bootloader) Updating: rpm @0017D000 sz=0003A000
(bootloader) Updating: tz @001B7000 sz=001DB000
(bootloader) Updating: xbl @00392000 sz=003A2000
(bootloader) Updating: apdp @00734000 sz=00004000
(bootloader) Updating: msadp @00738000 sz=00004000
(bootloader) Updating: hosd @0073C000 sz=01E31000
(bootloader) Updating: abl @0256D000 sz=00065000
OKAY [ 1.062s]
finished. total time: 1.985s
PS C:\11> fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.001s]
finished. total time: 0.001s
PS C:\11> fastboot flash radio radio-walleye-g8998-00122-1708311414.img
target reported max download size of 536870912 bytes
sending 'radio' (60428 KB)...
OKAY [ 1.364s]
writing 'radio'...
(bootloader) Updating: modem @00001000 sz=03B01000
OKAY [ 0.290s]
finished. total time: 1.814s
PS C:\11> fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.001s]
finished. total time: 0.001s
PS C:\11> fastboot flash image image-walleye-opd1.170816.010.zip
target reported max download size of 536870912 bytes
Invalid sparse file format at header magi
PS C:\11> fastboot
usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall flash boot, system, vendor and if found,
recovery
flash <partition> [ <filename> ] write a file to a flash partition
flashing lock locks the device. Prevents flashing partitions
flashing unlock unlocks the device. Allows user to flash any partition except the ones that are related to bootloader
flashing lock_critical Prevents flashing bootloader related partitions
flashing unlock_critical Enables flashing bootloader related partitions
flashing get_unlock_ability Queries bootloader to see if the device is unlocked
erase <partition> erase a flash partition
format[:[<fs type>][:[<size>]] <partition> format a flash partition.
Can override the fs type and/or
size the bootloader reports.
getvar <variable> display a bootloader variable
boot <kernel> [ <ramdisk> ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> ] create bootimage and flash it
devices list all connected devices
continue continue with autoboot
reboot [bootloader] reboot device, optionally into bootloader
reboot-bootloader reboot device into bootloader
help show this help message
options:
-w erase userdata and cache (and format
if supported by partition type)
-u do not first erase partition before
formatting
-s <specific device> specify device serial number
or path to device port
-l with "devices", lists device paths
-p <product> specify product name
-c <cmdline> override kernel commandline
-i <vendor id> specify a custom USB vendor id
-b <base_addr> specify a custom kernel base address.
default: 0x10000000
-n <page size> specify the nand page size.
default: 2048
-S <size>[K|M|G] automatically sparse files greater
than size. 0 to disable
PS C:\11> fastboot -w update image-walleye-opd1.170816.010.zip
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'
Creating filesystem with parameters:
Size: 121043398656
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 29551611
Block groups: 902
Reserved block group size: 1024
Created filesystem with 11/7389184 inodes and 511894/29551611 blocks
Erase successful, but not automatically formatting.
Can't determine partition type.
FAILED (remote: GetVar Variable Not found)
--------------------------------------------
Bootloader Version...: mw8998-002.0059.00
Baseband Version.....: g8998-00122-1708311414
Serial Number........: FA79G1A07951
--------------------------------------------
checking product...
OKAY [ 0.001s]
checking version-bootloader...
OKAY [ 0.001s]
checking version-baseband...
OKAY [ 0.001s]
sending 'boot' (32768 KB)...
OKAY [ 0.773s]
writing 'boot'...
OKAY [ 0.161s]
sending sparse 'system' (524284 KB)...
OKAY [ 12.709s]
writing 'system'...
OKAY [ 17.550s]
sending sparse 'system' (524284 KB)...
OKAY [ 13.020s]
writing 'system'...
OKAY [ 15.830s]
sending sparse 'system' (524284 KB)...
OKAY [ 13.551s]
writing 'system'...
OKAY [ 17.529s]
sending sparse 'system' (322300 KB)...
OKAY [ 7.849s]
writing 'system'...
OKAY [ 8.635s]
sending 'vendor' (346964 KB)...
OKAY [ 8.022s]
writing 'vendor'...
OKAY [ 10.314s]
erasing 'userdata'...
OKAY [ 1.559s]
sending 'userdata' (145005 KB)...
OKAY [ 3.188s]
writing 'userdata'...
OKAY [ 2.210s]
erasing 'cache'...
FAILED (remote: Check device console.)
finished. total time: 133.102s
PS C:\11> fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.001s]
finished. total time: 0.001s
I have tried, to put sideload OTA.zip (my file walleye-opd1.170816.010-factory-63083164.zip)
But it says NULL found, and will still not work. Can not go above bootloader.
Wanted to install twrp and device not found.
Any ideas., I'm lost.
cvenk said:
I have tried, to put sideload OTA.zip (my file walleye-opd1.170816.010-factory-63083164.zip)
But it says NULL found, and will still not work. Can not go above bootloader.
Wanted to install twrp and device not found.
Any ideas., I'm lost.
Click to expand...
Click to collapse
Shouldn't you be flashing the taimen image? walleye is for the P2, taimen is P2XL.
Hello,
Use the last version of adb ( I had this message with the old one ), second, use Taimen if you have the "2 XL"
Update your fastboot and try again
Personally I use Deuce script. Download the latest images and unzip them to the folder. Then run the Deuce batch file. It will clean/wipe/format everything and put it back to scratch/stock every time on my phone, no matter how fubar my phone like corrupt boot etc..
Then, developer/debug mode. Copy files over after you do a basic setup of the Rom. Then, do whatever are normal steps to run the Beta or a custom Rom from there.
I could never on two computers get fastboot to work with the Flash all bat without errors like that.
Deuce has always worked for me...and I've always had the latest fastboot/adb every time...so thank goodness for Deuce.
---------- Post added at 07:46 PM ---------- Previous post was at 07:38 PM ----------
lorax70 said:
Shouldn't you be flashing the taimen image? walleye is for the P2, taimen is P2XL.
Click to expand...
Click to collapse
Uh..yeah...the Words Taimen should be in the file...not walleye....haha
Anyway..use Deuce and try that method. Had same issues months ago and could never get flash all bat to work from Google without using Deuce to save the day.
OK, thanks. will try, also try the different computer that I had previous luck with it,
Have Pixel 2. But you guys are more active on XL forum, and at the end, it is the same phone.
The only trouble that I can find now is all my flashes worked without errors and nothing happened.
Will report back , hope with a good news.
---------- Post added at 06:17 AM ---------- Previous post was at 06:10 AM ----------
OK, some good news,
Did deuce script on the different computer.
And after restart, it went directly to TWRP. <I don't get it. didn't I just reformatted the phone with stock rom
Now I don't know where to continue.
Will probably install some custom ROM just in case, that I can get the normal boot? But want to go to android P and would appreciate any steps hot to get from custom rom and TWRP to original BETA.
Thank you again guys, you saved me this time.
I installed again TWRP just in case. TWRP installes on both slots, But when I but on SLOT A I can boot to recovery.
If I sellect SLOT B it gives me error and it is all over, can not get anywhere.
Than I fastboot --set-active=a
And again went to twrp.
Any IDEAS what is going on.
OK, did it. Did the fastboot flash all after new drivers new adb install and new computer.. after that it went through., Now I'm on BETA.
Thanks, everybody.
I just received my Android 10 update and after the update when it asked to reboot I tapped reboot and now it has been stuck in a continuous bootloop. My phone was not rooted or modded in any way. I was able to boot into the recovery selection menu but cant go into the actual recovery (it just says "no item" when I select recovery).
Any help/suggestions?
You can reflash the ROM using the full OTA package, as is stated by Google in https://developers.google.com/android/ota : This page contains full OTA update packages that allow you to restore your Nexus or Pixel device's original factory firmware. You will find these files useful if you have experienced a failure to take an OTA. This has the same effect as flashing the corresponding factory image, but without the need to wipe the device or unlock the bootloader." You also have in that page instructions of the whole process.
All you need to do is reboot into recovery, enter adb sideload mode from whitin it and send the zip OTA file using your PC and adb. Download QP1A.190711.020 version under Pixel 2 XL.
In order to boot into recovery, when you see the Android robot with the "no item" message keep pressed the power button and then short-press volume up until the recovery options show up.
It after that it's still failing, just format within recovery or flash the full firmware stock package.
fdgd1998 said:
You can reflash the ROM using the full OTA package, as is stated by Google in https://developers.google.com/android/ota : This page contains full OTA update packages that allow you to restore your Nexus or Pixel device's original factory firmware. You will find these files useful if you have experienced a failure to take an OTA. This has the same effect as flashing the corresponding factory image, but without the need to wipe the device or unlock the bootloader." You also have in that page instructions of the whole process.
All you need to do is reboot into recovery, enter adb sideload mode from whitin it and send the zip OTA file using your PC and adb. Download QP1A.190711.020 version under Pixel 2 XL.
In order to boot into recovery, when you see the Android robot with the "no item" message keep pressed the power button and then short-press volume up until the recovery options show up.
It after that it's still failing, just format within recovery or flash the full firmware stock package.
Click to expand...
Click to collapse
thank you for the helpful reply
i had already started the process and have already downloaded all the files
but i cant unlock the bootloader as it says in the tutorial
am i doing something wrong? or is there any way to flash without unlocking the bootloader?
Edit: I dont have the "oem unlock" option turned on.
PLZ HELP
areebiqbal said:
thank you for the helpful reply
i had already started the process and have already downloaded all the files
but i cant unlock the bootloader as it says in the tutorial
am i doing something wrong? or is there any way to flash without unlocking the bootloader?
Edit: I dont have the "oem unlock" option turned on.
PLZ HELP
Click to expand...
Click to collapse
Are you flashing the OTA or the full firmware? For the OTA bootloader unlock isn't necessary.
And in the instructions are stated the opposite, you must have misread it.
fdgd1998 said:
Are you flashing the OTA or the full firmware? For the OTA bootloader unlock isn't necessary.
And in the instructions are stated the opposite, you must have misread it.
Click to expand...
Click to collapse
hi, so luckily i had oem unlocking checked before this happened, but after the october update ive been stuck in bootloop.
ive tried both sideloading the ota in recovery, and also full firmware flash via fastboot.
after several attempts at both, i can't seem to access the recovery and bootloop persists.
any ideas?
[pixel sailfish never been rooted]
ku81na said:
hi, so luckily i had oem unlocking checked before this happened, but after the october update ive been stuck in bootloop.
ive tried both sideloading the ota in recovery, and also full firmware flash via fastboot.
after several attempts at both, i can't seem to access the recovery and bootloop persists.
any ideas?
[pixel sailfish never been rooted]
Click to expand...
Click to collapse
Have you looked into the Dueces recovery scrip?
https://forum.xda-developers.com/pi...ol-deuces-bootloop-recovery-flashing-t3704761
no dice. appreciate the suggestion though
ku81na said:
no dice. appreciate the suggestion though
Click to expand...
Click to collapse
if you can confirm a couple things for me....
Are you actually getting into the recovery, but not seeing any "items"; because in stock recovery, you just see a broken/dead android image, and only get selections revealed/not-hidden but holding the volume-up & power button at the same time momentarily.
But, then again, you claim that you have attempted to "sideload the ota in recovery", so I imagine you already did this…but then, again again, you don’t describe what “error” or outcome actually happened and it could possibly be that, when you attempted, you just couldn’t or didn’t know how to get into the stock recovery…
Also, the recovery resides in the boot partition; I suggest you download the Full Factory image file (from the Google Developers site), extract it until you can find the boot.img, then manually flash it to overwrite and maybe fix the boot & recovery; to further explain, copy the extracted “boot.img” file to platform-tools folder where adb and fastboot reside, then run the command “fastboot flash boot boot.img” – although, if the flash-all is successfully executed, it would be doing this anyways…..
Which brings me to my next thing…if you could edit the “flash-all.bat” file and remove the word “exit” at the end – and for that matter, if you wish to save your data, remove the -w as well – and if you could please copy the output/log of you running the flash-all; usually this resolves everything & it all, so maybe it’s here that something is going wrong…
And running Deuce’s famous rescue script has saved/recovered countless people and their device (taimen)…it definitely is a good idea to attempt it…
But, then again, this is assuming that you made sure to run (and successfully execute) the fastboot command “fastboot flashing unlock” and/or (depending on your bootloader version) “fastboot flashing unlock_critical”.
Good luck, hopefully you can get back to me/us on some of this stuff, and hopefully all this ends up being helpful…
simplepinoi177 said:
if you can confirm a couple things for me....
Are you actually getting into the recovery, but not seeing any "items"; because in stock recovery, you just see a broken/dead android image, and only get selections revealed/not-hidden but holding the volume-up & power button at the same time momentarily.
But, then again, you claim that you have attempted to "sideload the ota in recovery", so I imagine you already did this…but then, again again, you don’t describe what “error” or outcome actually happened and it could possibly be that, when you attempted, you just couldn’t or didn’t know how to get into the stock recovery…
Also, the recovery resides in the boot partition; I suggest you download the Full Factory image file (from the Google Developers site), extract it until you can find the boot.img, then manually flash it to overwrite and maybe fix the boot & recovery; to further explain, copy the extracted “boot.img” file to platform-tools folder where adb and fastboot reside, then run the command “fastboot flash boot boot.img” – although, if the flash-all is successfully executed, it would be doing this anyways…..
Which brings me to my next thing…if you could edit the “flash-all.bat” file and remove the word “exit” at the end – and for that matter, if you wish to save your data, remove the -w as well – and if you could please copy the output/log of you running the flash-all; usually this resolves everything & it all, so maybe it’s here that something is going wrong…
And running Deuce’s famous rescue script has saved/recovered countless people and their device (taimen)…it definitely is a good idea to attempt it…
But, then again, this is assuming that you made sure to run (and successfully execute) the fastboot command “fastboot flashing unlock” and/or (depending on your bootloader version) “fastboot flashing unlock_critical”.
Good luck, hopefully you can get back to me/us on some of this stuff, and hopefully all this ends up being helpful…
Click to expand...
Click to collapse
yes i've tried everything you've suggested (flashing boot separately/removing exit from flash-all/running deuces script), however i haven't been able to access the recovery since i last messaged so i haven't been able to retry an ota flash from recovery. (the screen is all black and a green line of fuzz blinks across the middle of the screen when holding power and volume up) i did however get into it successfully once, and when i did there were no errors at all.
the strange thing is there are no errors when flashing either. it just does not get passed "Google" without rebooting. i just tried another flash-all after flashing unlock & unlock_critical so here is the full log in case im missing something:
target reported max download size of 536870912 bytes
sending 'bootloader_b' (32480 KB)...
OKAY [ 0.847s]
writing 'bootloader_b'...
(bootloader) Valid bootloader version.
(bootloader) Flashing active slot "_b"
(bootloader) Flashing active slot "_b"
OKAY [ 4.107s]
finished. total time: 4.965s
rebooting into bootloader...
OKAY [ 0.046s]
finished. total time: 0.051s
target reported max download size of 536870912 bytes
sending 'radio_b' (57156 KB)...
OKAY [ 1.434s]
writing 'radio_b'...
OKAY [ 0.458s]
finished. total time: 1.903s
rebooting into bootloader...
OKAY [ 0.050s]
finished. total time: 0.055s
target reported max download size of 536870912 bytes
archive does not contain 'boot.sig'
archive does not contain 'boot_other.img'
archive does not contain 'recovery.img'
archive does not contain 'system.sig'
archive does not contain 'system.sig'
archive does not contain 'vendor.sig'
archive does not contain 'vendor_other.img'
wiping userdata...
Creating filesystem with parameters:
Size: 26663190528
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 6509568
Block groups: 199
Reserved block group size: 1024
Created filesystem with 11/1630208 inodes and 146354/6509568 blocks
--------------------------------------------
Bootloader Version...: 8996-012001-1908071822
Baseband Version.....: 8996-130361-1905270421
Serial Number........: FXXXXXXXXXXX
--------------------------------------------
checking product...
OKAY [ 0.050s]
checking version-bootloader...
OKAY [ 0.046s]
checking version-baseband...
OKAY [ 0.046s]
sending 'boot_b' (30793 KB)...
OKAY [ 0.797s]
writing 'boot_b'...
OKAY [ 0.294s]
erasing 'system_b'...
OKAY [ 0.316s]
sending sparse 'system_b' 1/4 (524284 KB)...
OKAY [ 13.692s]
writing 'system_b' 1/4...
OKAY [ 3.460s]
sending sparse 'system_b' 2/4 (524284 KB)...
OKAY [ 13.802s]
writing 'system_b' 2/4...
OKAY [ 3.481s]
sending sparse 'system_b' 3/4 (524284 KB)...
OKAY [ 13.816s]
writing 'system_b' 3/4...
OKAY [ 3.451s]
sending sparse 'system_b' 4/4 (461052 KB)...
OKAY [ 11.950s]
writing 'system_b' 4/4...
OKAY [ 3.087s]
erasing 'system_a'...
OKAY [ 0.246s]
sending 'system_a' (298348 KB)...
OKAY [ 7.005s]
writing 'system_a'...
OKAY [ 2.036s]
erasing 'vendor_b'...
OKAY [ 0.112s]
sending 'vendor_b' (259272 KB)...
OKAY [ 6.400s]
writing 'vendor_b'...
OKAY [ 1.747s]
Setting current slot to 'b'...
OKAY [ 0.081s]
erasing 'userdata'...
OKAY [ 1.853s]
sending 'userdata' (138957 KB)...
OKAY [ 3.089s]
writing 'userdata'...
OKAY [ 1.293s]
rebooting...
finished. total time: 92.497s
Press any key to exit...
ku81na said:
yes i've tried everything you've suggested (flashing boot separately/removing exit from flash-all/running deuces script), however i haven't been able to access the recovery since i last messaged so i haven't been able to retry an ota flash from recovery. (the screen is all black and a green line of fuzz blinks across the middle of the screen when holding power and volume up) i did however get into it successfully once, and when i did there were no errors at all.
the strange thing is there are no errors when flashing either. it just does not get passed "Google" without rebooting. i just tried another flash-all after flashing unlock & unlock_critical so here is the full log in case im missing something:
target reported max download size of 536870912 bytes
sending 'bootloader_b' (32480 KB)...
OKAY [ 0.847s]
writing 'bootloader_b'...
(bootloader) Valid bootloader version.
(bootloader) Flashing active slot "_b"
(bootloader) Flashing active slot "_b"
OKAY [ 4.107s]
finished. total time: 4.965s
rebooting into bootloader...
OKAY [ 0.046s]
finished. total time: 0.051s
target reported max download size of 536870912 bytes
sending 'radio_b' (57156 KB)...
OKAY [ 1.434s]
writing 'radio_b'...
OKAY [ 0.458s]
finished. total time: 1.903s
rebooting into bootloader...
OKAY [ 0.050s]
finished. total time: 0.055s
target reported max download size of 536870912 bytes
archive does not contain 'boot.sig'
archive does not contain 'boot_other.img'
archive does not contain 'recovery.img'
archive does not contain 'system.sig'
archive does not contain 'system.sig'
archive does not contain 'vendor.sig'
archive does not contain 'vendor_other.img'
wiping userdata...
Creating filesystem with parameters:
Size: 26663190528
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 6509568
Block groups: 199
Reserved block group size: 1024
Created filesystem with 11/1630208 inodes and 146354/6509568 blocks
--------------------------------------------
Bootloader Version...: 8996-012001-1908071822
Baseband Version.....: 8996-130361-1905270421
Serial Number........: FXXXXXXXXXXX
--------------------------------------------
checking product...
OKAY [ 0.050s]
checking version-bootloader...
OKAY [ 0.046s]
checking version-baseband...
OKAY [ 0.046s]
sending 'boot_b' (30793 KB)...
OKAY [ 0.797s]
writing 'boot_b'...
OKAY [ 0.294s]
erasing 'system_b'...
OKAY [ 0.316s]
sending sparse 'system_b' 1/4 (524284 KB)...
OKAY [ 13.692s]
writing 'system_b' 1/4...
OKAY [ 3.460s]
sending sparse 'system_b' 2/4 (524284 KB)...
OKAY [ 13.802s]
writing 'system_b' 2/4...
OKAY [ 3.481s]
sending sparse 'system_b' 3/4 (524284 KB)...
OKAY [ 13.816s]
writing 'system_b' 3/4...
OKAY [ 3.451s]
sending sparse 'system_b' 4/4 (461052 KB)...
OKAY [ 11.950s]
writing 'system_b' 4/4...
OKAY [ 3.087s]
erasing 'system_a'...
OKAY [ 0.246s]
sending 'system_a' (298348 KB)...
OKAY [ 7.005s]
writing 'system_a'...
OKAY [ 2.036s]
erasing 'vendor_b'...
OKAY [ 0.112s]
sending 'vendor_b' (259272 KB)...
OKAY [ 6.400s]
writing 'vendor_b'...
OKAY [ 1.747s]
Setting current slot to 'b'...
OKAY [ 0.081s]
erasing 'userdata'...
OKAY [ 1.853s]
sending 'userdata' (138957 KB)...
OKAY [ 3.089s]
writing 'userdata'...
OKAY [ 1.293s]
rebooting...
finished. total time: 92.497s
Press any key to exit..
.
Click to expand...
Click to collapse
Curious....
I would suggest you try Deuce's script -- again, it has assisted and recovered countless taimens. And, if that doesn't help, I would suggest you try temporarily booting into TWRP custom recovery. If you do not know how to do that, download the TWRP .img file from twrp.me (you'll have to direct yourself to the Google Pixel 2 XL [taimen] section), put it where you put the flash-all and other image files, then run the fastboot command "fastboot boot twrp.img" (replace "twrp.img" with the actual filename of the twrp image file). There you can erase/format the system and/or other partitions, or even "repair" the filesystem! You can also run adb commands, so you might have some luck and be able to install/flash an OTA image file as well....
Good luck and hope this helps...!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
riceDroid for OnePlus 9RT [martini]
What is riceDroid?
* RiceDroid is an opensource android operating system that aims to bring the necessary system modifications while being neat, stable and fast.
What is RiseUI?
* RiseUI is the name for our firmware skin/user interface.
Terminology
* The RICE in the project refers to rice(food) itself, but in a sense it is indeed the term RICING in linux.
Based on Android 13 | Tiramisu
What's working?
Wi-Fi
RIL
NFC
Mobile data
GPS
Camera
Flashlight
Camcorder
Bluetooth
Fingerprint reader
Lights
Sound/vibration
Known Issues
• You tell me
You tell me
DON'T FLASH GAPPS, THEY'RE ALREADY INCLUDED
Download link: IMAGES / OTA
Spoiler: Flashing requirements (IMPORTANT)
- If you have OnePlus 9RT CN (MT2110) , You can only flash it if you converted to OOS before, Don't flash it over ColorOS 12.1
Spoiler: Flashing requirements (IMPORTANT)
- You have to be on OxygenOS 12.1 C.07 to be able to flash this rom
- Those who are on OOS13 or those who downgraded from OOS13 to OOS12 in the past:
- YOU HAVE TO INSTALL FLASH A12 ROLLBACK PACKAGE TWICE ( device needs to reboot after each flash session ), this will make sure oos13 is completely gone from your device else it will cause a brick.
- If you rollbacked before from OOS13 to OOS12.1 , Flash Rollback package once so that OOS12.1 get written in the inactive slot
Steps to properly rollback and cross-check u don't have oos13 on your inactive slots
Spoiler: Flashing instructions
Unlocked the bootloader of you device (there are pretty much guides around XDA, go give a check)
A working usb cable
A computer
platform-tools installed (v32 or above)
A backup of your data
A brain (jk, but, make sure you know what you are doing)
Let's begin
Download the Images zip
Boot into Bootloader mode (hold power + both vol until you see fastboot mode logo)
- use adb reboot bootloader from system if you cant boot manually
fastboot -w
fastboot update filename.zip
Done
Spoiler: Instructions for updating
Download OTA zip on pc
Reboot to recovery Select "Apply update" Select "Apply from ADB"
Now on you pc use command := adb sideload <drag drop file here>
It will take around 5 mins to install
Note: Dont panic if update stops installing at 47% After update is installed ,You will get a confirmation on PC Now you can reboot and enjoy your updated os
Support Group
Android OS version: 13.0.0
Security patch level: 05-11-2022
Build author/Device Maintainer: inferno0230
Special thanks to abhinavgupta371 for helping out
Firmware source code: https://github.com/RiceDroid
Kernel source code: https://github.com/Abhinavgupta371/kernel_oneplus_sm8350
Firmware created by: The riceDroid Team
Device Changelogs: (24/11/22)
-Fixed Face unlock
-Fixed "Long press on fingerprint sensor to unlock phone" not working
-Added More UDFPS icon
@inferno0230 Please check your PM inbox. Thank you.
-Regards: Badger50
hmm. Oneplus 9RT mt2111 here, coming from A12.1 c.07
No success with this install, Using your instructions I get:
Code:
Info: Disable heap-based policy
Info: Debug level = 1
Info: Trim is disabled
Info: Set conf for android
Info: Segments per section = 1
Info: Sections per zone = 1
Info: sector size = 512
Info: total sectors = 470920600 (229941 MB)
Info: zone aligned segment0 blkaddr: 512
Info: add quota type = 0 => 4
Info: add quota type = 1 => 5
[f2fs_init_sit_area: 626] Filling sit area at offset 0x00600000
[f2fs_init_nat_area: 660] Filling nat area at offset 0x01a00000
[f2fs_write_root_inode:1274] Writing root inode (hot node), 2b800 0 200 at offset 0x00178176
[f2fs_write_default_quota:1350] Writing quota data, at offset 0002be01, 0002be02
[f2fs_write_qf_inode:1407] Writing quota inode (hot node), 2b800 0 200 at offset 0x00178177
[f2fs_write_default_quota:1350] Writing quota data, at offset 0002be03, 0002be04
[f2fs_write_qf_inode:1407] Writing quota inode (hot node), 2b800 0 200 at offset 0x00178178
[f2fs_update_nat_root:1461] Writing nat root, at offset 0x00001a00
[f2fs_add_default_dentry_root:1658] Writing default dentry root, at offset 0x0002be00
Info: Overprovision ratio = 0.420%
Info: Overprovision segments = 963 (GC reserved = 484)
[f2fs_write_check_point_pack: 819] Writing main segments, cp at offset 0x00000200
[f2fs_write_check_point_pack: 975] Writing Segment summary for HOT/WARM/COLD_DATA, at offset 0x00000201
[f2fs_write_check_point_pack:1002] Writing Segment summary for HOT_NODE, at offset 0x00000202
[f2fs_write_check_point_pack:1014] Writing Segment summary for WARM_NODE, at offset 0x00000203
[f2fs_write_check_point_pack:1025] Writing Segment summary for COLD_NODE, at offset 0x00000204
[f2fs_write_check_point_pack:1033] Writing cp page2, at offset 0x00000205
[f2fs_write_check_point_pack:1053] Writing NAT bits pages, at offset 0x000003fe
[f2fs_write_check_point_pack:1074] Writing cp page 1 of checkpoint pack 2, at offset 0x00000400
[f2fs_write_check_point_pack:1093] Writing cp page 2 of checkpoint pack 2, at offset 0x00000405
[f2fs_write_super_block:1126] Writing super block, at offset 0x00000000
Info: format successful
Sending 'userdata' (85 KB) OKAY [ 0.005s]
Writing 'userdata' OKAY [ 0.013s]
Erasing 'metadata' OKAY [ 4.919s]
mke2fs 1.46.2 (28-Feb-2021)
Creating filesystem with 4096 4k blocks and 4096 inodes
Allocating group tables: done
Writing inode tables: done
Creating journal (1024 blocks): done
Writing superblocks and filesystem accounting information: done
Sending 'metadata' (44 KB) OKAY [ 0.003s]
Writing 'metadata' OKAY [ 0.006s]
Finished. Total time: 6.010s
C:\platform-tools\platform-tools>fastboot update RiceDroid-userdebug-031022.inferno0230.zip
--------------------------------------------
Bootloader Version...:
Baseband Version.....:
Serial Number........: 25551e57
--------------------------------------------
extracting android-info.txt (0 MB) to RAM...
Checking 'product' OKAY [ 0.004s]
Setting current slot to 'b' OKAY [ 0.009s]
extracting boot.img (192 MB) to disk... took 0.344s
archive does not contain 'boot.sig'
Sending 'boot_b' (196608 KB) OKAY [ 4.961s]
Writing 'boot_b' OKAY [ 0.408s]
archive does not contain 'init_boot.img'
extracting dtbo.img (24 MB) to disk... took 0.032s
archive does not contain 'dtbo.sig'
Sending 'dtbo' (24576 KB) OKAY [ 0.621s]
Writing 'dtbo' OKAY [ 0.028s]
archive does not contain 'dt.img'
archive does not contain 'pvmfw.img'
archive does not contain 'recovery.img'
extracting vbmeta.img (0 MB) to disk... took 0.000s
archive does not contain 'vbmeta.sig'
Sending 'vbmeta' (8 KB) OKAY [ 0.001s]
Writing 'vbmeta' OKAY [ 0.001s]
extracting vbmeta_system.img (0 MB) to disk... took 0.001s
archive does not contain 'vbmeta_system.sig'
Sending 'vbmeta_system' (4 KB) OKAY [ 0.001s]
Writing 'vbmeta_system' OKAY [ 0.001s]
extracting vbmeta_vendor.img (0 MB) to disk... took 0.001s
archive does not contain 'vbmeta_vendor.sig'
Sending 'vbmeta_vendor' (4 KB) OKAY [ 0.001s]
Writing 'vbmeta_vendor' OKAY [ 0.001s]
extracting vendor_boot.img (192 MB) to disk... took 0.247s
archive does not contain 'vendor_boot.sig'
Sending 'vendor_boot' (196608 KB) OKAY [ 4.963s]
Writing 'vendor_boot' OKAY [ 0.375s]
extracting super_empty.img (0 MB) to disk... took 0.000s
Rebooting into fastboot OKAY [ 0.001s]
< waiting for any device >
And then it returns to AOSP recovery, I tried two types of platform tools v32 and above, no success
edit: to those that hit this error like me and want to recover, use the ColorOS to OxyOS A.07+ fastboot migration firmware on the other thread, and use install.bat/sh in bootloader fastboot
(if that doesn't work make sure you switch to slot b - this is what I had to do trying to figure that out blind - either use fastbootenhance or the boota/b switch commands to get to alternate boot partition)
hello, i would like to make roms for this phone, can you please give me the tree files? device tree kernal tree and all that? i coudln't find it anywhere onliine, thank you!!!!. Also really thanks for the rom, I'm installing rn.
strelokcyka said:
hmm. Oneplus 9RT mt2111 here, coming from A12.1 c.07
No success with this install, Using your instructions I get:
Code:
Info: Disable heap-based policy
Info: Debug level = 1
Info: Trim is disabled
Info: Set conf for android
Info: Segments per section = 1
Info: Sections per zone = 1
Info: sector size = 512
Info: total sectors = 470920600 (229941 MB)
Info: zone aligned segment0 blkaddr: 512
Info: add quota type = 0 => 4
Info: add quota type = 1 => 5
[f2fs_init_sit_area: 626] Filling sit area at offset 0x00600000
[f2fs_init_nat_area: 660] Filling nat area at offset 0x01a00000
[f2fs_write_root_inode:1274] Writing root inode (hot node), 2b800 0 200 at offset 0x00178176
[f2fs_write_default_quota:1350] Writing quota data, at offset 0002be01, 0002be02
[f2fs_write_qf_inode:1407] Writing quota inode (hot node), 2b800 0 200 at offset 0x00178177
[f2fs_write_default_quota:1350] Writing quota data, at offset 0002be03, 0002be04
[f2fs_write_qf_inode:1407] Writing quota inode (hot node), 2b800 0 200 at offset 0x00178178
[f2fs_update_nat_root:1461] Writing nat root, at offset 0x00001a00
[f2fs_add_default_dentry_root:1658] Writing default dentry root, at offset 0x0002be00
Info: Overprovision ratio = 0.420%
Info: Overprovision segments = 963 (GC reserved = 484)
[f2fs_write_check_point_pack: 819] Writing main segments, cp at offset 0x00000200
[f2fs_write_check_point_pack: 975] Writing Segment summary for HOT/WARM/COLD_DATA, at offset 0x00000201
[f2fs_write_check_point_pack:1002] Writing Segment summary for HOT_NODE, at offset 0x00000202
[f2fs_write_check_point_pack:1014] Writing Segment summary for WARM_NODE, at offset 0x00000203
[f2fs_write_check_point_pack:1025] Writing Segment summary for COLD_NODE, at offset 0x00000204
[f2fs_write_check_point_pack:1033] Writing cp page2, at offset 0x00000205
[f2fs_write_check_point_pack:1053] Writing NAT bits pages, at offset 0x000003fe
[f2fs_write_check_point_pack:1074] Writing cp page 1 of checkpoint pack 2, at offset 0x00000400
[f2fs_write_check_point_pack:1093] Writing cp page 2 of checkpoint pack 2, at offset 0x00000405
[f2fs_write_super_block:1126] Writing super block, at offset 0x00000000
Info: format successful
Sending 'userdata' (85 KB) OKAY [ 0.005s]
Writing 'userdata' OKAY [ 0.013s]
Erasing 'metadata' OKAY [ 4.919s]
mke2fs 1.46.2 (28-Feb-2021)
Creating filesystem with 4096 4k blocks and 4096 inodes
Allocating group tables: done
Writing inode tables: done
Creating journal (1024 blocks): done
Writing superblocks and filesystem accounting information: done
Sending 'metadata' (44 KB) OKAY [ 0.003s]
Writing 'metadata' OKAY [ 0.006s]
Finished. Total time: 6.010s
C:\platform-tools\platform-tools>fastboot update RiceDroid-userdebug-031022.inferno0230.zip
--------------------------------------------
Bootloader Version...:
Baseband Version.....:
Serial Number........: 25551e57
--------------------------------------------
extracting android-info.txt (0 MB) to RAM...
Checking 'product' OKAY [ 0.004s]
Setting current slot to 'b' OKAY [ 0.009s]
extracting boot.img (192 MB) to disk... took 0.344s
archive does not contain 'boot.sig'
Sending 'boot_b' (196608 KB) OKAY [ 4.961s]
Writing 'boot_b' OKAY [ 0.408s]
archive does not contain 'init_boot.img'
extracting dtbo.img (24 MB) to disk... took 0.032s
archive does not contain 'dtbo.sig'
Sending 'dtbo' (24576 KB) OKAY [ 0.621s]
Writing 'dtbo' OKAY [ 0.028s]
archive does not contain 'dt.img'
archive does not contain 'pvmfw.img'
archive does not contain 'recovery.img'
extracting vbmeta.img (0 MB) to disk... took 0.000s
archive does not contain 'vbmeta.sig'
Sending 'vbmeta' (8 KB) OKAY [ 0.001s]
Writing 'vbmeta' OKAY [ 0.001s]
extracting vbmeta_system.img (0 MB) to disk... took 0.001s
archive does not contain 'vbmeta_system.sig'
Sending 'vbmeta_system' (4 KB) OKAY [ 0.001s]
Writing 'vbmeta_system' OKAY [ 0.001s]
extracting vbmeta_vendor.img (0 MB) to disk... took 0.001s
archive does not contain 'vbmeta_vendor.sig'
Sending 'vbmeta_vendor' (4 KB) OKAY [ 0.001s]
Writing 'vbmeta_vendor' OKAY [ 0.001s]
extracting vendor_boot.img (192 MB) to disk... took 0.247s
archive does not contain 'vendor_boot.sig'
Sending 'vendor_boot' (196608 KB) OKAY [ 4.963s]
Writing 'vendor_boot' OKAY [ 0.375s]
extracting super_empty.img (0 MB) to disk... took 0.000s
Rebooting into fastboot OKAY [ 0.001s]
< waiting for any device >
And then it returns to AOSP recovery, I tried two types of platform tools v32 and above, no success
edit: to those that hit this error like me and want to recover, use the ColorOS to OxyOS A.07+ fastboot migration firmware on the other thread, and use install.bat/sh in bootloader fastboot
(if that doesn't work make sure you switch to slot b - this is what I had to do trying to figure that out blind - either use fastbootenhance or the boota/b switch commands to get to alternate boot partition)
Click to expand...
Click to collapse
If you are able to boot into aosp recovery you can use recovery rom and sideload it
Also, were u on oos12.1 at the time of flashing rom?
inferno0230 said:
If you are able to boot into aosp recovery you can use recovery rom and sideload it
Also, were u on oos12.1 at the time of flashing rom?
Click to expand...
Click to collapse
As I said. Followed instructions and was coming from stock oos a12.1 c0.7. Only can assume the boot partition was loaded on the wrong one
(that explains the errors but I'm not game enough to try the whole process again and now I'm kind of stuck back of Android 11 due to recovering from the issue. Maybe when someone uploads a c.07 fastboit firmware I will try again but for me OTA is broken.)
this rom is actually really great. i love this rom, i just have a biit problem with the vibration sensor, its not as good as stock, bit i got like a thousand things better then the stock rom, thanks a lot man. Keep up the good work!!
strelokcyka said:
As I said. Followed instructions and was coming from stock oos a12.1 c0.7. Only can assume the boot partition was loaded on the wrong one
(that explains the errors but I'm not game enough to try the whole process again and now I'm kind of stuck back of Android 11 due to recovering from the issue. Maybe when someone uploads a c.07 fastboit firmware I will try again but for me OTA is broken.)
Click to expand...
Click to collapse
Sorry to stray once again from the rom but this will be the last post -- but its important for those who get stuck for any reason like I did
You can update from stuck OTA, using the Oxygen Updater via playstore, they supply an alternative apk link to help flash the zip without using the OOS Settings.
你好，我是来自中国的用户，在这里我的5G没办法正常使用，就算是打开了也仅仅显示4G，希望伙计可以改进一下，还有就是 更新的时候可以在这个论坛发一下吗？源锻造里看不懂，但是我是真心喜欢这个系统，比我之前用过的都简洁，好看。感谢！
How is going the battery life of this ROM?
battery life is great for me, running everything, wifi bluetooth 120 hertz, high brightness, running many apps, only daily driver, (lite) gamaing but last charge 21 hours ago, im not super heavy user, but i can last 2 days, plus charging so so fast too
How can I return to stock rom. Pls help
hi i got the OS 12 air update today i install it into my phone but the phone was buggy freezing something not right, i try to downgrade back to OS 11 using local update, this option is no longer available so i did factory reset the phone stuck on fastboot
i try TOOL ALL IN ONE didnt work i try fastboot rom nothing works anymore any idea how to fix it
Do you want to wipe all the data ( Reccomended )[Y/N]?y
Erasing 'userdata' OKAY [ 0.125s]
F2FS-tools: mkfs.f2fs Ver: 1.12.0 (2018-11-12)
Info: Disable heap-based policy
Info: Debug level = 1
Info: Trim is disabled
Info: Set conf for android
Info: Segments per section = 1
Info: Sections per zone = 1
Info: sector size = 512
Info: total sectors = 203820072 (99521 MB)
Info: zone aligned segment0 blkaddr: 512
Info: add quota type = 0 => 4
Info: add quota type = 1 => 5
[f2fs_init_sit_area: 535] Filling sit area at offset 0x00600000
[f2fs_init_nat_area: 569] Filling nat area at offset 0x00e00000
[f2fs_write_root_inode:1147] Writing root inode (hot node), 1b800 0 200 at offset 0x00112640
[f2fs_write_default_quota:1223] Writing quota data, at offset 0001be01, 0001be02
[f2fs_write_qf_inode:1318] Writing quota inode (hot node), 1b800 0 200 at offset 0x00112641
[f2fs_write_default_quota:1223] Writing quota data, at offset 0001be03, 0001be04
[f2fs_write_qf_inode:1318] Writing quota inode (hot node), 1b800 0 200 at offset 0x00112642
[f2fs_update_nat_root:1372] Writing nat root, at offset 0x00000e00
[f2fs_add_default_dentry_root:1567] Writing default dentry root, at offset 0x0001be00
Info: Overprovision ratio = 0.640%
Info: Overprovision segments = 635 (GC reserved = 320)
[f2fs_write_check_point_pack: 713] Writing main segments, cp at offset 0x00000200
[f2fs_write_check_point_pack: 850] Writing Segment summary for HOT/WARM/COLD_DATA, at offset 0x00000201
[f2fs_write_check_point_pack: 877] Writing Segment summary for HOT_NODE, at offset 0x00000202
[f2fs_write_check_point_pack: 889] Writing Segment summary for WARM_NODE, at offset 0x00000203
[f2fs_write_check_point_pack: 900] Writing Segment summary for COLD_NODE, at offset 0x00000204
[f2fs_write_check_point_pack: 908] Writing cp page2, at offset 0x00000205
[f2fs_write_check_point_pack: 928] Writing NAT bits pages, at offset 0x000003fe
[f2fs_write_check_point_pack: 949] Writing cp page 1 of checkpoint pack 2, at offset 0x00000400
[f2fs_write_check_point_pack: 968] Writing cp page 2 of checkpoint pack 2, at offset 0x00000405
[f2fs_write_super_block:1001] Writing super block, at offset 0x00000000
Info: format successful
Sending 'userdata' (85 KB) OKAY [ 0.011s]
Writing 'userdata' OKAY [ 0.004s]
Erasing 'metadata' OKAY [ 0.007s]
Erase successful, but not automatically formatting.
File system type raw not supported.
Finished. Total time: 7.984s
Sending 'boot_b' (98304 KB) OKAY [ 2.218s]
Writing 'boot_b' OKAY [ 0.367s]
Finished. Total time: 2.669s
Sending 'dtbo' (16384 KB) OKAY [ 0.371s]
Writing 'dtbo' OKAY [ 0.067s]
Finished. Total time: 0.471s
Sending 'modem_b' (165396 KB) OKAY [ 3.737s]
Writing 'modem_b' OKAY [ 0.901s]
Finished. Total time: 4.785s
Sending 'reserve' (250164 KB) OKAY [ 5.607s]
Writing 'reserve' FAILED (remote: '(reserve_b) No such partition')
fastboot: error: Command failed
Sending 'recovery' (98304 KB) OKAY [ 2.200s]
Writing 'recovery' OKAY [ 0.442s]
Finished. Total time: 2.726s
Sending 'vbmeta' (8 KB) OKAY [ 0.013s]
Writing 'vbmeta' OKAY [ 0.003s]
Finished. Total time: 0.035s
Sending 'vbmeta_system' (4 KB) OKAY [ 0.009s]
Writing 'vbmeta_system' OKAY [ 0.004s]
Finished. Total time: 0.031s
Rebooting into fastboot OKAY [ 0.003s]
< waiting for any device >
fastboot: error: Failed to boot into userspace fastboot; one or more components might be unbootable.
Sending 'abl' (1164 KB) OKAY [ 0.039s]
Writing 'abl' FAILED (remote: 'Flashing is not allowed for Critical Partitions.
')
fastboot: error: Command failed
Sending 'aop' (200 KB) OKAY [ 0.019s]
Writing 'aop' FAILED (remote: 'Flashing is not allowed for Critical Partitions.
')
fastboot: error: Command failed
Sending 'bluetooth' (828 KB) OKAY [ 0.028s]
Writing 'bluetooth' FAILED (remote: 'Flashing is not allowed for Critical Partitions.
')
fastboot: error: Command failed
Sending 'cmnlib' (384 KB) OKAY [ 0.017s]
Writing 'cmnlib' FAILED (remote: 'Flashing is not allowed for Critical Partitions.
')
fastboot: error: Command failed
Sending 'cmnlib64' (500 KB) OKAY [ 0.018s]
Writing 'cmnlib64' FAILED (remote: 'Flashing is not allowed for Critical Partitions.
')
fastboot: error: Command failed
Sending 'devcfg' (52 KB) OKAY [ 0.009s]
Writing 'devcfg' FAILED (remote: 'Flashing is not allowed for Critical Partitions.
')
fastboot: error: Command failed
Sending 'dsp' (65536 KB) OKAY [ 1.468s]
Writing 'dsp' FAILED (remote: 'Flashing is not allowed for Critical Partitions.
')
fastboot: error: Command failed
Sending 'hyp' (480 KB) OKAY [ 0.024s]
Writing 'hyp' FAILED (remote: 'Flashing is not allowed for Critical Partitions.
')
fastboot: error: Command failed
Sending 'imagefv' (20 KB) OKAY [ 0.007s]
Writing 'imagefv' FAILED (remote: 'Flashing is not allowed for Critical Partitions.
')
fastboot: error: Command failed
Sending 'keymaster' (248 KB) OKAY [ 0.020s]
Writing 'keymaster' FAILED (remote: 'Flashing is not allowed for Critical Partitions.
')
fastboot: error: Command failed
Sending 'LOGO' (6540 KB) OKAY [ 0.161s]
Writing 'LOGO' OKAY [ 0.044s]
Finished. Total time: 0.232s
Sending 'multiimgoem' (16 KB) OKAY [ 0.015s]
Writing 'multiimgoem' FAILED (remote: 'Flashing is not allowed for Critical Partitions.
')
fastboot: error: Command failed
Sending 'odm' (912 KB) OKAY [ 0.028s]
Writing 'odm' FAILED (remote: '(odm_b) No such partition')
fastboot: error: Command failed
Sending 'oem_stanvbk' (2480 KB) OKAY [ 0.065s]
Writing 'oem_stanvbk' OKAY [ 0.017s]
Finished. Total time: 0.105s
Sending 'opproduct' (586912 KB) OKAY [ 13.173s]
Writing 'opproduct' FAILED (remote: 'Flashing is not allowed for Critical Partitions.
')
fastboot: error: Command failed
Sending 'qupfw' (72 KB) OKAY [ 0.016s]
Writing 'qupfw' FAILED (remote: 'Flashing is not allowed for Critical Partitions.
')
fastboot: error: Command failed
Sending 'storsec' (24 KB) OKAY [ 0.009s]
Writing 'storsec' FAILED (remote: 'Flashing is not allowed for Critical Partitions.
')
fastboot: error: Command failed
Sending 'tz' (3092 KB) OKAY [ 0.078s]
Writing 'tz' FAILED (remote: 'Flashing is not allowed for Critical Partitions.
')
fastboot: error: Command failed
Sending 'uefisecapp' (124 KB) OKAY [ 0.017s]
Writing 'uefisecapp' FAILED (remote: 'Flashing is not allowed for Critical Partitions.
')
fastboot: error: Command failed
Sending 'xbl' (3120 KB) OKAY [ 0.075s]
Writing 'xbl' FAILED (remote: 'Flashing is not allowed for Critical Partitions.
')
fastboot: error: Command failed
Sending 'xbl_config' (124 KB) OKAY [ 0.013s]
Writing 'xbl_config' FAILED (remote: 'Flashing is not allowed for Critical Partitions.
')
fastboot: error: Command failed
Invalid sparse file format at header magic
Sending sparse 'system' 1/3 (784708 KB) OKAY [ 17.615s]
Writing 'system' FAILED (remote: 'Partition not found')
fastboot: error: Command failed
Invalid sparse file format at header magic
Sending sparse 'vendor' 1/2 (785569 KB)
if tis happen to any of you i have fix the problem i guess by luck i give up trying all the old methods nothing work
i download twrp-3.6.0_11-0-hotdog.img
i use cmd command fastboot flash boot twrp-3.6.0_11-0-hotdog.img
i repeat the command few times then the phone reboot to the languages screen from there i click at
format system
OS 12 been formatted and my phone back to OS11
note TWPR never open but i dont care as long the problem fixed
Starting from here in your log.
Code:
Rebooting into fastboot OKAY [ 0.003s]
< waiting for any device >
fastboot: error: Failed to boot into userspace fastboot; one or more components might be unbootable.
Fastboot mode was not available so, you were rebooted back into bootloader mode, critical partitions can not be flashed in bootloader mode.
Newer devices have two modes for fastboot commands.
bootloader (fastboot).
fastboot (fastboot_d, fastbootd, or some other variation of the name).
Depending on the device, you might be able to enter fastboot_d by command.
adb reboot fastboot or fastboot reboot fastboot
Some devices you have to enter recovery and select an option to reboot to fastboot mode.
To enter recovery from command line.
recovery (recovery)
adb reboot recovery or fastboot reboot recovery
---
With 7T, fastbootd mode is part of the recovery image.
So you need to flash a compatible version of stock recovery or a custom recovery that supports fastbootd mode.
Then you you can run the fastboot update in bootloader mode.
The update can then switch into fastbootd mode when needed.
---
I updated my 7T a few weeks ago from 11 to 12 but, I used the local update option..
MAGISK MODULE ❯ Universal SafetyNet Fix 2.3.1 - [ xdaThread ] - Post #2,514
Cheers.
PS.
For reference.
The fastbootd (fastboot_d) mode (for the lack of a better description) is a low level recovery.
This mode allows flashing secure (critical) partitions that are not available to flash in bootloader.
Years ago..
Pixel 2XL, OnePlus 5T and some other devices supported unlock critical that allowed flashing secure (critical) in regular fastboot (bootloader).
This shift to fastbootd never made sense to me because what is more critical than being able to flash the actual bootloader. ¯\_(ツ)_/¯