This morning my phone (with a recent lineage nightly) was off when I got up and when I tried to turn it on it said my password was wrong, which I am positive it was not. For some reason I decided to "solve" the problem by going into TWRP and wiping/formating everything (including system) and then installing a fresh copy of lineage, and flashing the bootloader and vendor. Once I did that it started bootlooping, I could get into bootloader but not recovery. After some playing with it I found that the 4 cores modified twrp would work, so I tried installing some roms from there with no luck. Then tried flashing a variety of factory images, none of which work, including the 48C 7.12 image with the 4 cores boot image, as well as the same with the ex4.12 kernel flashed over it.
Is there anything I can do, or is it just time to shop for a new phone?
Dacull said:
This morning my phone (with a recent lineage nightly) was off when I got up and when I tried to turn it on it said my password was wrong, which I am positive it was not. For some reason I decided to "solve" the problem by going into TWRP and wiping/formating everything (including system) and then installing a fresh copy of lineage, and flashing the bootloader and vendor. Once I did that it started bootlooping, I could get into bootloader but not recovery. After some playing with it I found that the 4 cores modified twrp would work, so I tried installing some roms from there with no luck. Then tried flashing a variety of factory images, none of which work, including the 48C 7.12 image with the 4 cores boot image, as well as the same with the ex4.12 kernel flashed over it. Is there anything I can do, or is it just time to shop for a new phone?
Click to expand...
Click to collapse
Have you tried the workaround of disabling big cores with EX Kernel? There is an XDA thread dedicated to it. From your post I'm not sure if you disabled the cores or not.
v12xke said:
Have you tried the workaround of disabling big cores with EX Kernel? There is an XDA thread dedicated to it. From your post I'm not sure if you disabled the cores or not.
Click to expand...
Click to collapse
I didn't, I thought it has already been done. But now even the 4 core twrp just gives me a splash screen followed by a momentary page of text and then crash.
Edit: Nevermind, I misunderstood you. I installed the EX kernel from this thread.
I also just managed to somehow override whatever was crashing twrp by pushing the power button right when the text screen was showing. Flashed the EX kernel again, but still not working. I'm thinking the problem is something more than/other than the regular bootloop issue, but it is odd that only the 4 cores twrp will work.
Did you flash boot?
ItsMason said:
Did you flash boot?
Click to expand...
Click to collapse
In the most recent effort I flashed the entire n2g48c factory image but substituted the 4 cores boot image and 4 cores twrp recovery, then once I managed to get into twrp I installed the EX kernel from the thread listed above. Now, after that, it will bootloop once and then try to boot twrp which still crashes after showing the splash screen.
Dacull said:
In the most recent effort I flashed the entire n2g48c factory image but substituted the 4 cores boot image and 4 cores twrp recovery, then once I managed to get into twrp I installed the EX kernel from the thread listed above. Now, after that, it will bootloop once and then try to boot twrp which still crashes after showing the splash screen.
Click to expand...
Click to collapse
Try to fastboot FORMAT Boot, System and Userdata to see if they will format without errors. You may have a hardware issue (eg. bad eMMC). If so, the formatting process will not complete and give you a specific error code. If these 3 all complete, then flash a full image using flash-all.bat.
v12xke said:
Try to fastboot FORMAT Boot, System and Userdata to see if they will format without errors. You may have a hardware issue (eg. bad eMMC). If so, the formatting process will not complete and give you a specific error code. If these 3 all complete, then flash a full image using flash-all.bat.
Click to expand...
Click to collapse
This is what I got, I'm guessing the response on "boot" might be related to the problem?
Code:
[[email protected] angler-n2g48c]$ sudo fastboot format boot
[sudo] password for cullen:
Formatting is not supported for file system with type ''.
[[email protected] angler-n2g48c]$ sudo fastboot format system
Couldn't parse erase-block-size '0x'.
Couldn't parse logical-block-size '0x'.
Creating filesystem with parameters:
Size: 3221225472
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 12288
Label:
Blocks: 786432
Block groups: 24
Reserved block group size: 191
Created filesystem with 11/196608 inodes and 25785/786432 blocks
target reported max download size of 494927872 bytes
erasing 'system'...
OKAY [ 0.557s]
sending 'system' (52216 KB)...
OKAY [ 1.941s]
writing 'system'...
OKAY [ 0.732s]
finished. total time: 3.231s
[[email protected] angler-n2g48c]$ sudo fastboot format userdata
Couldn't parse erase-block-size '0x'.
Couldn't parse logical-block-size '0x'.
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
target reported max download size of 494927872 bytes
erasing 'userdata'...
OKAY [ 0.640s]
sending 'userdata' (141002 KB)...
OKAY [ 5.181s]
writing 'userdata'...
OKAY [ 2.109s]
finished. total time: 7.930s
Dacull said:
This is what I got, I'm guessing the response on "boot" might be related to the problem?
Click to expand...
Click to collapse
Something is up with boot. Have you tried manually flashing just the Boot.img? Sorry I meant format System, Cache & Userdata. Did you then flash a full image with flash-all.bat? Was there any error on the Cache partition? If you still can't successfully enter Recovery, you could try to fastboot boot TWRP it rather than fastboot flashing. If you can access a stable Recovery you then have ADB and can sideload, etc.
v12xke said:
Something is up with boot. Have you tried manually flashing just the Boot.img? Sorry I meant format System, Cache & Userdata. Did you then flash a full image with flash-all.bat? Was there any error on the Cache partition? If you still can't successfully enter Recovery, you could try to fastboot boot TWRP it rather than fastboot flashing. If you can access a stable Recovery you then have ADB and can sideload, etc.
Click to expand...
Click to collapse
I cache formated ok. I have been flashing everything manually, including boot, since flash-all.sh ends on an error, but manually flashing seems to work fine.
Here's the output from flash-all.sh
Code:
[[email protected] angler-n2g48c]$ sudo ./flash-all.sh
target reported max download size of 494927872 bytes
sending 'bootloader' (3544 KB)...
OKAY [ 0.152s]
writing 'bootloader'...
OKAY [ 0.209s]
finished. total time: 0.361s
rebooting into bootloader...
OKAY [ 0.022s]
finished. total time: 0.072s
target reported max download size of 494927872 bytes
sending 'radio' (48728 KB)...
OKAY [ 1.862s]
writing 'radio'...
OKAY [ 2.164s]
finished. total time: 4.026s
rebooting into bootloader...
OKAY [ 0.022s]
finished. total time: 0.072s
target reported max download size of 494927872 bytes
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
W/ziparchive( 3437): Zip: unable to allocate 2860210996 bytes at offset 0 : No space left on device
failed to extract 'system.img': I/O Error
I was able to get a stable twrp using the 4 cores twrp and fastboot boot twrp, what would I want to sideload in this situation? The ota for the whatever version I just flashed?
Dacull said:
I cache formated ok. I have been flashing everything manually, including boot, since flash-all.sh ends on an error, but manually flashing seems to work fine.
I was able to get a stable twrp using the 4 cores twrp and fastboot boot twrp, what would I want to sideload in this situation? The ota for the whatever version I just flashed?
Click to expand...
Click to collapse
Have you updated fastboot/adb recently? I don't use the whole SDK, just the stand alone binaries. Some older versions weren't able to handle the multiple system packages.... but..... I/O error sounds like bad memory to me. The current versions were published 12-May-17. On the adb, I was just going to suggest flashing SU because it modifies boot and if it found something it wasn't expecting you may receive a better error message. Now sounding more like bad onboard memory. I don't think you have a valid system partition so maybe why it's not booting. Just a guess. Many ppl with BLOD have reported manually flashing completes with no error yet the OS won't boot.
Ok, I was running a slightly older version of fastboot, but I get the exact same results after switching to the latest binary, so it looks like the phones just toast. Huge thanks for all the help, even if it didnt end up working.
Related
FIXED: It seems I flashed the files in fastboot incorrectly, as I got my 16GB back! Thank gbroon! See gbroon's post below..
http://forum.xda-developers.com/showpost.php?p=28873891&postcount=10
Okay so I got my Nexus 7 on Friday from GameStop, 16GB. Was the first one. I tried changing the DPI with the LCD Modder app to the tablet UI and this soft bricked my device, so I erased everything and restored to stock with the Nakasi factory images from Google, through fastboot,
https://developers.google.com/android/nexus/images#nakasi
I haven't downloaded much and only realized something was wrong when I tried to make a nandroid and I only had 2.3GB remaining!
I did a df on the file system before I wiped it again in adb...
Code:
1|[email protected]:/ $ df
df
Filesystem Size Used Free Blksize
/dev 487M 32K 487M 4096
/mnt/asec 487M 0K 487M 4096
/mnt/obb 487M 0K 487M 4096
/system 639M 429M 209M 4096
/cache 436M 8M 427M 4096
/data 6G 5G 332M 4096
/storage/sdcard0 6G 5G 332M 4096
So did I some how get an 8GB unit? I have checked the SN on the sticker, and in About tablet, and they both match the one on the box, and they both state 16GB.
So now I'm asking two things
1.) Is the factory image from Google only for the 8GB unit and some how partitioned the space for only 8GB?
or
2.) Could this be a much larger scale problem where they physically did not add another 8GB at the factory (aka 8GB unit), but marked it at 16GB?
Because if it's 2, then I might not be the only one with this problem...
how much space do you have left on /sdcard?
That should be where your internal storage is.
jptech said:
how much space do you have left on /sdcard?
That should be where your internal storage is.
Click to expand...
Click to collapse
6GB. See attachment.
Yeah. That's an 8gb unit.
.. Gromet
Sent from my Nexus 7 using Tapatalk 2
Gromet said:
Yeah. That's an 8gb unit.
.. Gromet
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
It's weird though then, because my box and serial numbers all indicate 16GB.
Has anyone tried using the factory restore images from Google on a 16GB unit?
I think I read something about this in the dev forum. Worth a look, but can't remember which thread
Sent from my Nexus S using xda app-developers app
dzap said:
It's weird though then, because my box and serial numbers all indicate 16GB.
Has anyone tried using the factory restore images from Google on a 16GB unit?
Click to expand...
Click to collapse
I did and I thought I was alright... I'll check when I get home
Sent from my SCH-I535 using Tapatalk 2
Perhaps when you reimaged it you used the partition layout of the 8gb model.
Sent from my Galaxy Nexus using xda premium
blackhand1001 said:
Perhaps when you reimaged it you used the partition layout of the 8gb model.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
I don't really know how. This is what I did.
Extracted the zip and got all the imgs on my desktop, Cd to my desktop and just inputted fastboot commands..
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot erase cache
dzap said:
I don't really know how. This is what I did.
Extracted the zip and got all the imgs on my desktop, Cd to my desktop and just inputted fastboot commands..
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot erase cache
Click to expand...
Click to collapse
How big is the userdata.img, it is possible you have flashed a small partition image.
edit had a look at the factory image
The factory image has another image bootloader-grouper that the scripts that come with it flash first, reboots then it applys the zip. Try again using the commands in flash-all.sh
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
fastboot flash bootloader bootloader-grouper-3.34.img
fastboot reboot-bootloader
sleep 10
fastboot -w update image-nakasi-jrn84d.zip
Could be something in bootloader-grouper you didn't have and it defaulted to the lowest size.
Sent from my Transformer while the N7 is lost in the Play Store Black Hole.
gbroon said:
How big is the userdata.img, it is possible you have flashed a small partition image.
edit had a look at the factory image
The factory image has another image bootloader-grouper that the scripts that come with it flash first, reboots then it applys the zip. Try again using the commands in flash-all.sh
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
fastboot flash bootloader bootloader-grouper-3.34.img
fastboot reboot-bootloader
sleep 10
fastboot -w update image-nakasi-jrn84d.zip
Could be something in bootloader-grouper you didn't have and it defaulted to the lowest size.
Sent from my Transformer while the N7 is lost in the Play Store Black Hole.
Click to expand...
Click to collapse
YOU SIR..YOU SIR ARE A GENTLEMAN AND A SCHOLAR. I didn't even think of looking at the .sh batch script (I don't have my Ubuntu LiveCD handy was just about to do it), but it WORKED!!
I did all those commands and my Nexus just re-popped back up as a MTP device ...with 13GB!!!
Thanks! :good: :highfive:
You have bested me...I saw that file but blew it off and didn't think of it.
Odd. I have the same issue, I just re-flashed using your commands (substituting image-nakasi-jro03d.zip for image-nakasi-jrn84d.zip, since jro03d is the only one posted currently and I assume it's newer.)
however mine still comes back as the wrong size. am I missing the magic touch?
Excellent info! Got my N7 back to being a 16Gb. Thank you a ton for this very very useful thread!
this also worked for me. I was really worried when my 32gb N7 only showed 6gb total. Running the update script in bootloader put everytthing back the way it was supposed to be.:victory::victory::victory:
Worked for me. Thanks. :good:
Exactly the same problem after 5.0.2 upgrade
Hi, I have a 16Gb nakasi/grouper Nexus 7 tablet & after I followed all of the steps in the flash-all.sh script to upgrade it to 5.0.2 my Nexus booted up running Lollipop fine. It's just that now I only have a total of 6.02Gb of space with 2.18Gb available. It's all completely stock & I haven't tried to do anything to it except let google re-download my apps again (& I don't have that many, honest). What can I do to get my 10Gb back? I don't even have enough space to do a nandroid backup any longer, or even to copy back over my Kitkat nandroid if I want to revert my tablet to a working ROM (as opposed to Lollipop, which has given me no end of grief, lags, crashes, factory resets & re-flashes, etc).
I downloaded nakasi 5.0.2 (LRX22G) from developers.google.com & following the popular FAILED (remote: (InvalidState)) problems that everyone seems to have with the 'bootloader-grouper-4.23.img' from the zip file, I downloaded a working copy from the XDA forums.
fastboot oem unlock
(bootloader) Bootloader is already unlocked
OKAY [ 0.020s]
fastboot erase boot
erasing 'boot'...
OKAY [ 0.032s]
fastboot erase cache
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 0.193s]
fastboot erase recovery
erasing 'recovery'...
OKAY [ 0.032s]
fastboot erase system
******** Did you mean to fastboot format this partition?
erasing 'system'...
OKAY [ 0.401s]
fastboot erase userdata
******** Did you mean to fastboot format this partition?
erasing 'userdata'...
OKAY [ 7.577s]
(this is one of the good bootloaders that works from the XDA forums)
fastboot flash bootloader bootloader-grouper-4.23.img
sending 'bootloader' (2100 KB)...
OKAY [ 0.267s]
writing 'bootloader'...
OKAY [ 1.226s]
fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.020s]
fastboot flash system system.img
erasing 'system'...
OKAY [ 0.108s]
sending 'system' (648819 KB)...
OKAY [ 78.230s]
writing 'system'...
OKAY [ 36.069s]
fastboot flash userdata userdata.img
erasing 'userdata'...
OKAY [ 4.931s]
sending 'userdata' (104289 KB)...
OKAY [ 12.558s]
writing 'userdata'...
OKAY [ 10.511s]
fastboot flash recovery recovery.img
sending 'recovery' (5688 KB)...
OKAY [ 0.706s]
writing 'recovery'...
OKAY [ 0.273s]
fastboot flash boot boot.img
sending 'boot' (5152 KB)...
OKAY [ 0.623s]
writing 'boot'...
OKAY [ 0.214s]
fastboot erase cache
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 0.090s]
# Then I rooted it as normal, which all worked just as it normally does
fastboot boot CF-Auto-Root-grouper-nakasi-nexus7.img
downloading 'boot.img'...
OKAY [ 1.156s]
booting...
OKAY [ 0.015s]
# Then I flashed in the latest TWRP
fastboot flash recovery openrecovery-twrp-2.8.4.0-grouper.img
sending 'recovery' (8364 KB)...
OKAY [ 8.930s]
writing 'recovery'...
OKAY [ 0.413s]
It all boots & works (as well as can be expected from Lollipop on a Nexus 7 nakasi, ie it lags & crashes, but less than it did with 5.0), but now it is no longer a 16Gb machine, it only has 6Gb... How can I fix this? Thanks
I had this problem when I flashed the 5.02 .img files in fastboot, including userdata. Went from 16Gb to 8Gb. Since I had already cleared my data, I went into fastboot and did a 'fastboot format data'. That got it back to 16Gb.
Groid said:
I had this problem when I flashed the 5.02 .img files in fastboot, including userdata. Went from 16Gb to 8Gb. Since I had already cleared my data, I went into fastboot and did a 'fastboot format data'. That got it back to 16Gb.
Click to expand...
Click to collapse
Same here. Seems to be a pretty common issue...
that didn't work for me
I entered the command, but it wouldn't do it. What should I try next?
Code:
fastboot format data
formatting 'data' partition...
Formatting is not supported for filesystem with type ''.
FAILED ()
finished. total time: 0.030s
reflash... again...
OK, I gave up messing around & used my TWRP Recovery advanced wipe to delete & reformat the data partition. Then I factory reset it. Then I re-flashed from a fresly downloaded version of nakasi-lrx22g-factory-2291c36b.tgz & re-rooted it with a freshly downloaded version of CF-Auto-Root-grouper-nakasi-nexus7.img
BINGO
Running like it should, with all of my storage space back. Thanks to all for your help & advice, & I'm still not too impressed with Lollipop so far...
Due to my sensors being completely gone in 5.1 on my Nexus 4, I decided to flash the new 5.1.1 image. Did a backup in CWM (which is now lost, CWM recovery wipe/reset removes its own backups pffft ), flashed the factory image except userdata.img ... and boot loop. Did a backup of everything (CWM), repeated, still the boot loop. Tried CWM reset (which is supposed to leave backups), no joy. Tried restoring backup, GONE. Sigh. (Should've adb pulled /sdcard/ , I know. )
Okay, so flashed everything again incl. userdata.img. Still boot loop.
Flashed 4.4.4 on it and performed stock recovery reset. No joy. LOcked bootloader, then unlocked again, JOY. Booted up into 4.4.4, and lo and friggin' behold, sensors are all there.
So flashed 5.1.1 factory image completely (bootloader, radio, recovery, boot, cache, system, userdata images). And again the infinite boot animation. Tried locking and then unlocking bootloader. no joy.
Each time I'm giving the phone 5 minutes of the animation to continue to setup, more than enough.
The flash-all.bat file hasn't worked in the past (missing sig file warnings),[1] so I'm unpacking image-occam-lmy47v.zip and fastboot flashing each partition by hand.
[1] This time it's working, so ... patience wins.
sending 'bootloader' (2264 KB)...
OKAY [ 0.078s]
writing 'bootloader'...
OKAY [ 0.312s]
finished. total time: 0.391s
rebooting into bootloader...
OKAY [ 0.000s]
finished. total time: 0.000s
< waiting for device >
sending 'radio' (45537 KB)...
OKAY [ 2.781s]
writing 'radio'...
OKAY [ 2.375s]
finished. total time: 5.188s
rebooting into bootloader...
OKAY [ 0.000s]
finished. total time: 0.062s
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
archive does not contain 'vendor.img'
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
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
--------------------------------------------
Bootloader Version...: MAKOZ30f
Baseband Version.....: M9615A-CEFWMAZM-2.0.1701.07
Serial Number........: 018ce19f988a6159
--------------------------------------------
checking product...
OKAY [ 0.000s]
checking version-bootloader...
OKAY [ 0.000s]
checking version-baseband...
OKAY [ 0.000s]
sending 'boot' (6398 KB)...
OKAY [ 4.125s]
writing 'boot'...
OKAY [ 0.328s]
sending 'recovery' (6960 KB)...
OKAY [ 1.281s]
writing 'recovery'...
OKAY [ 0.375s]
erasing 'system'...
OKAY [ 0.812s]
sending 'system' (834754 KB)...
OKAY [ 39.891s]
writing 'system'...
Click to expand...
Click to collapse
Anyone else encountering problems with the 5.1.1 factory image?
ChromeJob said:
Due to my sensors being completely gone in 5.1 on my Nexus 4, I decided to flash the new 5.1.1 image. Did a backup in CWM (which is now lost, CWM recovery wipe/reset removes its own backups pffft ), flashed the factory image except userdata.img ... and boot loop. Did a backup of everything (CWM), repeated, still the boot loop. Tried CWM reset (which is supposed to leave backups), no joy. Tried restoring backup, GONE. Sigh. (Should've adb pulled /sdcard/ , I know. )
Okay, so flashed everything again incl. userdata.img. Still boot loop.
Flashed 4.4.4 on it and performed stock recovery reset. No joy. LOcked bootloader, then unlocked again, JOY. Booted up into 4.4.4, and lo and friggin' behold, sensors are all there.
So flashed 5.1.1 factory image completely (bootloader, radio, recovery, boot, cache, system, userdata images). And again the infinite boot animation. Tried locking and then unlocking bootloader. no joy.
Each time I'm giving the phone 5 minutes of the animation to continue to setup, more than enough.
The flash-all.bat file hasn't worked in the past (missing sig file warnings),[1] so I'm unpacking image-occam-lmy47v.zip and fastboot flashing each partition by hand.
[1] This time it's working, so ... patience wins.
Anyone else encountering problems with the 5.1.1 factory image?
Click to expand...
Click to collapse
5 minutes? Takes at least 10 min to boot from flashing images on 5.0+. You likely are not looping, it just takes a very long time. You will see the screen dim at one point, and that signals like the last 25% or so of your wait, but if you do not see any errors, you are 99.99% likely just not waiting long enough.
Actually, my first flash of the 5.1.1 image files failed. Not sure if it was fastboot crashing on my laptop, or the fact my hyper kids were able to momentarily disconnect the USB while flashing, but I got an error sending system the first time.
ariesgodofwar said:
5 minutes? Takes at least 10 min to boot from flashing images on 5.0+. You likely are not looping, it just takes a very long time. You will see the screen dim at one point, and that signals like the last 25% or so of your wait, but if you do not see any errors, you are 99.99% likely just not waiting long enough.
Actually, my first flash of the 5.1.1 image files failed. Not sure if it was fastboot crashing on my laptop, or the fact my hyper kids were able to momentarily disconnect the USB while flashing, but I got an error sending system the first time.
Click to expand...
Click to collapse
Thanks, seems I have to go through this at least once a year ... not taking time to copy my CWM backup (adb pull /sdcard/ . ), etc. Not waiting for flash-all.bat to finish. Yada yada yada. I know that I'd set the N4 booting for more than 10 minutes (taking a shower and getting dressed, doing my 1-1/2 mile run -- 15 minutes -- etc).
Successfully installed and configured 4.4.4 again (good to clean out a system a bit. Will try again now that I've got a backup in hand, on a USB drive. Thanks for the feedback.
Having made and stored a successful backup, have been trying the 5.1 and 5.1.1 factory image install scripts with and without the -w userdata switch ... in all cases, the phone stays in a boot animation loop for longer than 15 minutes.
Is this Google's passive aggressive way of telling us the N4 is no longer supported? I.e. issue a broken factory image and leave us to stew in our juices?
I tried further tests last night and this morning with pure, straight factory image scripts, and the 5.1, 5.1.1 image just won't boot up on a Nexus 4. Pffft. I really wanted to see if the sensor problems were from an upgrade I did, or if it's a clear fault on a new vanilla install of stock 5.1.x. But it never worked. (I think I was running 5.0.1 until yesterday.)
This is infuriating.
Back to 4.4.4 because ... I need my phone, darn it!
I have the same problem. i tried everything, its now looping for a hour...
Maybe you might give installing 4.4.4 stock a try, and then upgrading via the OTAs instead of the images? The 5.1.1 images are not broken as I was able to flash without issue, so I am not thinking it is a problem with the images themselves.
If you are sure you are waiting long enough, I do know the was an issue with the 4.4.4->5.0 flash from the images where you literally had to flash and if you just left it, the dots would spin endlessly. This was remedied by then rebooting to bootloader, wiping the cache partition from bootloader, and rebooting. It would then boot just fine. It was just the N4 I found this to be the case on. I am pretty sure Wug even made an allowance for it in the NRT code (2.0.3 I think). Are you using 2.0.5 NRT to flash the images? If not, you might give it a try.
Adding- Are you trying to go from 4.4.4 to 5.1.1 directly? I can't recall if there were changes, but you might try flashing the 5.0 images from 4.4.4, and then going up to 5.1.1 just in case there is some issue with the version leap which is causing your issue.
Yes i tried have formated the partition and everything. I just go take a step backwards, i am currently installing 5.0.1, if thats not working i gonna flash 4.4.4. I wil give a update if i succeeded.
joostburg said:
Yes i tried have formated the partition and everything. I just go take a step backwards, i am currently installing 5.0.1, if thats not working i gonna flash 4.4.4. I wil give a update if i succeeded.
Click to expand...
Click to collapse
Just to be clear, when in bootloop, try rebooting to bootloader (hold Volume- and power) to get the android laying down with his chest open, and then I think it is hold Vol+ and tap pwr that will get you to the menu you are looking for.
Go in and just wipe the cache partition and reboot. Do not reformat it or anything. Just wipe cache, reboot, and then give it 10-15 minutes.
Still nothing works, damn tried now everything. How long should i see the 4 dots spinning approximately? 15, 30 or 60 minutes? Normally i just see it for about 5 minutes with a fresh installation.
edit: now its optimizing my apps, hope i am finally there now.
"The idea is simple. After you dirty flash the required images (boot, system and radio), install a custom recovery (CWM or TWRP) and clear "cache" AND "dalvik-cache". Bootloop avoided.You might think it's enough to just clear the cache. It's not. Trust me, I've tested this extensively." http://www.reddit.com/r/nexus4/comments/36r8s2/how_to_avoid_a_bootloop_when_flashing_the_511_or/
joostburg said:
Still nothing works, damn tried now everything. How long should i see the 4 dots spinning approximately? 15, 30 or 60 minutes? Normally i just see it for about 5 minutes with a fresh installation.
edit: now its optimizing my apps, hope i am finally there now.
"The idea is simple. After you dirty flash the required images (boot, system and radio), install a custom recovery (CWM or TWRP) and clear "cache" AND "dalvik-cache". Bootloop avoided.You might think it's enough to just clear the cache. It's not. Trust me, I've tested this extensively." http://www.reddit.com/r/nexus4/comments/36r8s2/how_to_avoid_a_bootloop_when_flashing_the_511_or/
Click to expand...
Click to collapse
I told you it takes an ungodly amount of time. I have more than a few times almost pulled the plug too early thinking it was taking too long.
Afters apps are optimized, i get a starting apps screen or something like that. After 8 hours its still showing that screen, pffff.
Edit: When i try to wipe data or internal storage i get:
e:Unable to mount /data
e:Unable to mount usb-otg
ariesgodofwar said:
Just to be clear, when in bootloop, try rebooting to bootloader (hold Volume- and power) to get the android laying down with his chest open, and then I think it is hold Vol+ and tap pwr that will get you to the menu you are looking for.
Go in and just wipe the cache partition and reboot. Do not reformat it or anything. Just wipe cache, reboot, and then give it 10-15 minutes.
Click to expand...
Click to collapse
Let's be clear about how to wipe cache, you can't do it in the bootloader.
Power off
Hold Power and VOL DOWN => bootloader
VOL to select Recovery
Power to enter Recovery.
In stock Recovery "fallen Android" icon, hold POWER and VOL UP => Recovery menu
Now use vol and power buttons to select Wipe cache partition.
My final attempt after doing factory reset/wipe data in stock recovery, using the factory image flash-all.bat and NOT removing the -w switch (so /userdata/ is overwritten as well), the N4 didn't boot after waiting > 30 minutes.
INteresting about clearing cache and Dalvik cache during factory flash ... Dalvik cache should be irrelevant with ART being default in Lollipop....
ChromeJob said:
Let's be clear about how to wipe cache, you can't do it in the bootloader.
Power off
Hold Power and VOL DOWN => bootloader
VOL to select Recovery
Power to enter Recovery.
In stock Recovery "fallen Android" icon, hold POWER and VOL UP => Recovery menu
Now use vol and power buttons to select Wipe cache partition.
My final attempt after doing factory reset/wipe data in stock recovery, using the factory image flash-all.bat and NOT removing the -w switch (so /userdata/ is overwritten as well), the N4 didn't boot after waiting > 30 minutes.
Click to expand...
Click to collapse
I did exact the some for the fifth time and after an hour still 4 dancing dots. OMG gonna throw my phone trough a wall! BTW if i wipe the dalvik cache the phone will boot then get a infinite loop after optimizing apps with android is starting apps.
Same. Tried the instructions on that reddit article, posted this:
... I cleared the cache with stock recovery, no joy. Powered off, flashed CWM recovery, cleared cache and Dalvik-cache with CWM, then reflashed stock recovery, then rebooted, endless "starting apps."
Now that I know this, I'm flashing 5.0.1 with existing apps, will either wait a day for OTA, or try flashing the factory image again over 5.0.1 with the caches clearing. Maybe some app is causing the problem. I know I was able to flash 5.0.1 previously over 4.4.4....
I just don't get how the 5.1.1 image is working for some people. It seems that as Android progresses, there are more and more little undocumented tricks and gimmicks that we have to use to update a factory image without wiping data....
And my kitchen In-Sink-Erator just bit the dust, so I've got that to deal with as well. (sigh)
I give up... Hope someone can post the solution. I gonna borrow a other phone, this is not gonna work.
Oh, I got caught up in several things ... 5.0.1 didn't work, though I previously installed it OVER 4.4.4. Pffft.
Frankly, I think 4.4.4 was a fine OS version running on the N4. ART, Material Design, etc....
5 has its enhancements, but I can't live without my sensors working properly.[1] They've got some bug fixin' to do....
[1] I didn't even know 5.1 or 5.1.1 was out, I was troubleshooting the sensors being gone in 5.0.1, searched online for similar reports, saw the new OTA announcements.
So ChromeJob and joostburg, were you guys at least able to manually flash back to 4.4.4?
Also, ChromeJob, on my post, you commented:
For your problem, download the factory image, then edit flash-all.bat/sh and remove the -w from the last flash command (-w rewrites /userdata partition). Whether you use 5.0.1 or 4.4.4 is up to you.
Click to expand...
Click to collapse
May you please explain this a little?
No i tried but the 4 dots won't disappear. I am phone less for more than 48 hours now lol, and all the stores are closed till Tuesday, fml.
About the -w flag, when you download the stock roms from google you have a file flash-all.bat, when you edit this file with notepad you will see -w, that stand for wiping your device (remove all data), when you remove the -w (backspace, backspace) save the file and execute your data will NOT be removed.
By the way, when i try to clear my sd card in custom recovery i get: e:mount -o bind '/data/media/0' '/sdcard' proces ended with error=255, is this the cause?
hmmzz, i did a last try with 4.4.4, did first factory reset and then a cache wipe and it booted again, finally.
After updates around 5.1.* my phone started playing up and was taking longer and longer to boot, eventually getting stuck with the four coloured dots swirling around.
Time to root the phone which I duly achieved with chainfires CF-Auto-Root via fastboot (since the phone wouldn't boot up/start). I then installed TWRP and sideloaded via adb the Cataclysm ROM (both the last Lollipop and the new Marshmallow versions), performing a full factory reset first, then for good measure making sure to wipe cache and dalvik cache again (should have wiped during factory reset).
All looks good, but on booting after optimizing the applications it hangs on "Cataclysm is installing... Starting apps" and will not progress any further. I left it five hours and no progress. Powered off and rebooted and back to where I started, hangs with the four coloured dots swirling around. This was with the Lollipop version of Cataclysm so I decided to give Marshmallow a go, same result, currently stuck on "Starting apps" now for 40 minutes.
Wiping cache and dalvik cache again just results in the the applications needing to be optomised each time.
Any thoughts, advice, suggested ROMs, kernels, tricks to try or ideas on how to recover the phone would be very much appreciated.
Thanks in advance,
enilkcals
Wipe from TWRP and Install just the Rom but do not install GAPPS. There may be problem with your GAPPS package. If the ROM boots perfectly, download and install different GAPPS package.
NEXUSg4 said:
Wipe from TWRP and Install just the Rom but do not install GAPPS. There may be problem with your GAPPS package. If the ROM boots perfectly, download and install different GAPPS package.
Click to expand...
Click to collapse
Cataclysm includes Gapps so I've had a go at flashing MinimalOS (5.1.1) which doesn't (after wiping Cache, Data and Dalvik Cache of course). Still hangs on boot animation and I left it half an hour just to make sure.
Tried with XenonHD without Gapps and it too just hangs at the boot animation.
Pretty stumped now as to whats going on or how to solve it.
Try flashing a factory image. That should return it to complete stock.
This guide tells you how: http://androidforums.com/threads/guide-how-to-flash-a-nexus-factory-image-manually.706533/
You should download the image from here though since the one in the guide is outdated. https://developers.google.com/android/nexus/images
theminikiller said:
Try flashing a factory image. That should return it to complete stock.
This guide tells you how: http://androidforums.com/threads/guide-how-to-flash-a-nexus-factory-image-manually.706533/
You should download the image from here though since the one in the guide is outdated. https://developers.google.com/android/nexus/images
Click to expand...
Click to collapse
I'll give it a go, but it was on stock when the problem first arose and wiping cache/dalvik/data didn't help.
I'm slightly confused as to which to download though. There are only "occam" for Nexus 4 listed, so I guess its one of those (likely 5.1.1 (LMY48T) as its the most recent). But for the other ROMs I've been installing they've all been for "mako" and when I boot into Fastboot the display reads...
Code:
FASTBOOT MODE
PRODUCT_NAME - mako
VARIANT - mako 8GB
HW VERSION - rev_10
BOOTLOADER VERSION - MAKOz30f
BASEBAND VERSION - M9615A-CEFWMAZM-2.0.1701.07
CARRIER INFO - None
SERIAL NUMBER - 002fff0a560d4e29
SIGNING - production
SECURE BOOT - enabled
LOCK STATE - unlocked
Wary of flashing the wrong ROM and screwing up the bootloader, as the instructions you linked (and on the image page itself) suggest the bootloader will be flashed and if I get that wrong there seems a high chance it will brick the phone.
How do I go about reconciling the device I have with the images available?
Occam is the right one. There is just several names for the device for some reason.
theminikiller said:
Occam is the right one. There is just several names for the device for some reason.
Click to expand...
Click to collapse
Thanks for the confirmation/sanity check.
Code:
# fastboot devices -l
002fff0a560d4e29 fastboot usb:2-2
occam-lmy48t # fastboot flash bootloader bootloader-mako-makoz30f.img
sending 'bootloader' (2264 KB)...
OKAY [ 0.080s]
writing 'bootloader'...
OKAY [ 0.332s]
finished. total time: 0.413s
occam-lmy48t # fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.000s]
finished. total time: 0.050s
occam-lmy48t # fastboot flash radio radio-mako-m9615a-cefwmazm-2.0.1701.07.img
sending 'radio' (45537 KB)...
OKAY [ 1.445s]
writing 'radio'...
OKAY [ 2.540s]
finished. total time: 3.986s
occam-lmy48t # fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.000s]
finished. total time: 0.050s
occam-lmy48t # fastboot -w update image-occam-lmy48t.zip
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
archive does not contain 'vendor.img'
Creating filesystem with parameters:
Size: 6189744128
Block size: 4096
Blocks per group: 32768
Inodes per group: 8048
Inode size: 256
Journal blocks: 23612
Label:
Blocks: 1511168
Block groups: 47
Reserved block group size: 375
Created filesystem with 11/378256 inodes and 50366/1511168 blocks
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
--------------------------------------------
Bootloader Version...: MAKOZ30f
Baseband Version.....: M9615A-CEFWMAZM-2.0.1701.07
Serial Number........: 002fff0a560d4e29
--------------------------------------------
checking product...
OKAY [ 0.002s]
checking version-bootloader...
OKAY [ 0.002s]
checking version-baseband...
OKAY [ 0.002s]
sending 'boot' (6448 KB)...
OKAY [ 0.211s]
writing 'boot'...
OKAY [ 0.337s]
sending 'recovery' (7008 KB)...
OKAY [ 0.237s]
writing 'recovery'...
OKAY [ 0.401s]
erasing 'system'...
OKAY [ 0.813s]
sending 'system' (834934 KB)...
OKAY [ 28.409s]
writing 'system'...
OKAY [ 47.296s]
erasing 'userdata'...
OKAY [ 1.400s]
sending 'userdata' (98413 KB)...
OKAY [ 3.401s]
writing 'userdata'...
OKAY [ 5.233s]
erasing 'cache'...
OKAY [ 0.056s]
sending 'cache' (10984 KB)...
OKAY [ 0.377s]
writing 'cache'...
OKAY [ 0.629s]
rebooting...
finished. total time: 88.871s
Rebooted and sitting on the booting screen with four coloured dots swirling around. Off to bed, will see if anything has happened tomorrow. Thanks again.
I think when this happened to be I had the wrong modem radio , I flash a new one appropriate for 5.1 and I was working after that.
Left it over night and still stuck on the boot animation.
Any more suggestions/ideas of things to try would be very welcome, but its looking like this phone has given up the ghost which is a bit of a shame as it would have made a nice backup.
Sadly, I don't have any other ideas.
In any case, good luck fixing it!
Thanks for your suggestions and help, appreciated.
cloneman1 said:
I think when this happened to be I had the wrong modem radio , I flash a new one appropriate for 5.1 and I was working after that.
Click to expand...
Click to collapse
Do you happen to have details of which modem radio you used? Not much for me to go on otherwise.
I've tried the official stock ROM from Google as theminikiller suggested and would expect that to have the correct modem radio included within it (which for 5.1.1 was the file radio-mako-m9615a-cefwmazm-2.0.1701.07.img that was bundled in with occam-lmy48t-factory-416938f1.tgz).
enilkcals said:
Thanks for your suggestions and help, appreciated.
Click to expand...
Click to collapse
hi i too had a similar issue.it was somewhat similar.my battery was dying.i tried installing stock rom.it never gotten past optimising apps screen.i tried some custom rom without gapps which booted fine. i used it a few days without gapps then the battery eventually died.it couldnt get past bootanimation.it can however stay in stock/twrp recovery.
so if you can try booting up the phone with a charger connected then the battery may be the issue. if it still didnt bootup go to a local service center ask them to open up nd remove battery and connect it directly to a power source in battery terminals.if the phone boots up fine you can order a new oem battery.[emoji3]
Sent from my Nexus 4 using Tapatalk
jaison thomas said:
hi i too had a similar issue.it was somewhat similar.my battery was dying.i tried installing stock rom.it never gotten past optimising apps screen.i tried some custom rom without gapps which booted fine. i used it a few days without gapps then the battery eventually died.it couldnt get past bootanimation.it can however stay in stock/twrp recovery.
so if you can try booting up the phone with a charger connected then the battery may be the issue. if it still didnt bootup go to a local service center ask them to open up nd remove battery and connect it directly to a power source in battery terminals.if the phone boots up fine you can order a new oem battery.[emoji3]
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
Hi,
Thanks for the suggestion, I have already tried booting with the charger plugged in (both USB from cable and a micro-USB charger from the mains).
I sent the phone back to LG last year and had the battery replaced under warranty then (just checked and last email communication was 2014-10-22) having bought the phone 2013-08-17. I guess since thats about a year its not unreasonable to think the battery could be worn out again. Not sure whether LG will replace under warranty and wary of throwing cash down the drain, but might see if can find one and replace it.
Thanks for the idea.
slackline
Hi,
Had a very similar thing happen to me. Turned out the radio was dying - something basic about loading firmware to it during very early hardware boot up.
Figured this out after a long process - and solution was to keep on soft rebooting it until the firmware loaded successfully - then Android booted ok - otherwise it would hang at starting apps.
James
enilkcals said:
Hi,
Thanks for the suggestion, I have already tried booting with the charger plugged in (both USB from cable and a micro-USB charger from the mains).
I sent the phone back to LG last year and had the battery replaced under warranty then (just checked and last email communication was 2014-10-22) having bought the phone 2013-08-17. I guess since thats about a year its not unreasonable to think the battery could be worn out again. Not sure whether LG will replace under warranty and wary of throwing cash down the drain, but might see if can find one and replace it.
Thanks for the idea.
slackline
Click to expand...
Click to collapse
Hi Everyone!
I tried to install LineageOS to my OP based on the OP6T page at the LineageOS website (I cannot link as it's my first post). I did everything as it was written without errors and after the last reboot nothing happened, I got back my Oxygen OS with google. I thought I might screwed up something, so I started it over again. At step "Installing LineageOS from recovery / step 5" when they say "Return to the previous menu" I had two options as first time.
1: tapping back until I really get back
2: reboot
First time I chose the first one, so I thought I might reboot now instead. Then I got no TWRP again back. After many-many tries, currently I'm at a point where I can access fastboot. My plan is to get back the original Oxygen OS and try again installing LineageOS.
The problem I face with can see in the end of the post.
I used adb/fastboot downloaded from google and I downloaded the latest OTA software from oneplus itself. After booting the phone, I see the OP loading logo stuck. I can get into fastboot by holding down all buttons (to halt the phone) and then turning it off with holding POWER+VOL DOWN. Then I get into a blueish menu (not fastboot or twrp!) where I can reboot into recovery/fastboot or wipe data.
Note, that the images.zip is created by me by extracting the payload.bin from the OTA zip I downloaded from OP's site.
I also tried to install back TWRP by flashing it onto boot, but the phone got again into an andless loading screen.
Yes, I know we have a tool called MSM, but I have no windows available, only linux and macos. I tried wine and virtualbox running windows but MSM didn't recognize my phone.
Any idea what can I do?
Logs:
Code:
[email protected]:~/Downloads/ota/output$ ./fastboot update images.zip
--------------------------------------------
Bootloader Version...:
Baseband Version.....:
Serial Number........: e5a9f9c
--------------------------------------------
extracting android-info.txt (0 MB) to RAM...
Checking 'product' OKAY [ 0.001s]
Setting current slot to 'a' OKAY [ 0.007s]
extracting boot.img (64 MB) to disk... took 0.187s
archive does not contain 'boot.sig'
Sending 'boot_a' (65536 KB) OKAY [ 2.032s]
Writing 'boot_a' OKAY [ 0.333s]
extracting dtbo.img (8 MB) to disk... took 0.051s
archive does not contain 'dtbo.sig'
Sending 'dtbo' (8192 KB) OKAY [ 0.250s]
Writing 'dtbo' OKAY [ 0.052s]
archive does not contain 'dt.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.003s]
Writing 'vbmeta' OKAY [ 0.001s]
archive does not contain 'vbmeta_system.img'
archive does not contain 'vendor_boot.img'
archive does not contain 'super_empty.img'
archive does not contain 'boot_other.img'
archive does not contain 'odm.img'
archive does not contain 'product.img'
extracting system.img (2860 MB) to disk... took 12.379s
Invalid sparse file format at header magic
archive does not contain 'system.sig'
Sending sparse 'system_a' 1/6 (513608 KB) OKAY [ 16.216s]
Writing 'system_a' OKAY [ 0.001s]
Sending sparse 'system_a' 2/6 (514145 KB) OKAY [ 18.289s]
Writing 'system_a' OKAY [ 0.001s]
Sending sparse 'system_a' 3/6 (515013 KB) OKAY [ 18.389s]
Writing 'system_a' OKAY [ 0.001s]
Sending sparse 'system_a' 4/6 (515534 KB) OKAY [ 18.281s]
Writing 'system_a' OKAY [ 0.001s]
Sending sparse 'system_a' 5/6 (510919 KB) OKAY [ 18.317s]
Writing 'system_a' OKAY [ 0.001s]
Sending sparse 'system_a' 6/6 (184768 KB) OKAY [ 8.139s]
Writing 'system_a' OKAY [ 0.001s]
archive does not contain 'system_ext.img'
archive does not contain 'system_other.img'
extracting vendor.img (1024 MB) to disk... took 4.095s
Invalid sparse file format at header magic
archive does not contain 'vendor.sig'
Sending sparse 'vendor' 1/2 (511135 KB) OKAY [ 16.211s]
Writing 'vendor' OKAY [ 0.001s]
Sending sparse 'vendor' 2/2 (389097 KB) OKAY [ 15.169s]
Writing 'vendor' OKAY [ 0.001s]
archive does not contain 'vendor_other.img'
Rebooting OKAY [ 10.729s]
Finished. Total time: 165.761s
mudlee said:
Hi Everyone!
I tried to install LineageOS to my OP based on the OP6T page at the LineageOS website (I cannot link as it's my first post). I did everything as it was written without errors and after the last reboot nothing happened, I got back my Oxygen OS with google. I thought I might screwed up something, so I started it over again. At step "Installing LineageOS from recovery / step 5" when they say "Return to the previous menu" I had two options as first time.
1: tapping back until I really get back
2: reboot
First time I chose the first one, so I thought I might reboot now instead. Then I got no TWRP again back. After many-many tries, currently I'm at a point where I can access fastboot. My plan is to get back the original Oxygen OS and try again installing LineageOS.
The problem I face with can see in the end of the post.
I used adb/fastboot downloaded from google and I downloaded the latest OTA software from oneplus itself. After booting the phone, I see the OP loading logo stuck. I can get into fastboot by holding down all buttons (to halt the phone) and then turning it off with holding POWER+VOL DOWN. Then I get into a blueish menu (not fastboot or twrp!) where I can reboot into recovery/fastboot or wipe data.
Note, that the images.zip is created by me by extracting the payload.bin from the OTA zip I downloaded from OP's site.
I also tried to install back TWRP by flashing it onto boot, but the phone got again into an andless loading screen.
Yes, I know we have a tool called MSM, but I have no windows available, only linux and macos. I tried wine and virtualbox running windows but MSM didn't recognize my phone.
Any idea what can I do?
Logs:
Click to expand...
Click to collapse
Can you Reboot to Fastboot? If so then load up TWRP via Fastboot Boot. Once in TWRP, flash OOS ZIP and TWRP Installer. Once that's done, Reboot to Recovery and Again flash OOS ZIP and TWRP Installer. Then Format Data by going to Wipe -> Format Data. Once that's done, Reboot to OOS and skip the Initial Setup. Transfer the LOS ROM and TWRP Installer as well as Gapps to Phone Storage and Reboot your phone to Recovery. Once there, go to Install and Flash LOS and TWRP Installer. Once that finishes, Reboot to TWRP and flash Gapps. After flashing Gapps, Format Data again and Reboot. Hopefully you boot into LOS. Also, if you are trying to install LOS 16, Use OOS 9.0.17 ZIP and if you're trying to Install LOS 17, Use OOS 10.3.0
thanks for your reply. I tried to load twrp into boot, but then it stuck at a screen where you can see with yellow color that the phone is unlocked and data integrity is not guaranteed.
I ran fastboot flash boot twrp.img then fastboot boot twrp.img, all went good, no errors, but then after the phone is rebooted, I see the screen above described and it stucks there.
mudlee said:
thanks for your reply. I tried to load twrp into boot, but then it stuck at a screen where you can see with yellow color that the phone is unlocked and data integrity is not guaranteed.
I ran fastboot flash boot twrp.img then fastboot boot twrp.img, all went good, no errors, but then after the phone is rebooted, I see the screen above described and it stucks there.
Click to expand...
Click to collapse
I'm afraid you'll have to MSM back to stock. That's the only way to recover your phone for sure.
DarthVader said:
I'm afraid you'll have to MSM back to stock. That's the only way to recover your phone for sure.
Click to expand...
Click to collapse
:-O I have to grab a windows pc then.
mudlee said:
:-O I have to grab a windows pc then.
Click to expand...
Click to collapse
Well before that, take a look at Fastboot ROMs. It's in the Guides Section. Instructions are in the First Post.
DarthVader said:
Well before that, take a look at Fastboot ROMs. It's in the Guides Section. Instructions are in the First Post.
Click to expand...
Click to collapse
Tried, the manual version as I was on linux. All images were sent to the device, got OKAY for everything, then the phone rebooted AND I HAVE STOCK ANDROID!
Thank you so much! Now I'm heading to install LineageOS
mudlee said:
Tried, the manual version as I was on linux. All images were sent to the device, got OKAY for everything, then the phone rebooted AND I HAVE STOCK ANDROID!
Thank you so much! Now I'm heading to install LineageOS
Click to expand...
Click to collapse
OK, so I tried to continue installing LineageOS with TWRP, but twrp does not load.
I ran
Code:
fastboot flash boot twrp.img
then rebooted the phone and twrp does not load, the phone just hangs at the screen with the yellow text saying the bootloader is unlocked. I can get back into stock by flashing the boot partition any time at least. I tried multiple twrp images.
What can be the problem with twrt?
Yellow screen is something like this (not my phone): https://forums-images.oneplus.net/attachments/1063/1063433-f5952bb27df62507293d3a3fd5496e11.jpg
mudlee said:
OK, so I tried to continue installing LineageOS with TWRP, but twrp does not load.
I ran then rebooted the phone and twrp does not load, the phone just hangs at the screen with the yellow text saying the bootloader is unlocked. I can get back into stock by flashing the boot partition any time at least. I tried multiple twrp images.
What can be the problem with twrt?
Yellow screen is something like this (not my phone): https://forums-images.oneplus.net/attachments/1063/1063433-f5952bb27df62507293d3a3fd5496e11.jpg
Click to expand...
Click to collapse
Sounds like a TWRP issue to me. Can you tell me what is your OOS version? And what version of TWRP are you using?
DarthVader said:
Sounds like a TWRP issue to me. Can you tell me what is your OOS version? And what version of TWRP are you using?
Click to expand...
Click to collapse
- As I said, I tried multiple twrp versions. Currently I'm trying out this one: https://eu.dl.twrp.me/fajita/twrp-3.3.1-1-fajita.img.html
- OOS: 10.3.0
- Android: 10
Maybe the problem is that I flashed last time too new OOS and that's why twrp does not work?
The answer is YES! I flashed an older OOS and I have now TWRP. I'll report back if I succeed.
mudlee said:
The answer is YES! I flashed an older OOS and I have now TWRP. I'll report back if I succeed.
Click to expand...
Click to collapse
Are you trying to install LOS 17 or 16?
DarthVader said:
Are you trying to install LOS 17 or 16?
Click to expand...
Click to collapse
I installed LOS 16 in the end, I might try the unofficial 17 as well, will see if I have time. I'm getting used to this flashing this and that here and there stuff
Thank you for your really valuable help!
eellogofusciouhipoppokunurious
Quote:
Originally Posted by OhioYJ
Appreciate it. This step maybe the key. I was using the TWRP installer, that maybe where I was going wrong. I'll have to give it another try.
(BASE STOCK ROM)
OnePlus6TOxygen_41_OTA_063_all_2001032024_215eea3f e7c64e37.zip (BETA4)
(CUSTOM ROM)
lineage-17.1-20200115_153235-UNOFFICIAL-fajita
(TWRP WITH SUCESSFULL DECRYPTION OF BASE STOCK ROM / CUSTOM ROM STORAGE)
twrp 3.3.1-30 zip
(Latest)
Magisk Canary . Zip
(Latest)
open_gapps - arm64-10.0-pico-20200116-BETA
(Latest)
RadioactiveKernel _ V10.2.0_CUSTOM_OnePlus6-6T
(Latest)
NanoDroid - 22.5.1.20200102
(&)
India_Fake_Partition_Deleter
------------------- EASY-CLEAN-INSTALL (LONG BUT BULLETPROOF) -------------------
!(BACK UP STORAGE/WILL LOSE DATA ETC.
ALL FILES ABOVE CAN BE SUBSTITUTED FOR ANY "IDEAL" ROM SETUP
CONFIGURATIONS YOU MAY PREFER., THESE ARE MY)!
------------------------------------------------------------------------------------------------
You only need any custom rom with the required BASE STOCK ROM and compatible TWRP version to decrypt storage, and of course, the latest magisk.
------------------------------------------------------------------------------------------------
fastboot boot twrp.img
Install twrp installer.
Mount all partitions / wipe / advanced / check all boxes & wipe all / format.
- - Reboot twrp - -
Mount all partitions / wipe / advanced / check all boxes & wipe all / format.
Reboot twrp
(DONT BE MOUNTING OR UNMOUNTING ANYTHING MANUALY ANYMORE!)
install OOS(BETA4).zip / TWRP installer
- - reboot recovery - -
install OOS(BETA4).zip / TWRP installer
- - reboot to recovery - -
Copy -
Magisk , TWRP & ROM to internal storage.
Format Data
Flash ROM
Flash TWRP installer
Reboot to recovery
Wipe Dalvik/ART Cache
Wipe Data
Flash Magisk.
Reboot system with your device unplugged to be safe (Device may reboot a couple times)
- - reboot to recovery - -
Copy -
Magisk , TWRP & ROM to internal storage.
Flash ROM
Flash TWRP installer
- - reboot to recovery - -
Flash Magisk
BOOT UP System
- - reboot back to recovery - -
Choose Reboot Option / (CHANGE YOUR SLOT) / Back / Reboot Recovery
Flash Magisk.
Reboot system
SETUP ROM
/////////////////////////////////////\OPTIONAL/\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\
- - REBOOT TO RECOVERY - -
----------------------------------------------------------------------------------------------------
STEP *( .=./ )*
Flash GAPPS
Flash India_Fake_Partition_Deleter
Flash NanoDroid (With prefered pre-configured setup/overlay/apps files placed)
Flash Custom Kernel
Re-Flash Magisk again
Click - WIPE DALVIK & Reboot system right after
------------------------------------------------------------------------------------------------------
- - REBOOT TO RECOVERY - -
Choose Reboot (CHANGE YOUR SLOT TO THE OPPOSITE SLOT)
- - REBOOT BACK TO RECOVERY - -
REPEAT STEP " *( .=./ )* "
-------------------------------------------------------------------------------------------------
GAME OVER
1up
THIS is EXTENSIVE but will work for any particular rom setup for a/b devices based on Q
Last edited by Johndoesmoked; 18th January 2020 at 07:13 AM. Reason: i dont know
Michelsup
19th January 2020, 08:55 AM |#743
Member91 posts Thanks: 133
Quote:
Originally Posted by OhioYJ
You were able to install TWRP? A lot of us cant install TWRP anymore, only boot it. If this has changed it would be nice to have a recovery
There was a bug on the first 17.1. With the last builds you can update like you always did; lineage.zip, twrp.zip, reboot to twrp, gapps.zip, magisk.zip, reboot and profit.
Of course you obviously had to update /vendor, as stated on Luk's post.
Hello. I'm new in playing with smartphones around and flashing roms and all the other things.
But I wanted to learn, and began with something like the Android 12 Beta.
I found this article: Install Android 12 GSI
I used the ARM64 because after the command to check the architecture I got: arm64-v8a outputted.
I tried it with gApps and without. After every command I reboot and after that I'm in a bootloop. I get the Huawei Logo and after that the "warning" that I have an unlocked bootloader and it can't be trusted. After a bit, I get the Huawei Logo again and so on. After 3 times I guess eRecovery comes.
C:\Users\weber\Desktop\dc-unlocker2client_1.00.1435>adb reboot bootloader
C:\Users\weber\Desktop\dc-unlocker2client_1.00.1435>fastboot flash vbmeta vbmeta.img
target reported max download size of 471859200 bytes
sending 'vbmeta' (4 KB)...
OKAY [ 0.017s]
writing 'vbmeta'...
OKAY [ 0.036s]
finished. total time: 0.073s
C:\Users\weber\Desktop\dc-unlocker2client_1.00.1435>fastboot erase system
erasing 'system'...
OKAY [ 37.155s]
finished. total time: 37.169s
C:\Users\weber\Desktop\dc-unlocker2client_1.00.1435>fastboot flash system system.img
target reported max download size of 471859200 bytes
Invalid sparse file format at header magi
sending sparse 'system' 1/4 (460796 KB)...
OKAY [ 13.484s]
writing 'system' 1/4...
OKAY [ 4.426s]
sending sparse 'system' 2/4 (456612 KB)...
OKAY [ 14.049s]
writing 'system' 2/4...
OKAY [ 3.476s]
sending sparse 'system' 3/4 (460796 KB)...
OKAY [ 13.959s]
writing 'system' 3/4...
OKAY [ 3.582s]
sending sparse 'system' 4/4 (173628 KB)...
OKAY [ 5.140s]
writing 'system' 4/4...
OKAY [ 1.580s]
finished. total time: 59.786s
C:\Users\weber\Desktop\dc-unlocker2client_1.00.1435>fastboot -w
wiping userdata...
Erase successful, but not automatically formatting.
Can't determine partition type.
FAILED (remote: Command not allowed)
erasing 'userdata'...
(bootloader) success to erase cryypt info in oeminfo
OKAY [ 1.711s]
finished. total time: 1.719s
C:\Users\weber\Desktop\dc-unlocker2client_1.00.1435>fastboot reboot
rebooting...
finished. total time: 0.043s
Click to expand...
Click to collapse
Those are the outputs ov ervery command. Did I do something wrong? Or is the Huawei P10 Lite not able to flash the Androdi 12 Beta?
I appreciate any help!
Traijan said:
Hello. I'm new in playing with smartphones around and flashing roms and all the other things.
But I wanted to learn, and began with something like the Android 12 Beta.
I found this article: Install Android 12 GSI
I used the ARM64 because after the command to check the architecture I got: arm64-v8a outputted.
I tried it with gApps and without. After every command I reboot and after that I'm in a bootloop. I get the Huawei Logo and after that the "warning" that I have an unlocked bootloader and it can't be trusted. After a bit, I get the Huawei Logo again and so on. After 3 times I guess eRecovery comes.
Those are the outputs ov ervery command. Did I do something wrong? Or is the Huawei P10 Lite not able to flash the Androdi 12 Beta?
I appreciate any help!
Click to expand...
Click to collapse
Hi...
first....the untrustet warning is normal even the bootloader is unlocked. Thats just ah info!
sec...did you come from Stock Rom or any other custom Rom and if custom then was this rom rootet. if yes (root) then you need to unroot first or you get bootloop. for unroot you must restore the stock ramdisk image thats the boot image. If you have no backup (btw greatest fail you could do by developing any Device) the recover stock Rom with erecovery and after initia boot activate dev options and usb debugging again. After that start from a clean stock Rom.
next...did you encrypt your internal storage with the fstab.hi6250b.zip and reboot to TWRP and then format Data then wipe Cache, Dalvik, Data, internal Storage and System then (Method a) reboot again to TWRP and flash the Rom. Yor also can also (Method b) not reboot to Bootloader not to TWRP and flash it with fastboot command.
But it is possible that the GSI Rom Android 12 actually not compatible with p10 lite. Its beta State and gapps for A12 would be beta to i think. So my thinking is just to wait for the official release what no garat for compatibility with p10 lite is but then the Rom isnt beta anymore.
solong
speedson
Supplement...the Part with the vbmeta is not necessary as far as i know.
solong
speedson
speedson said:
Hi...
first....the untrustet warning is normal even the bootloader is unlocked. Thats just ah info!
sec...did you come from Stock Rom or any other custom Rom and if custom then was this rom rootet. if yes (root) then you need to unroot first or you get bootloop. for unroot you must restore the stock ramdisk image thats the boot image. If you have no backup (btw greatest fail you could do by developing any Device) the recover stock Rom with erecovery and after initia boot activate dev options and usb debugging again. After that start from a clean stock Rom.
next...did you encrypt your internal storage with the fstab.hi6250b.zip and reboot to TWRP and then format Data then wipe Cache, Dalvik, Data, internal Storage and System then (Method a) reboot again to TWRP and flash the Rom. Yor also can also (Method b) not reboot to Bootloader not to TWRP and flash it with fastboot command.
But it is possible that the GSI Rom Android 12 actually not compatible with p10 lite. Its beta State and gapps for A12 would be beta to i think. So my thinking is just to wait for the official release what no garat for compatibility with p10 lite is but then the Rom isnt beta anymore.
solong
speedson
Click to expand...
Click to collapse
Hey, I used the default rom installed on my huawei p10 lite.
I did a complete clean install yet.
Before that I used twrp to install it (because I thought it worked with .img) and after that I startet from a clean install of the default rom again and did the linked tutorial.
I'm not root on this device, I just have a unlocked bootloader.
I also didn't encrypted my internal storage. Do I have to do it?
What you mean with not reboot to bootloader? I did the commands in the link on fastboot (holding vol - and connect to pc)
Do you have an idea what I can do? I really would like to test android 12.
A good place to start when figuring out why no rom install's in my system-as-root...
Back to stock it is...