ANDROID 4.4.4 CM11S XNPH3O0 && Incremental && XNPH33R
{
"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"
}
**PLEASE READ ALL OF THIS! INCLUDING POST 2**
Hello again fellow Android enthusiasts! With the new update rolling out slowly for our beloved One Plus,update XNPH3O0. I thought I would make this thread for you. If you are trying to sideload the new update and keep getting a error message saying xxx.xml or xxx.apk is missing/modified,whatever.If you have TWRP installed already you can either sideload the updates or just flash them as you would any other ROM or MOD.
¥Changelog¥
- 8/11 OTA XNPH3O0
- 8/11 Incremental XNPH3O0
- 8/22 Added new OTA XNPH33R
- 8/27 Uploaded system images with instructions to get back to stock
=============FILES============
Update XNPH3O0
***Update 1***
Mirror 1 - http://bit.ly/1nMahIE
=============================
XNPH3O0 Incremental
***Update 2***
MEGA - http://bit.ly/1uFQX8l
=============================
8/22 Update XNPH33R
***Update 3***
MEGA - http://bit.ly/YIQa9m
=============================
****NOTE***READ ME***YES YOU***If you run into a bootloop. Wipe both caches and try flashing again. If you get any FC then try setting permissions with another cache wipe. If you tried everything,including a Google search (yeah right),and you are that special person you can download these special files. With beauty of of having a device like the OPO you can get back up and running in no time by using factory 4.4.4 images, found → https://cyngn.com/products/oneplusone/This is explained below
¥ If you have tried the above file(or you have no clue what to do)and you are still having problems there's one sure fire way to get back to 100% stock.¥This method will work no matter what position you are in. All you have to do is get to fastboot mode. With the download link I've provided, you can get your OP back up and running in a few minutes. I even included all the latest fastboot/ADB files from the Android SDK in the zip. Just follow the below directions and download this file (Uploading now)
This will wipe your device. EVERYTHING, including your internal sdcard. So if you need something make sure you make the proper backups.
1) Unzip the folder and click the "cmd.exe" file.
2) Type the bolded/blue fastboot commands below IN ORDER! I strongly suggest copy and paste these.
3) Profit !
This will zap you to 4.4.4 with the stock recovery. You will get the 33R update as soon as you sign in and setup.You will need to flash TWRP after this is done if you choose to.
C:\Users\Dave\Desktop\cm-11.0-XNPH30O-bacon-signed-fastboot>fastboot flash modem NON-HLOS.bin
target reported max download size of 536870912 bytes
sending 'modem' (56337 KB)...
OKAY [ 2.120s]
writing 'modem'...
OKAY [ 0.853s]
finished. total time: 2.974s
C:\Users\Dave\Desktop\cm-11.0-XNPH30O-bacon-signed-fastboot>fastboot flash sbl1 sbl1.mbn
target reported max download size of 536870912 bytes
sending 'sbl1' (295 KB)...
OKAY [ 0.015s]
writing 'sbl1'...
OKAY [ 0.013s]
finished. total time: 0.028s
C:\Users\Dave\Desktop\cm-11.0-XNPH30O-bacon-signed-fastboot>fastboot flash dbi sdi.mbn
target reported max download size of 536870912 bytes
sending 'dbi' (11 KB)...
OKAY [ 0.004s]
writing 'dbi'...
OKAY [ 0.010s]
finished. total time: 0.014s
C:\Users\Dave\Desktop\cm-11.0-XNPH30O-bacon-signed-fastboot>fastboot flash aboot emmc_appsboot.mbn
target reported max download size of 536870912 bytes
sending 'aboot' (376 KB)...
OKAY [ 0.017s]
writing 'aboot'...
OKAY [ 0.015s]
finished. total time: 0.033s
C:\Users\Dave\Desktop\cm-11.0-XNPH30O-bacon-signed-fastboot>fastboot flash rpm rpm.mbn
target reported max download size of 536870912 bytes
sending 'rpm' (185 KB)...
OKAY [ 0.010s]
writing 'rpm'...
OKAY [ 0.012s]
finished. total time: 0.022s
C:\Users\Dave\Desktop\cm-11.0-XNPH30O-bacon-signed-fastboot>fastboot flash tz tz.mbn
target reported max download size of 536870912 bytes
sending 'tz' (283 KB)...
OKAY [ 0.013s]
writing 'tz'...
OKAY [ 0.013s]
finished. total time: 0.026s
C:\Users\Dave\Desktop\cm-11.0-XNPH30O-bacon-signed-fastboot>fastboot flash LOGO logo.bin
target reported max download size of 536870912 bytes
sending 'LOGO' (9591 KB)...
OKAY [ 0.362s]
writing 'LOGO'...
OKAY [ 0.148s]
finished. total time: 0.510s
C:\Users\Dave\Desktop\cm-11.0-XNPH30O-bacon-signed-fastboot>fastboot update -w cm-11.0-XNPH30O-bacon
-signed-fastboot.zip
target reported max download size of 536870912 bytes
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...:
Baseband Version.....:
Serial Number........:
--------------------------------------------
checking product...
OKAY [ 0.003s]
sending 'boot' (5606 KB)...
OKAY [ 0.215s]
writing 'boot'...
OKAY [ 0.092s]
sending 'recovery' (7458 KB)...
OKAY [ 0.284s]
writing 'recovery'...
OKAY [ 0.132s]
erasing 'system'...
OKAY [ 0.301s]
sending sparse 'system' (524112 KB)...
OKAY [ 20.693s]
writing 'system'...
OKAY [ 25.144s]
sending sparse 'system' (250752 KB)...
OKAY [ 9.879s]
writing 'system'...
OKAY [ 8.375s]
erasing 'userdata'...
OKAY [ 2.381s]
formatting 'userdata' partition...
Creating filesystem with parameters:
Size: 59914792960
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 14627635
Block groups: 447
Reserved block group size: 1024
Created filesystem with 11/3661824 inodes and 275906/14627635 blocks
sending 'userdata' (141075 KB)...
writing 'userdata'...
OKAY [ 18.852s]
erasing 'cache'...
OKAY [ 0.034s]
formatting 'cache' partition...
Creating filesystem with parameters:
Size: 536870912
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 2048
Label:
Blocks: 131072
Block groups: 4
Reserved block group size: 31
Created filesystem with 11/32768 inodes and 4206/131072 blocks
sending 'cache' (10432 KB)...
writing 'cache'...
OKAY [ 0.884s]
rebooting...
finished. total time: 87.287s
C:\Users\Dave\Desktop\cm-11.0-XNPH30O-bacon-signed-fastboot> PROFIT! If you got this far you can breath now!!!!!!
Please remember myself or XDA Developers are not responsible for your device if anything would happen to it. This includes bootloops,force closes, thermonuclear war with Russia,your alarm clock not going off and you get fired from work or you're phone jumping up and running down the street.
I don't ask for donations, their for charity. All I ask is you smash the thanks button.
DirtyDroidX
¥ Please Read Tips/Facts ¥
- You will get a small update (incremental) after you are on 4.4.4. Just select update and it will update via TWRP or stock recovery. You CAN NOT flash the tiny update first. You must flash in order. The small incremental update is under "UPDATE TWO" in the OP. Remember to flash them in order.
- I made this for rooted peeps so they can update without putting back any little changes they made.
- If you bootloop,or something is not functioning right blah,blah,blah. Please post as much details as you can; what carrier your on,what country,the process you took.
- Read through all the posts. Most likely you're question has been answered already.
- If you don't have your Bootloader unlocked...well....SMH.
-DISABLE Xposed!!!!! This can cause conflicts. Uninstall Xposed through the app itself.
- This is for the CM11s Odexed version.....obviously. If your on any thing else ppl are going to laugh at you.
- If your system is heavily modified. Their is a chance you will boot loop.
- Always Always Always make a full nandroid backup.
- Update added XNPH33R
- If you find yourself in a bootloop or any other problems arise please Google "android logcats" . This helps when posting problems.
- Added a custom zip folder with factory images and a slimmed down fastboot/ADB sdk binaries with directions to get back to 100% stock.
Trying your option 2 zip same as Ludestar I am experiencing a bootloop. I have wiped cache and data before sideloading.
I just dloaded your zip and in android opened twrp and selected your zip to flash and let twrp do its thing. During reboot from the flash dalvik was rebuilt and now I'm on kk 444. Sweet. No Sideload needed.
Edit - one last thing...had to reboot to recovery and flash supersu.
Okay this time I did not sideload it, but directly placed it onto my phone. Using TWRP flashed it and now it booted.
Mine if I add the download link for option 2 in my guide thread?
Transmitted via Bacon
ahmaddiablo said:
Okay this time I did not sideload it, but directly placed it onto my phone. Using TWRP flashed it and now it booted.
Click to expand...
Click to collapse
Lol I was just going to tell you to use TWRP [emoji106] . Glad you got it working.
Sent from my OnePlus using Tapatalk
timmaaa said:
Mine if I add the download link for option 2 in my guide thread?
Transmitted via Bacon
Click to expand...
Click to collapse
Nope go right ahead. If you could put a link back to the original thread to. That would be cool.
Also if anyone can mirror these files I would appreciate it.
Sent from my OnePlus using Tapatalk
This is the only one that worked for me, thank you!
Please remember myself or XDA Developers are not responsible for your device if anything would happen to it. This includes bootloops,force closes, thermonuclear war with Russia lol
DirtyDroidX said:
Hello again fellow Android enthusiasts! With the new update rolling out slowly for our beloved OPO. I thought I would make this thread for you. If you are trying to sideload the new update and keep getting a error message saying xxx.xml or xxx.apk is missing/modified,whatever.
You have two options at this point.
¥ All you need to do is swap out the update script if you have modified anything. I have taken out the checksums in the update-script so it will work. **Note** this will remove any modification you made to any XML files or added any system apps. You can download just the meta folder below.
Option 1 - http://bit.ly/1sw1baq
¥ If you want the whole OTA you can go with option two. This is the whole update zip with the hacked update-script already in it. All you have to do is boot to recovery, go to "Advanced" then select ADB side load, then from a cmd prompt type "adb sideload filename.zip"
¥ Sidenote ¥
Shhhh, don't tell anyone bit you can also just flash this in TWRP instead of hooking up to a computer!
Option 2- http://bit.ly/1kXFhL3[[/COLOR]/url]... fixed my problem when I edited the mixer.xml
Click to expand...
Click to collapse
Thz dude this realy solve my problem! thz!!!
sharp2G said:
"AudioFX has stopped" on clicking the OK button the message appears within a second rendering the device unusable.
I changed mixer.xml or something and this happened... Any suggestions on how to fix this? I am rooted with TWRP. I have no knowledge of adb or fast boot so I am a complete noob.
*** Could I download Option 2 -> place in a folder -> boot to TWRP -> flash .zip -> wipe cache/dalvik -> reboot
Would this work to fixed my problem when I edited the mixer.xml
Click to expand...
Click to collapse
Yes option 2 would be a good route for you to take Or flash my Okay Google zip in my other thread it will put the correct mixer_paths.xml file in place.
Sent from my OnePlus using Tapatalk
DirtyDroidX said:
Yes option 2 would be a good route for you to take Or flash my Okay Google zip in my other thread it will put the correct mixer_paths.xml file in place.
Sent from my OnePlus using Tapatalk
Click to expand...
Click to collapse
What is your other thread because I just flashed Option 2 and I still get the "Unforunately, AudioFX has stopped" message...
It worked! Had the mixer_paths issue as I modified it with a flashable zip from the forums to boost volume. This got me updated though, downloaded bottom one, flashed in twrp
sharp2G said:
What is your other thread because I just flashed Option 2 and I still get the "Unforunately, AudioFX has stopped" message...
Click to expand...
Click to collapse
Its in the same forum. I'm driving ATM. Just click on my name and look at threads I've started.
Sent from my OnePlus using Tapatalk
DirtyDroidX said:
Its in the same forum. I'm driving ATM. Just click on my name and look at threads I've started.
Sent from my OnePlus using Tapatalk
Click to expand...
Click to collapse
Issue resolved. Many thanks for your help.
sharp2G said:
Issue resolved. Many thanks for your help.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2828980
How did you fix it?
Sent from my OnePlus using Tapatalk
DirtyDroidX said:
http://forum.xda-developers.com/showthread.php?t=2828980
How did you fix it?
Sent from my OnePlus using Tapatalk
Click to expand...
Click to collapse
I flashed the default setting zip file from
http://forum.xda-developers.com/oneplus-one/themes-apps/mod-volume-increase-mod-oneplus-one-t2835010
Can someone link me to the stock systemUI.apk? I used option 2, and now I keep getting a "SystemUI has stopped" error.
Related
Hello,
My name is Rahul. This is the first time I am posting.
I flashed the latest factory image for Android Kitkat onto the Nexus 4. the image was occam KRT16O. I followed the instructions and used fastboot on mac and ran the flash-all.sh script that was provided.
The log of the script was as indicated below and the device rebooted. However, it was stuck in the boot animation for a long time.
What can I do next? The options I can consider are:
1. force reboot the nexus 4 by holding the power button [if that would work] and flashing the image again.
2. go to the bootloader (if reboot works) and switch away to the previous ROM (I was using CM and PAC for some time now flashing them nightly) and wait for a new more days.
I would love to try the new factory image for KitKat on my phone and would appreciate if you could provide some direction.
Thanks in advance for your help.
- Rahul
silverbook:Nexus4Root rahul$ ./flash-all.sh
ERROR: could not get pipe properties
sending 'bootloader' (2203 KB)... OKAY
writing 'bootloader'... OKAY
ERROR: could not get pipe properties
rebooting into bootloader... OKAY
sending 'radio' (45537 KB)... OKAY
writing 'radio'... OKAY
rebooting into bootloader... OKAY
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: MAKOZ30d
Baseband Version.....: M9615A-CEFWMAZM-2.0.1700.97
Serial Number........: 024443a016985273
--------------------------------------------
checking product... OKAY
checking version-bootloader... OKAY
checking version-baseband... OKAY
sending 'boot' (6336 KB)... OKAY
writing 'boot'... OKAY
sending 'recovery' (6884 KB)... OKAY
writing 'recovery'... OKAY
sending 'system' (700500 KB)... OKAY
writing 'system'... OKAY
erasing 'userdata'... OKAY
erasing 'cache'... OKAY
rebooting...
Rebooted and trying again...fingers crossed.
i would download again, look down in the log and u see that it just erased usersdata partition(it needs to erase and flash userdata.img)
I have the exact same problem, please let me know what what the solution for you.
eran- said:
I have the exact same problem, please let me know what what the solution for you.
Click to expand...
Click to collapse
I opened the zip file image-occam-krt16o.zip and found userdata.img and i used fastboot to flash userdata with that image. I am still waiting for my phone to move ahead from the boot animation...crossed fingers.
rreiki said:
I opened the zip file image-occam-krt16o.zip and found userdata.img and i used fastboot to flash userdata with that image. I am still waiting for my phone to move ahead from the boot animation...crossed fingers.
Click to expand...
Click to collapse
I guess that you, like me, took the wipe flag off the fastboot bat file right?
Well I was told that 4.3 --> 4.4 needs a full wipe so I put that -w back in place and everything works, my 4.4 works
and my phone looks fresher than fresh.
Good luck
opssemnik said:
i would download again, look down in the log and u see that it just erased usersdata partition(it needs to erase and flash userdata.img)
Click to expand...
Click to collapse
opssemnik, I downloaded the file again, unzipped and tried again. It gave me the same log. I then opened the zip which contained user data.img and flashed it and it still waits at the boot animation for a long time. I think its already been twenty minutes.
Is there anything else I can try?
Thanks for your response.
rreiki said:
I opened the zip file image-occam-krt16o.zip and found userdata.img and i used fastboot to flash userdata with that image. I am still waiting for my phone to move ahead from the boot animation...crossed fingers.
Click to expand...
Click to collapse
rreiki said:
opssemnik, I downloaded the file again, unzipped and tried again. It gave me the same log. I then opened the zip which contained user data.img and flashed it and it still waits at the boot animation for a long time. I think its already been twenty minutes.
Is there anything else I can try?
Thanks for your response.
Click to expand...
Click to collapse
Did you fully wiped your device?
eran- said:
Did you fully wiped your device?
Click to expand...
Click to collapse
Yes. The flash-all.sh uses -w which fully wipes the device. I remember reading about -w somewhere.
rreiki said:
Yes. The flash-all.sh uses -w which fully wipes the device. I remember reading about -w somewhere.
Click to expand...
Click to collapse
I am now trying to download the latest adb and fastboot downloading the sdk and will retry flashing the image.
rreiki said:
I am now trying to download the latest adb and fastboot downloading the sdk and will retry flashing the image.
Click to expand...
Click to collapse
okay, interesting observation. I downloaded the new platform-tools (adb/fastboot) and re-ran flash-all.sh. the log looked like the one below.
and my phone started!!!!
silverbook:android rahul$ ./flash-all.sh
sending 'bootloader' (2203 KB)...
OKAY [ 0.115s]
writing 'bootloader'...
OKAY [ 0.287s]
finished. total time: 0.402s
rebooting into bootloader...
OKAY [ 0.001s]
finished. total time: 0.001s
< waiting for device >
sending 'radio' (45537 KB)...
OKAY [ 1.889s]
writing 'radio'...
OKAY [ 2.535s]
finished. total time: 4.424s
rebooting into bootloader...
OKAY [ 0.001s]
finished. total time: 0.001s
< waiting for device >
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: MAKOZ30d
Baseband Version.....: M9615A-CEFWMAZM-2.0.1700.97
Serial Number........: 024443a016985273
--------------------------------------------
checking product...
OKAY [ 0.002s]
checking version-bootloader...
OKAY [ 0.002s]
checking version-baseband...
OKAY [ 0.002s]
sending 'boot' (6336 KB)...
OKAY [ 0.203s]
writing 'boot'...
OKAY [ 0.339s]
sending 'recovery' (6884 KB)...
OKAY [ 0.235s]
writing 'recovery'...
OKAY [ 0.395s]
erasing 'system'...
OKAY [ 0.690s]
sending 'system' (700500 KB)...
OKAY [ 22.043s]
writing 'system'...
OKAY [ 40.629s]
erasing 'userdata'...
OKAY [ 0.572s]
formatting 'userdata' partition...
Creating filesystem with parameters:
Size: 14129561600
Block size: 4096
Blocks per group: 32768
Inodes per group: 8144
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 3449600
Block groups: 106
Reserved block group size: 847
Created filesystem with 11/863264 inodes and 95427/3449600 blocks
sending 'userdata' (137438 KB)...
writing 'userdata'...
OKAY [ 13.523s]
erasing 'cache'...
OKAY [ 0.022s]
formatting 'cache' partition...
Creating filesystem with parameters:
Size: 587202560
Block size: 4096
Blocks per group: 32768
Inodes per group: 7168
Inode size: 256
Journal blocks: 2240
Label:
Blocks: 143360
Block groups: 5
Reserved block group size: 39
Created filesystem with 11/35840 inodes and 4616/143360 blocks
sending 'cache' (10984 KB)...
writing 'cache'...
OKAY [ 1.082s]
rebooting...
finished. total time: 79.749s
I had the same problem, came from PA 3.99 and flashed the kitkat google image and phone got stuck in bootloop. Only way i could fix it was to get the new sdk studio and use the fastboot from that
the last log u gave looks like mine so i guess its ok, but u were using a really outdated adb huh? im using the minimal adb + fastboot from like 6 to 7 months ago(so the fastboot / adb is from that time witch means is old) and i can flash the stock images
rreiki said:
okay, interesting observation. I downloaded the new platform-tools (adb/fastboot) and re-ran flash-all.sh. the log looked like the one below.
and my phone started!!!!
silverbook:android rahul$ ./flash-all.sh
sending 'bootloader' (2203 KB)...
OKAY [ 0.115s]
writing 'bootloader'...
OKAY [ 0.287s]
finished. total time: 0.402s
rebooting into bootloader...
OKAY [ 0.001s]
finished. total time: 0.001s
< waiting for device >
sending 'radio' (45537 KB)...
OKAY [ 1.889s]
writing 'radio'...
OKAY [ 2.535s]
finished. total time: 4.424s
rebooting into bootloader...
OKAY [ 0.001s]
finished. total time: 0.001s
< waiting for device >
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: MAKOZ30d
Baseband Version.....: M9615A-CEFWMAZM-2.0.1700.97
Serial Number........: 024443a016985273
--------------------------------------------
checking product...
OKAY [ 0.002s]
checking version-bootloader...
OKAY [ 0.002s]
checking version-baseband...
OKAY [ 0.002s]
sending 'boot' (6336 KB)...
OKAY [ 0.203s]
writing 'boot'...
OKAY [ 0.339s]
sending 'recovery' (6884 KB)...
OKAY [ 0.235s]
writing 'recovery'...
OKAY [ 0.395s]
erasing 'system'...
OKAY [ 0.690s]
sending 'system' (700500 KB)...
OKAY [ 22.043s]
writing 'system'...
OKAY [ 40.629s]
erasing 'userdata'...
OKAY [ 0.572s]
formatting 'userdata' partition...
Creating filesystem with parameters:
Size: 14129561600
Block size: 4096
Blocks per group: 32768
Inodes per group: 8144
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 3449600
Block groups: 106
Reserved block group size: 847
Created filesystem with 11/863264 inodes and 95427/3449600 blocks
sending 'userdata' (137438 KB)...
writing 'userdata'...
OKAY [ 13.523s]
erasing 'cache'...
OKAY [ 0.022s]
formatting 'cache' partition...
Creating filesystem with parameters:
Size: 587202560
Block size: 4096
Blocks per group: 32768
Inodes per group: 7168
Inode size: 256
Journal blocks: 2240
Label:
Blocks: 143360
Block groups: 5
Reserved block group size: 39
Created filesystem with 11/35840 inodes and 4616/143360 blocks
sending 'cache' (10984 KB)...
writing 'cache'...
OKAY [ 1.082s]
rebooting...
finished. total time: 79.749s
Click to expand...
Click to collapse
I place all files in "platform tools" in the SDK and re-ran flash-all.sh. from there and works!!!! Thanks!
fidozgz said:
I place all files in "platform tools" in the SDK and re-ran flash-all.sh. from there and works!!!! Thanks!
Click to expand...
Click to collapse
can you send your "platform tools" somehow? I downloaded everything today and tried flashing 4.4. Stuck at boot screen. How long did you have to wait before it went past the boot screen?
prongs_rajat said:
can you send your "platform tools" somehow? I downloaded everything today and tried flashing 4.4. Stuck at boot screen. How long did you have to wait before it went past the boot screen?
Click to expand...
Click to collapse
just ask him for the link as of which he got it from probably easier.
Edit: May I ask you guys a question if you skimmed through this forum prior to making a decision to upgrade you would see so many people with the same issue and post day in and day out about flashing images. I am confused as to why those of you want to flash images instead of just flashing through a custom recovery. There is no difference? other than less headaches from what I see
playya said:
just ask him for the link as of which he got it from probably easier.
Edit: May I ask you guys a question if you skimmed through this forum prior to making a decision to upgrade you would see so many people with the same issue and post day in and day out about flashing images. I am confused as to why those of you want to flash images instead of just flashing through a custom recovery. There is no difference? other than less headaches from what I see
Click to expand...
Click to collapse
Yeah I'm kind of a noob. I installed CWM recovery. I boot into recovery and I see a bunch of options. Which one will fix my phone?
When I select "wipe data/factory reset", the output is the following:
-- Wiping Data....
Formatting /data...
Formatting /cache...
Formatting /sd-ext...
Formatting /sdcard/.android_secure...
E:unknown volume "/sdcard/.android_secure"
Data wipe complete.
Click to expand...
Click to collapse
prongs_rajat said:
Yeah I'm kind of a noob. I installed CWM recovery. I boot into recovery and I see a bunch of options. Which one will fix my phone?
When I select "wipe data/factory reset", the output is the following:
Click to expand...
Click to collapse
factory reset with stock recovery after flashing everything
playya said:
factory reset with stock recovery after flashing everything
Click to expand...
Click to collapse
Already tried that. Didn't work. Always gets stuck at the boot animation. That's why I thought of trying a different recovery. Neither works
prongs_rajat said:
Already tried that. Didn't work. Always gets stuck at the boot animation. That's why I thought of trying a different recovery. Neither works
Click to expand...
Click to collapse
May have to start from scratch since this is how all others have gotten past that screen or simply why not flash a zip. So much easier than dealing with images
Sent from my Nexus 4 using Tapatalk
Free Beer* for anyone who can help!
I have a serious problem with my nexus 7 (2012) which I have been researching and working on for many months now to no avail. For this reason I am offering a free beer to anyone who can help (t's&c's apply)!
Background:
The device has stock 4.2.2 rooted installed along with Multirom which has CM10, paranoid android and Ubuntu (desktop).
All this ran fine for a while. I then noticed that if I made any change to the stock rom, update an app, download an app, change the wallpaper, download a file to any part of the filesystem... that when I rebooted the tablet that change would not be there... The wallpaper would be back as it was or the file simply didn't exist! It was as if the filesystem was mounted as non - persistent.
So I tried the other rooms on the tablet and realised they would not boot. All except Ubuntu which was working fine however doesn't mount the internal storage so I couldn't test any further.
I attempted to re flash back to stock. Using flashboot I cleared the cache, system, user data etc and had no errors and then flashed the stock rom. After rebooting my old system appeared to my surprise.
I have tried since then to re flash everything. Recovery won't update (currently TWRP) and the only time I get any error message is when trying to re flash the bootloader which is currently 4.18, everything seems to go well and then "signature match" appears on the tablet screen and it hangs leaving an error in the fastboot terminal reading "Remote: ()"
If anyone can help me fix this issue then the beer is yours... The only stipulation is you have to be in Ireland to claim it but what better excuse for a holiday
Thanks in advance.
Kieran
I have just used Wug's Toolkit to "Flash Stock + Unroot"
Below is th terminal output:
Code:
Flash Stock + Unroot...
--------------------------------------------------------------
erasing 'boot'...
OKAY [ 0.020s]
finished. total time: 0.020s
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 0.020s]
finished. total time: 0.020s
erasing 'recovery'...
OKAY [ 0.020s]
finished. total time: 0.020s
******** Did you mean to fastboot format this partition?
erasing 'system'...
OKAY [ 0.020s]
finished. total time: 0.020s
******** Did you mean to fastboot format this partition?
erasing 'userdata'...
OKAY [ 0.030s]
finished. total time: 0.030s
sending 'bootloader' (2096 KB)...
OKAY [ 0.270s]
writing 'bootloader'...
OKAY [ 0.590s]
finished. total time: 0.860s
rebooting into bootloader...
OKAY [ 0.020s]
finished. total time: 0.020s
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: 4.18
Baseband Version.....: N/A
Serial Number........: 015d21d914481613
--------------------------------------------
checking product...
OKAY [ 0.040s]
checking version-bootloader...
OKAY [ 0.020s]
sending 'boot' (4944 KB)...
OKAY [ 0.610s]
writing 'boot'...
OKAY [ 0.160s]
sending 'recovery' (5446 KB)...
OKAY [ 0.670s]
writing 'recovery'...
OKAY [ 0.180s]
erasing 'system'...
OKAY [ 0.020s]
sending 'system' (471804 KB)...
OKAY [ 55.586s]
writing 'system'...
OKAY [ 20.822s]
erasing 'userdata'...
OKAY [ 0.030s]
formatting 'userdata' partition...
Creating filesystem with parameters:
Size: 14442037248
Block size: 4096
Blocks per group: 32768
Inodes per group: 8176
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 3525888
Block groups: 108
Reserved block group size: 863
Created filesystem with 11/883008 inodes and 96825/3525888 bloc
sending 'userdata' (137526 KB)...
writing 'userdata'...
OKAY [ 24.063s]
erasing 'cache'...
OKAY [ 0.010s]
formatting 'cache' partition...
Creating filesystem with parameters:
Size: 464519168
Block size: 4096
Blocks per group: 32768
Inodes per group: 7088
Inode size: 256
Journal blocks: 1772
Label:
Blocks: 113408
Block groups: 4
Reserved block group size: 31
Created filesystem with 11/28352 inodes and 3654/113408 blocks
sending 'cache' (9052 KB)...
writing 'cache'...
OKAY [ 1.580s]
rebooting...
finished. total time: 103.951s
Booting up your freshly flashed stock device...
--------------------------------------------------------------
Wait for your device to finish booting up...
- It may appear to be boot looping; just wait...
- It could take 5-10 minutes; please be patient...
When its finally booted back up, please remember
to re-enable USB debugging if you plan on using
the toolkit to perform other operations.
NOTE: If this process was too quick and your device
is still in bootloader mode, then flashing stock may
have failed or been incomplete. Simply check the
log above: if you notice it skipped steps because it
didn't meet certain requirements, like the bootloader
or baseband version, then consider enabling 'Force Flash'
mode in the toolkits options menu and trying the
'Flash Stock + Unroot' processs again. Cheers.
Press any key to exit...
I used the same stock rom I am using so I ddn't have to flash the bootloader which is an issue (see above).
I can't see any errors in that terminal, everything looks fine but when the tablet reboots it has not changed a single thing!! Multirom is still there as it was and my old rom and userdata and everything down to the crappy wallpaper I put on 8 months ago is still there!!
Can anyone PLEASE HELP!!!
So what do you want to do? Get rid of the multirom and get back to stock? If so do you care about your data?
kilometers4 said:
So what do you want to do? Get rid of the multirom and get back to stock? If so do you care about your data?
Click to expand...
Click to collapse
Exactly that! Don't care about data, just want a stock working image.
I'm having the exact same issue. Tablet reboots after 5 seconds after the lock screen loads so I thought I'd erase user data and re flash the rom. Except that it doesn't actually flash, or erase anything. I've tried toolkits and fastboot. And the log always says the flash has performed successfully but it always reboots to the same old rom, wallpaper, all data still intact.
It's almost like the partitions are write protected and won't allow any data changes.
If anyone can help with this issue, I'll double the free beer offer!
Sent from my iPhone using Tapatalk
mattsolberg said:
I'm having the exact same issue. Tablet reboots after 5 seconds after the lock screen loads so I thought I'd erase user data and re flash the rom. Except that it doesn't actually flash, or erase anything. I've tried toolkits and fastboot. And the log always says the flash has performed successfully but it always reboots to the same old rom, wallpaper, all data still intact.
It's almost like the partitions are write protected and won't allow any data changes.
If anyone can help with this issue, I'll double the free beer offer!
Sent from my iPhone using Tapatalk
Click to expand...
Click to collapse
Can I just ask, are you using multirom aswell? Your the only other person I've heard of with the problem, we should go more notes and try and narrow this down.
No multi-rom. I've found about a half dozen other threads with people experiencing the same thing. It's rare, but it's not just me. Being completely unable to wipe data has me thinking there might be a hardware issue at play.
I'll post links to some of the other threads. Thanks for offering to help. I'm willing to try anything at this point.
Sent from my iPhone using Tapatalk
---------- Post added at 01:00 PM ---------- Previous post was at 12:57 PM ----------
Four other threads describing the exact same problem:
http://forum.xda-developers.com/showthread.php?t=2588911
http://forum.xda-developers.com/showthread.php?t=2585440
http://forum.xda-developers.com/showthread.php?t=2514148
http://forum.xda-developers.com/showthread.php?t=1781250
Sent from my iPhone using Tapatalk
Okay...So I feel like a complete ID10T (IDIOT). I managed to Soft Brick Nexus 6P. Currently it goes between the white Google Logo with the unlock icon at the bottom and the "Your device software cannot be check for corruption Please lock the Bootloader." Image. I have tried using WUGFresh Toolkit to flash the files as well as just using the factory image to no avail.
I can get into TWRP but even when flashing CM13 it just sits at the white Google logo and does not continue.
Does anyone have any suggestions?
Perhaps try manually flashing factory instead of using wugfresh's toolkit. I had a similar situation and that's what got me lot of my jam, but that may have been because wugfresh's kit wasn't updated for all the marshmallow shenanigans. So make sure you're on the latest version too
jasonftfw said:
Perhaps try manually flashing factory instead of using wugfresh's toolkit. I had a similar situation and that's what got me lot of my jam, but that may have been because wugfresh's kit wasn't updated for all the marshmallow shenanigans. So make sure you're on the latest version too
Click to expand...
Click to collapse
I tried that as well. I installed the Android SDK and put the angler-mmb29m-factory-8c31db3f files in adb folder on that's on the root of C:\ and ran the flash-all.bat. It goes though the process but I still get the same bootlooping issue.
C:\adb>fastboot devices
8XV5T15B10000200 fastboot
C:\adb>flash-all
target reported max download size of 494927872 bytes
sending 'bootloader' (3526 KB)...
OKAY [ 0.137s]
writing 'bootloader'...
OKAY [ 0.208s]
finished. total time: 0.347s
rebooting into bootloader...
OKAY [ 0.125s]
finished. total time: 0.126s
target reported max download size of 494927872 bytes
sending 'radio' (48472 KB)...
OKAY [ 1.611s]
writing 'radio'...
OKAY [ 2.170s]
finished. total time: 3.782s
rebooting into bootloader...
OKAY [ 0.015s]
finished. total time: 0.017s
target reported max download size of 494927872 bytes
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
archive does not contain 'vendor.sig'
Creating filesystem with parameters:
Size: 58688266240
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 14328190
Block groups: 438
Reserved block group size: 1024
Created filesystem with 11/3588096 inodes and 271280/14328190 blocks
Creating filesystem with parameters:
Size: 104857600
Block size: 4096
Blocks per group: 32768
Inodes per group: 6400
Inode size: 256
Journal blocks: 1024
Label:
Blocks: 25600
Block groups: 1
Reserved block group size: 7
Created filesystem with 11/6400 inodes and 1438/25600 blocks
--------------------------------------------
Bootloader Version...: angler-02.45
Baseband Version.....: angler-02.50
Serial Number........: MY SN
--------------------------------------------
checking product...
OKAY [ 0.020s]
checking version-bootloader...
OKAY [ 0.020s]
checking version-baseband...
OKAY [ 0.018s]
sending 'boot' (12045 KB)...
OKAY [ 0.428s]
writing 'boot'...
OKAY [ 0.184s]
sending 'recovery' (12981 KB)...
OKAY [ 0.453s]
writing 'recovery'...
OKAY [ 0.192s]
erasing 'system'...
OKAY [ 0.402s]
sending sparse 'system' (463062 KB)...
OKAY [ 15.904s]
writing 'system'...
OKAY [ 6.511s]
sending sparse 'system' (466961 KB)...
OKAY [ 16.220s]
writing 'system'...
OKAY [ 6.804s]
sending sparse 'system' (479253 KB)...
OKAY [ 17.006s]
writing 'system'...
OKAY [ 7.519s]
sending sparse 'system' (481623 KB)...
OKAY [ 16.713s]
writing 'system'...
OKAY [ 6.772s]
sending sparse 'system' (79148 KB)...
OKAY [ 2.786s]
writing 'system'...
OKAY [ 1.134s]
sending 'vendor' (185129 KB)...
OKAY [ 6.096s]
writing 'vendor'...
OKAY [ 3.017s]
erasing 'userdata'...
OKAY [ 1.012s]
sending 'userdata' (141002 KB)...
OKAY [ 4.674s]
writing 'userdata'...
OKAY [ 2.135s]
erasing 'cache'...
OKAY [ 0.091s]
sending 'cache' (5752 KB)...
OKAY [ 0.228s]
writing 'cache'...
OKAY [ 0.107s]
rebooting...
finished. total time: 116.562s
Press any key to exit...
Click to expand...
Click to collapse
I literally mean flash manual, like type it all out, I had issues with the flash all too
jasonftfw said:
I literally mean flash manual, like type it all out, I had issues with the flash all too
Click to expand...
Click to collapse
Thanks! I will try that and report back.
I tried manually typing out all the commands and it still just bootlooping at the Google logo. It will show it for about 22 seconds and then go black for 4 seconds. Any other suggestions?
What exactly did you do to softbrick it ?
If you connect with ADB, can you dump a log while booting ?
If not: what I'd try is do a factory reset, try a boot, when it loops, boot into TWRP. Then check if there's a log in /data/tombstones
gekkehenkie11 said:
What exactly did you do to softbrick it ?
If you connect with ADB, can you dump a log while booting ?
If not: what I'd try is do a factory reset, try a boot, when it loops, boot into TWRP. Then check if there's a log in /data/tombstones
Click to expand...
Click to collapse
Well when I received it, it was on 6.0.0 (MDB08L) so I rooted it and installed xposed framework. I was trying to install the OTA update for 6.0.1 and of course it failed with TWRP, so I decided I would just factory reset and start over and that was where the problem start. Once I rebooted it started bootlooping and has been doing so every since.
mxjcmxjc said:
Well when I received it, it was on 6.0.0 (MDB08L) so I rooted it and installed xposed framework. I was trying to install the OTA update for 6.0.1 and of course it failed with TWRP, so I decided I would just factory reset and start over and that was where the problem start. Once I rebooted it started bootlooping and has been doing so every since.
Click to expand...
Click to collapse
Hmm wish I knew a way how to help you but if you flashed all partitions to factory and also did a factory reset and if that still doesnt help, then I'd be out of idea's. I'd try to dump logs like I said in my previous posts, maybe there's something in there but still, it doesn't make any sense to me, so I doubt there's something in the logs to go by but who knows. ..
Maybe though it's encryption related ? I'm still a bit confused myself there how all that fits in.
gekkehenkie11 said:
Hmm wish I knew a way how to help you but if you flashed all partitions to factory and also did a factory reset and if that still doesnt help, then I'd be out of idea's. I'd try to dump logs like I said in my previous posts, maybe there's something in there but still, it doesn't make any sense to me, so I doubt there's something in the logs to go by but who knows. ..
Maybe though it's encryption related ? I'm still a bit confused myself there how all that fits in.
Click to expand...
Click to collapse
I checked the Tombstone folder and found 10 files there. Here is the link to the dumps. I really hope it helps.
mxjcmxjc said:
I checked the Tombstone folder and found 10 files there. Here is the link to the dumps. I really hope it helps.
Click to expand...
Click to collapse
Your error is "couldn't find an OpenGL ES implementation". So what we know:
1) The kernel boots
2) System image loads, it runs libEGL.so, this lib is in your system image.
3) libEGL.so tries to access the OpenGL implementation. This stuff is located in the vendor partition. And this is where it goes wrong. It says it cant find that file. What this means ? Not really sure. It could mean that the vendor partition is not good, maybe try to flash it again ? Also, what happens if you try to make a logcat during boot ? Issue:
adb logcat > out.txt
And see if it saves something after the bootloop. Maybe there's a better hint in there.
*EDIT2* also see if the openGL implementation is even there ! It should look like this:
[email protected]:/vendor/lib64/egl # ls -al
-rw-r--r-- root root 47200 2009-01-01 04:00 eglSubDriverAndroid.so
-rw-r--r-- root root 103256 2009-01-01 04:00 libEGL_adreno.so
-rw-r--r-- root root 210776 2009-01-01 04:00 libGLESv1_CM_adreno.so
-rw-r--r-- root root 7288296 2009-01-01 04:00 libGLESv2_adreno.so
-rw-r--r-- root root 661552 2009-01-01 04:00 libq3dtools_adreno.so
-rw-r--r-- root root 361800 2009-01-01 04:00 libq3dtools_esx.so
[email protected]:/vendor/lib64/egl #
gekkehenkie11 said:
Your error is "couldn't find an OpenGL ES implementation". So what we know:
1) The kernel boots
2) System image loads, it runs libEGL.so, this lib is in your system image.
3) libEGL.so tries to access the OpenGL implementation. This stuff is located in the vendor partition. And this is where it goes wrong. It says it cant find that file. What this means ? Not really sure. It could mean that the vendor partition is not good, maybe try to flash it again ? Also, what happens if you try to make a logcat during boot ? Issue:
adb logcat > out.txt
And see if it saves something after the bootloop. Maybe there's a better hint in there.
*EDIT2* also see if the openGL implementation is even there ! It should look like this:
[email protected]:/vendor/lib64/egl # ls -al
-rw-r--r-- root root 47200 2009-01-01 04:00 eglSubDriverAndroid.so
-rw-r--r-- root root 103256 2009-01-01 04:00 libEGL_adreno.so
-rw-r--r-- root root 210776 2009-01-01 04:00 libGLESv1_CM_adreno.so
-rw-r--r-- root root 7288296 2009-01-01 04:00 libGLESv2_adreno.so
-rw-r--r-- root root 661552 2009-01-01 04:00 libq3dtools_adreno.so
-rw-r--r-- root root 361800 2009-01-01 04:00 libq3dtools_esx.so
[email protected]:/vendor/lib64/egl #
Click to expand...
Click to collapse
I'm not getting any output from logcat when trying to boot it seems.
I just sit there like this.
C:\adb>adb logcat > out.txt
- waiting for device -
mxjcmxjc said:
I'm not getting any output from logcat when trying to boot it seems.
I just sit there like this.
C:\adb>adb logcat > out.txt
- waiting for device -
Click to expand...
Click to collapse
Ok so it's not getting to that point, which makes sense I realize now, since first thing it does is trying to get display up (it's not even getting beyond that).
So, let's see if your vendor partition seems correct. boot into TWRP, connect via 'adb shell', then 'mount /vendor' and then:
Code:
ls -al /vendor/lib64/egl
and see if all the files are there that I listed in my post on the previous page of this thread
I'm having the same issue. I stupidly tried to flash the OTA update via TWRP and now the phone won't go past the Google logo. Even when I restore my backup, it still won't go past that screen.
I didn't back up the vendor partition though (didn't know that I needed to).
My phone was not rooted. All I had was the custom recovery so that I can install MoaAB.
Now I have to wait until tomorrow because my USB C to USB A cable is at work. Hopefully we can get this fixed soon.
gekkehenkie11 said:
Ok so it's not getting to that point, which makes sense I realize now, since first thing it does is trying to get display up (it's not even getting beyond that).
So, let's see if your vendor partition seems correct. boot into TWRP, connect via 'adb shell', then 'mount /vendor' and then:
Code:
ls -al /vendor/lib64/egl
and see if all the files are there that I listed in my post on the previous page of this thread
Click to expand...
Click to collapse
Sorry for the late reply...
Yes the files are there. I was able to mount the vendor partition in TWRP and then use the File Manager to see the directory.
https://www.dropbox.com/s/3yq97hs75me933m/IMG_20151211_002153.jpg?dl=0
Just another detail. Whenever I restarted the device prior to bootlooping. I would have to enter my pattern before Android would start.
Closed at OP's request.
Hey guys, I've done something wonky in TWRP and simply cant get a clean factory imagine installed. I feel like ive tried everything and am now coming here in an attempt to get some help.
At this point, I am stuck at the Google logo booting indefinitely. When I flash the latest TWRP recovery and go into it, im pretty locked down in what I can do. I cant get ANYTHING to mount, it vibrates but wont let me mount anything.
When I go into advanced wipe settings in an attempt to repair partitions there is NO system or Data present and will not let me repair. When I do repair system, i get "/sbin/efsck -fp process ended with ERROR: 16 unable to repair system" Googling brings me nothing on error 16.
Despite trying to flash a multitude of different factory images through both WugFresh and Fastboot commands I havent been able to stick. I cant even wipe/factory reset in stock recovery.
I've attempted "fastboot format userdata" as well as flashing the modified boot.img to bypass encryption (not sure how this works?) But to no avail.
Could anyone help me diagnose this a bit? Help would be greatly appreciated.
tcardozo said:
Hey guys, I've done something wonky in TWRP and simply cant get a clean factory imagine installed. I feel like ive tried everything and am now coming here in an attempt to get some help.
At this point, I am stuck at the Google logo booting indefinitely. When I flash the latest TWRP recovery and go into it, im pretty locked down in what I can do. I cant get ANYTHING to mount, it vibrates but wont let me mount anything.
When I go into advanced wipe settings in an attempt to repair partitions there is NO system or Data present and will not let me repair. When I do repair system, i get "/sbin/efsck -fp process ended with ERROR: 16 unable to repair system" Googling brings me nothing on error 16.
Despite trying to flash a multitude of different factory images through both WugFresh and Fastboot commands I havent been able to stick. I cant even wipe/factory reset in stock recovery.
I've attempted "fastboot format userdata" as well as flashing the modified boot.img to bypass encryption (not sure how this works?) But to no avail.
Could anyone help me diagnose this a bit? Help would be greatly appreciated.
Click to expand...
Click to collapse
Have you tried flashing stock?
P. S. Reading your post, I feel like you don't have much knowledge of what you're doing and especially how the things work on your Nexus. But don't worry that is nothing to be ashamed of, all of us here have been through that stage. So once we have resolved your issue, I would advise you to read the stickies in different sections of the 6P.
DJBhardwaj said:
Have you tried flashing stock?
P. S. Reading your post, I feel like you don't have much knowledge of what you're doing and especially how the things work on your Nexus. But don't worry that is nothing to be ashamed of, all of us here have been through that stage. So once we have resolved your issue, I would advise you to read the stickies in different sections of the 6P.
Click to expand...
Click to collapse
Hey there, thanks for chiming in.
Despite my hastily typed out response, I have a relatively good idea of what I am doing, though I know I am no power user.
I have attempted to flash stock. I started with MTC20F once I realized I was having problems. After that failed to boot, I downloaded MTC 19X and attempted to flash that. I first started with going through Nexus Toolkit to get it up and running but that still left me at the Google logo after booting. Wondering what was up, I threw in TWRP as a means of taking a look at my partitions after the stock install which is when I realized something was fishy. Nothing is able to be mounted, repaired or resized and TWRP is telling me that both /system and /data are not present directly after reinstalling Stock. and said their size is 0mb. Essentially it seems no internal memory is being detected at all.
Also I am prompted that there is no OS installed when i go to exit recovery, despite having just flashed it.
The problem I am having seems quite simple, but makes no sense to me.
tcardozo said:
Hey there, thanks for chiming in.
Despite my hastily typed out response, I have a relatively good idea of what I am doing, though I know I am no power user.
I have attempted to flash stock. I started with MTC20F once I realized I was having problems. After that failed to boot, I downloaded MTC 19X and attempted to flash that. I first started with going through Nexus Toolkit to get it up and running but that still left me at the Google logo after booting. Wondering what was up, I threw in TWRP as a means of taking a look at my partitions after the stock install which is when I realized something was fishy. Nothing is able to be mounted, repaired or resized and TWRP is telling me that both /system and /data are not present directly after reinstalling Stock. and said their size is 0mb. Essentially it seems no internal memory is being detected at all.
Also I am prompted that there is no OS installed when i go to exit recovery, despite having just flashed it.
The problem I am having seems quite simple, but makes no sense to me.
Click to expand...
Click to collapse
Okay, I am guessing you missed something out while flashing stock. Plus, avoid toolkits for now.
Now, try re-installing stock from the steps mentioned here: http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928/page1
Or to be simple, extract the factory image, and use flash-all.bat file on your PC. Let me know the results.
DJBhardwaj said:
Okay, I am guessing you missed something out while flashing stock. Plus, avoid toolkits for now.
Now, try re-installing stock from the steps mentioned here: http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928/page1
Or to be simple, extract the factory image, and use flash-all.bat file on your PC. Let me know the results.
Click to expand...
Click to collapse
So I opted to go through Heisenberg's tutorial so I knew if anything happened at each step, and also locked the bootloader again after.
After going through all the steps with the MTC20F factory image (verified), it takes me right to the stock recovery with the android on his back after showing me the google logo.
Edit: it seems to be staying in stock recovery for a short period of time before going through a boot cycle continuously.
Edit2: When I go into recovery, it wont let me "apply update from SD card" or "wipe data/factory reset" or "wipe cache" It says:
Can't open /dev/block/platform/soc.0/f9824900.sdhci/by-name/misc (no such file or directory)
E: failed to mount /cache (no such file or directory)
E:unknown volume for path [/sdcard]
followed by a series of errors about not being able to mount other parts
tcardozo said:
So I opted to go through Heisenberg's tutorial so I knew if anything happened at each step, and also locked the bootloader again after.
After going through all the steps with the MTC20F factory image (verified), it takes me right to the stock recovery with the android on his back after showing me the google logo
Click to expand...
Click to collapse
To be safe, keep the bootloader unlocked. As for flashing stock, try the flash-all.bat script. Just a try, and let me know.
One more thing, you flashed the correct vendor image, right?
DJBhardwaj said:
To be safe, keep the bootloader unlocked. As for flashing stock, try the flash-all.bat script. Just a try, and let me know.
One more thing, you flashed the correct vendor image, right?
Click to expand...
Click to collapse
unlocked the bootloader again. Double checked and the vendor image is directly from the factory image. Went ahead and used the flash-all.bat and came to the same result; shows Google logo for about 20 seconds then right into stock recovery.
Also check my edits above about weird behaviour.
tcardozo said:
unlocked the bootloader again. Double checked and the vendor image is directly from the factory image. Went ahead and used the flash-all.bat and came to the same result; shows Google logo for about 20 seconds then right into stock recovery.
Also check my edits above about weird behaviour.
Click to expand...
Click to collapse
The above errors that mentioned probably indicate that your partition table is the culprit here. The stock factory image should have done it already. Might want to check out the service centre?
DJBhardwaj said:
The above errors that mentioned probably indicate that your partition table is the culprit here. The stock factory image should have done it already. Might want to check out the service centre?
Click to expand...
Click to collapse
Thanks for the advice. Unfortunately I'm located in Bangkok, Thailand, without an adequate service centre around that can help with Nexus devices.
Could you post out the complete log when the factory image is being flashed?
---------- Post added at 12:11 AM ---------- Previous post was at 12:09 AM ----------
tcardozo said:
Thanks for the advice. Unfortunately I'm located in Bangkok, Thailand, without an adequate service centre around that can help with Nexus devices.
Click to expand...
Click to collapse
I could see, there is one there: http://consumer.huawei.com/en/support/service-center/index.htm
DJBhardwaj said:
Could you post out the complete log when the factory image is being flashed?
How can I grab the log?
Click to expand...
Click to collapse
tcardozo said:
DJBhardwaj said:
Could you post out the complete log when the factory image is being flashed?
How can I grab the log?
Click to expand...
Click to collapse
Once the flashing is done, you just copy down the complete content of the CMD window, or Terminal, if you're using Linux or Mac.
Click to expand...
Click to collapse
deleted
DJBhardwaj said:
tcardozo said:
Once the flashing is done, you just copy down the complete content of the CMD window, or Terminal, if you're using Linux or Mac.
Click to expand...
Click to collapse
target reported max download size of 494927872 bytes
sending 'bootloader' (3526 KB)...
OKAY [ 0.104s]
writing 'bootloader'...
OKAY [ 0.203s]
finished. total time: 0.309s
rebooting into bootloader...
OKAY [ 0.144s]
finished. total time: 0.145s
target reported max download size of 494927872 bytes
sending 'radio' (48600 KB)...
OKAY [ 1.061s]
writing 'radio'...
OKAY [ 2.168s]
finished. total time: 3.231s
rebooting into bootloader...
OKAY [ 0.008s]
finished. total time: 0.009s
target reported max download size of 494927872 bytes
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
archive does not contain 'vendor.sig'
wiping userdata...
Creating filesystem with parameters:
Size: 58688266240
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 14328190
Block groups: 438
Reserved block group size: 1024
Created filesystem with 11/3588096 inodes and 271280/14328190 blocks
wiping cache...
Creating filesystem with parameters:
Size: 104857600
Block size: 4096
Blocks per group: 32768
Inodes per group: 6400
Inode size: 256
Journal blocks: 1024
Label:
Blocks: 25600
Block groups: 1
Reserved block group size: 7
Created filesystem with 11/6400 inodes and 1438/25600 blocks
--------------------------------------------
Bootloader Version...: angler-03.54
Baseband Version.....: angler-03.61
Serial Number........: CVH7N16126000684
--------------------------------------------
checking product...
OKAY [ 0.020s]
checking version-bootloader...
OKAY [ 0.020s]
checking version-baseband...
OKAY [ 0.019s]
sending 'boot' (12201 KB)...
OKAY [ 0.288s]
writing 'boot'...
OKAY [ 0.181s]
sending 'recovery' (13133 KB)...
OKAY [ 0.298s]
writing 'recovery'...
OKAY [ 0.201s]
erasing 'system'...
OKAY [ 0.422s]
sending sparse 'system' 1/5 (478162 KB)...
OKAY [ 10.776s]
writing 'system' 1/5...
OKAY [ 6.765s]
sending sparse 'system' 2/5 (482961 KB)...
OKAY [ 10.917s]
writing 'system' 2/5...
OKAY [ 6.987s]
sending sparse 'system' 3/5 (480085 KB)...
OKAY [ 10.834s]
writing 'system' 3/5...
OKAY [ 7.450s]
sending sparse 'system' 4/5 (470078 KB)...
OKAY [ 10.611s]
writing 'system' 4/5...
OKAY [ 6.434s]
sending sparse 'system' 5/5 (55832 KB)...
OKAY [ 1.321s]
writing 'system' 5/5...
OKAY [ 0.797s]
sending 'vendor' (185181 KB)...
OKAY [ 3.997s]
writing 'vendor'...
(eventually this finishes, but I cant copy the final finished text because it closes the winow)
Click to expand...
Click to collapse
tcardozo said:
DJBhardwaj said:
target reported max download size of 494927872 bytes
sending 'bootloader' (3526 KB)...
OKAY [ 0.104s]
writing 'bootloader'...
OKAY [ 0.203s]
finished. total time: 0.309s
rebooting into bootloader...
OKAY [ 0.144s]
finished. total time: 0.145s
target reported max download size of 494927872 bytes
sending 'radio' (48600 KB)...
OKAY [ 1.061s]
writing 'radio'...
OKAY [ 2.168s]
finished. total time: 3.231s
rebooting into bootloader...
OKAY [ 0.008s]
finished. total time: 0.009s
target reported max download size of 494927872 bytes
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
archive does not contain 'vendor.sig'
wiping userdata...
Creating filesystem with parameters:
Size: 58688266240
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 14328190
Block groups: 438
Reserved block group size: 1024
Created filesystem with 11/3588096 inodes and 271280/14328190 blocks
wiping cache...
Creating filesystem with parameters:
Size: 104857600
Block size: 4096
Blocks per group: 32768
Inodes per group: 6400
Inode size: 256
Journal blocks: 1024
Label:
Blocks: 25600
Block groups: 1
Reserved block group size: 7
Created filesystem with 11/6400 inodes and 1438/25600 blocks
--------------------------------------------
Bootloader Version...: angler-03.54
Baseband Version.....: angler-03.61
Serial Number........: CVH7N16126000684
--------------------------------------------
checking product...
OKAY [ 0.020s]
checking version-bootloader...
OKAY [ 0.020s]
checking version-baseband...
OKAY [ 0.019s]
sending 'boot' (12201 KB)...
OKAY [ 0.288s]
writing 'boot'...
OKAY [ 0.181s]
sending 'recovery' (13133 KB)...
OKAY [ 0.298s]
writing 'recovery'...
OKAY [ 0.201s]
erasing 'system'...
OKAY [ 0.422s]
sending sparse 'system' 1/5 (478162 KB)...
OKAY [ 10.776s]
writing 'system' 1/5...
OKAY [ 6.765s]
sending sparse 'system' 2/5 (482961 KB)...
OKAY [ 10.917s]
writing 'system' 2/5...
OKAY [ 6.987s]
sending sparse 'system' 3/5 (480085 KB)...
OKAY [ 10.834s]
writing 'system' 3/5...
OKAY [ 7.450s]
sending sparse 'system' 4/5 (470078 KB)...
OKAY [ 10.611s]
writing 'system' 4/5...
OKAY [ 6.434s]
sending sparse 'system' 5/5 (55832 KB)...
OKAY [ 1.321s]
writing 'system' 5/5...
OKAY [ 0.797s]
sending 'vendor' (185181 KB)...
OKAY [ 3.997s]
writing 'vendor'...
(eventually this finishes, but I cant copy the final finished text because it closes the winow)
Click to expand...
Click to collapse
Seems like it is flashing fine. I am out of clues now. Would still recommend you to go to the nearest service centre.
Click to expand...
Click to collapse
Problem solved
I saw a threads from oneplus for unlock bootloader, I tried that and hope can use dual sim on my T-Mobile phone.
https://support.oneplus.com/app/answers/detail/a_id/588/~/how-to-unlock-bootloader-for-oneplus-6t-%28t-mobile-version%29"]https://support.oneplus.com/app/answers/detail/a_id/588/~/how-to-unlock-bootloader-for-oneplus-6t-%28t-mobile-version%29
I follow those steps unlocked bootloader but dual sim function is not available, so I found another threads shows dual sim is ready to use.
So I just follow his steps then ...... Phone always go recovery mode first, then reboot to initial welcome screen. It automatically turn off less than three sec.
I have no idea hoe fix that. If I just need official Rom in future, how can I fix that?
https://forums.oneplus.com/threads/no-longer-waiting-for-t-mobile-updates.942145/"]https://forums.oneplus.com/threads/no-longer-waiting-for-t-mobile-updates.942145/
{
"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"
}
This is what shows on CMD
I also tried wipe data, format devise in recovery, it not works
C:\>cd fastboot
C:\FASTBOOT>flash-all.bat
extracting android-info.txt (0 MB) to RAM...
extracting boot.img (64 MB) to disk... took 0.293s
target reported max download size of 536870912 bytes
archive does not contain 'boot.sig'
archive does not contain 'boot_other.img'
extracting dtbo.img (8 MB) to disk... took 0.044s
archive does not contain 'dtbo.sig'
archive does not contain 'dt.img'
archive does not contain 'recovery.img'
extracting system.img (2860 MB) to disk... took 21.514s
Invalid sparse file format at header magic
archive does not contain 'system.sig'
archive does not contain 'system_other.img'
extracting vbmeta.img (0 MB) to disk... took 0.002s
archive does not contain 'vbmeta.sig'
extracting vendor.img (1024 MB) to disk... took 9.014s
Invalid sparse file format at header magic
archive does not contain 'vendor.sig'
archive does not contain 'vendor_other.img'
wiping userdata...
mke2fs 1.43.3 (04-Sep-2016)
Creating filesystem with 28835840 4k blocks and 7223040 inodes
Filesystem UUID: 50d507d8-9c77-11e9-857c-a19626331dd2
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,
4096000, 7962624, 11239424, 20480000, 23887872
Allocating group tables: done
Writing inode tables: done
Creating journal (131072 blocks): done
Writing superblocks and filesystem accounting information: done
--------------------------------------------
Bootloader Version...:
Baseband Version.....:
Serial Number........: f5f0ba62
--------------------------------------------
checking product...
OKAY [ 0.002s]
sending 'boot_a' (65536 KB)...
OKAY [ 1.886s]
writing 'boot_a'...
OKAY [ 0.287s]
sending 'dtbo' (8192 KB)...
OKAY [ 0.239s]
writing 'dtbo'...
OKAY [ 0.106s]
erasing 'system_a'...
OKAY [ 0.143s]
sending sparse 'system_a' 1/6 (524284 KB)...
OKAY [ 15.506s]
writing 'system_a' 1/6...
OKAY [ 0.003s]
sending sparse 'system_a' 2/6 (499286 KB)...
OKAY [ 17.704s]
writing 'system_a' 2/6...
OKAY [ 0.003s]
sending sparse 'system_a' 3/6 (519680 KB)...
OKAY [ 17.003s]
writing 'system_a' 3/6...
OKAY [ 0.004s]
sending sparse 'system_a' 4/6 (513053 KB)...
OKAY [ 17.302s]
writing 'system_a' 4/6...
OKAY [ 0.002s]
sending sparse 'system_a' 5/6 (522296 KB)...
OKAY [ 17.746s]
writing 'system_a' 5/6...
OKAY [ 0.004s]
sending sparse 'system_a' 6/6 (220472 KB)...
OKAY [ 8.681s]
writing 'system_a' 6/6...
OKAY [ 0.004s]
sending 'vbmeta' (4 KB)...
OKAY [ 6.543s]
writing 'vbmeta'...
OKAY [ 0.004s]
sending sparse 'vendor' 1/2 (523043 KB)...
OKAY [ 15.642s]
writing 'vendor' 1/2...
OKAY [ 0.004s]
sending sparse 'vendor' 2/2 (290984 KB)...
OKAY [ 11.753s]
writing 'vendor' 2/2...
OKAY [ 0.004s]
Setting current slot to 'a'...
OKAY [ 17.400s]
erasing 'userdata'...
OKAY [ 0.722s]
sending 'userdata' (5273 KB)...
OKAY [ 0.156s]
writing 'userdata'...
OKAY [ 0.004s]
rebooting...
finished. total time: 148.965s
Press any key to exit...
Don't use Fastboot, use Qualcomm Snapdragon processor tool instead.
Fastbooted image don't wipe the modem firmware properly, instead you have bricked the modem. I found out why - the exact same thing happened to me, shuts down immediately after it gets to the welcome screen so I reflashed the phone with Qualcomm Snapdragon processor tool (it's in a thread covering the conversion of T-Mobile phone to international - https://forum.xda-developers.com/oneplus-6t/how-to/t-mobile-6t-to-international-t3888307 ), with a modified flasher software (which bypasses the checks on the phone). On the Pixel Experience ROM before I nuked the SSD with the Qualcomm Snapdragon processor tool from OnePlus, I found out why when I was struggling to fix it; wiped IMEI ID so SIM wasn't detected at all (my own fault, I wiped the /system without realizing that it would brick the modem).
Sent from my ONEPLUS 6T using Tapatalk
Dr. Mario said:
Don't use Fastboot, use Qualcomm Snapdragon processor tool instead.
Fastbooted image don't wipe the modem firmware properly, instead you have bricked the modem. I found out why - the exact same thing happened to me, shuts down immediately after it gets to the welcome screen so I reflashed the phone with Qualcomm Snapdragon processor tool (it's in a thread covering the conversion of T-Mobile phone to international - https://forum.xda-developers.com/oneplus-6t/how-to/t-mobile-6t-to-international-t3888307 ), with a modified flasher software (which bypasses the checks on the phone). On the Pixel Experience ROM before I nuked the SSD with the Qualcomm Snapdragon processor tool from OnePlus, I found out why when I was struggling to fix it; wiped IMEI ID so SIM wasn't detected at all (my own fault, I wiped the /system without realizing that it would brick the modem).
Sent from my ONEPLUS 6T using Tapatalk
Click to expand...
Click to collapse
It's back to normal and able show dual sim now.
Thanks, I spent more than 12 hrs for that, finally its back and even better.
Good, I am glad you got it fixed.
Sent from my ONEPLUS 6T using Tapatalk