Develop Bugs

[Q] Hardest Soft-Bricked ever seen!!! (Help me plz)

hello
i try to install recovery on 5.1.1 stock ROM with this:
http://forum.xda-developers.com/showthread.php?t=1346180
after clicking on install... my device reboot but stuck in bootloop
I try to fix this... flash softbrick/bootloop with Nexus Root ToolKit but not fixed
and next i try flash manually and wipe dalvik_cache but stuck bootloop agian...
sorry for poor my english...
PLZ HELP!!!

xx000xx said:
hello
i try to install recovery on 5.1.1 stock ROM with this:
http://forum.xda-developers.com/showthread.php?t=1346180
after clicking on install... my device reboot but stuck in bootloop
I try to fix this... flash softbrick/bootloop with Nexus Root ToolKit but not fixed
and next i try flash manually and wipe dalvik_cache but stuck bootloop agian...
sorry for poor my english...
PLZ HELP!!!
Click to expand...
Click to collapse
You tried to flash with an app designed for the TF101?????? And you wonder why this is happening to your Nexus 7?

graphdarnell said:
You tried to flash with an app designed for the TF101?????? And you wonder why this is happening to your Nexus 7?
Click to expand...
Click to collapse
I didn't see that...anyway it happened... NO WAY???!! :crying:

xx000xx said:
I didn't see that...anyway it happened... NO WAY???!! :crying:
Click to expand...
Click to collapse
You don't sound like one who's familiar with flashing anything. Be that as it may, what did you do exactly by "manually flash"? Can you get into fastboot mode or recovery at all? If you can, what does the screen show? You mentioned bootloop. How far does the tablet get before looping?

graphdarnell said:
You don't sound like one who's familiar with flashing anything. Be that as it may, what did you do exactly by "manually flash"? Can you get into fastboot mode or recovery at all? If you can, what does the screen show? You mentioned bootloop. How far does the tablet get before looping?
Click to expand...
Click to collapse
i did flashing with factory img already...
--------
i did manually flash because when flash system.img cmd error:cannot load system.img
so I fixed it by editing the command used to flash the system.img
fastboot flash -S 512M system system.img
and all my commands cmd:
Code:
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
fastboot flash bootloader ["bootloader name".img]
fastboot flash radio ["radio name".img]
fastboot reboot-bootloader
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash -S 512M system system.img
fastboot flash cache cache.img
fastboot flash userdata userdata.img
And all command were finished successfully
---------
yes... i can get into fastboot mode and recovery mode
you said : "If you can, what does the screen show?"
hmm...in fastboot show normal bootloader
and in recovery mode I install cwm recovery
------------
bootloop happen in animation after google logo
-----------

xx000xx said:
i did flashing with factory img already...
--------
i did manually flash because when flash system.img cmd error:cannot load system.img
so I fixed it by editing the command used to flash the system.img
fastboot flash -S 512M system system.img
and all my commands cmd:
Code:
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
fastboot flash bootloader ["bootloader name".img]
fastboot flash radio ["radio name".img]
fastboot reboot-bootloader
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash -S 512M system system.img
fastboot flash cache cache.img
fastboot flash userdata userdata.img
And all command were finished successfully
---------
yes... i can get into fastboot mode and recovery mode
you said : "If you can, what does the screen show?"
hmm...in fastboot show normal bootloader
and in recovery mode I install cwm recovery
------------
bootloop happen in animation after google logo
-----------
Click to expand...
Click to collapse
From experience, mine and others', if you get to the animation part, it means the boot partition is intact. You get into trouble when that is damaged somehow. If I were you, I would flash everything again and separately, from boot.img, to system.img, to recovery.img.
Make sure you choose the right one for your tablet. LTE for LTE and flo for flo (wifi only model) - no mix up. I did flash a wi-fi only rom on an LTE 2012 before, and it didn't brick the tablet, but I have no idea what such a mistake would do to a 2013 model.
I would use a stock-based rom like CleanRom only because so many people bricked theirs after flashing stock rom. I would try Cleanrom to make sure the tablet is functional hardware-wise first. Then, if you feel like taking the dive, go for your stock rom. Ask the author if you cannot retrieve the individual images from the zip file. Good luck.

hardest soft-bricked ever seen!!!
anybody haven't idea?

Why is -S 512M needed? I see what you said above but I've never seen anyone saying to use that command for this device. Update fastboot? Maybe a fastboot format cache at the end?
To be a ****, all you had to do was fastboot flash recovery recoveryname.img but you know that now. :highfive:

yosmokinman said:
Why is -S 512M needed? I see what you said above but I've never seen anyone saying to use that command for this device. Update fastboot? Maybe a fastboot format cache at the end?
To be a ****, all you had to do was fastboot flash recovery recoveryname.img but you know that now. :highfive:
Click to expand...
Click to collapse
because this:
http://forum.xda-developers.com/google-nexus-5/help/load-img-error-t3108648
in #4 solved
---
i did that all thing u said but not worked
---

HTC One M8 recovery Error

I did install Blues Marshmallow GPE rom that i found here.I installed it without root/s-off.Now i want to install cyanogenmod 13 but when i try to enter to recovery mode it says Error with an Android logo.Nothing else,just "Error." and can't enter to twrp recovery mode.How do i fix this?

Try fastboot erase cache, and fastboot flash TWRP again.

redpoint73 said:
Try fastboot erase cache, and fastboot flash TWRP again.
Click to expand...
Click to collapse
I'm not that good at this kind of stuff.Is there any guide videos of how to do erase cache and flash twrp? i don't remember how did i do it.

burakby35 said:
I'm not that good at this kind of stuff.Is there any guide videos of how to do erase cache and flash twrp? i don't remember how did i do it.
Click to expand...
Click to collapse
Instructions on how to flash TWRP via fastboot are on the TWRP page: https://twrp.me/devices/htconem8gsm.html
Before you flash TWRP, erasing cache (which can often clear up problems with TWRP not installing or booting properly), is a simple fastboot command: fastboot erase cache

Flashing from MM to N system images via fastboot stuck at google logo

All,
I am not a noob by any means, but when I attempted to manually flash the img files via fastboot for the latest N build from the factory images coming from the last 6.0.1 build I get stuck on the Google logo. I checked the commands and re-flashed again and the same result happened ( i did flash radios and BL ) .
I even tried to format data ( i had backed everything up ) , still no go and stuck at google logo still. I could access BL and able to access TWRP.
I got frustrated and flashed the 6.0.1 images including BL and radio via fastboot and booted up just fine. I then rooted, installed flashfire and used the OTA and Android N installed just fine.
Does anyone have any idea what could be causing this. I am currently on N, but wanted to do a clean install .
Thanks in Advance

Did you flash vendor.img?
Why don't you list the exact commands you used to flash, then people can comment.

fastboot flash system system.img
fastboot flash vendor vendor.img
fastboot flash boot boot.img
fastboot erase cache
fastboot flash cache cache.img
fastboot flash recovery twrp-3.0.2-2-bullhead.img
fastboot reboot-bootloader
fastboot flash recovery twrp-3.0.2-2-bullhead.img
Flashing mtc20k works successfully
Using the same commands to flashing npf10c results in stuck the google logo
In order for me to even get on N I have to me on 6.0.1 then either use the bullhead-ota-npf10c-d1785fea.zip on the root of the SD card and use flashfire OR use the following command from stock recovery
adb sideload bullhead-ota-npf10c-d1785fea.zip
The later is what I did recently, but both will work to get to N.
So why can I not simply flash the factory images like for 6.0.1?

carm01 said:
fastboot flash system system.img
fastboot flash vendor vendor.img
fastboot flash boot boot.img
fastboot erase cache
fastboot flash cache cache.img
fastboot flash recovery twrp-3.0.2-2-bullhead.img
fastboot reboot-bootloader
fastboot flash recovery twrp-3.0.2-2-bullhead.img
Flashing mtc20k works successfully
Using the same commands to flashing npf10c results in stuck the google logo
In order for me to even get on N I have to me on 6.0.1 then either use the bullhead-ota-npf10c-d1785fea.zip on the root of the SD card and use flashfire OR use the following command from stock recovery
adb sideload bullhead-ota-npf10c-d1785fea.zip
The later is what I did recently, but both will work to get to N.
So why can I not simply flash the factory images like for 6.0.1?
Click to expand...
Click to collapse
What happens when you flash a Nougat factory image that is NOT a developer preview? Try flashing NRD91N from here:
https://developers.google.com/android/images?hl=en
Sent from my Nexus 5X using Tapatalk

carm01 said:
fastboot flash system system.img
fastboot flash vendor vendor.img
fastboot flash boot boot.img
fastboot erase cache
fastboot flash cache cache.img
fastboot flash recovery twrp-3.0.2-2-bullhead.img
fastboot reboot-bootloader
fastboot flash recovery twrp-3.0.2-2-bullhead.img
Flashing mtc20k works successfully
Using the same commands to flashing npf10c results in stuck the google logo
In order for me to even get on N I have to me on 6.0.1 then either use the bullhead-ota-npf10c-d1785fea.zip on the root of the SD card and use flashfire OR use the following command from stock recovery
adb sideload bullhead-ota-npf10c-d1785fea.zip
The later is what I did recently, but both will work to get to N.
So why can I not simply flash the factory images like for 6.0.1?
Click to expand...
Click to collapse
I don't usually flash cache or user.
Try this instead and see if it works.
Instead of flashing cache.img
fastboot erase cache
fastboot format cache
(if you want to reset user)
fastboot erase userdata
fastboot format userdata

sfhub said:
I don't usually flash cache or user.
Try this instead and see if it works.
Instead of flashing cache.img
fastboot erase cache
fastboot format cache
(if you want to reset user)
fastboot erase userdata
fastboot format userdata
Click to expand...
Click to collapse
SlimSnoopOS said:
What happens when you flash a Nougat factory image that is NOT a developer preview? Try flashing NRD91N from here:
https://developers.google.com/android/images?hl=en
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
I have tried fastboot erase userdata and fastboot format userdata and fastboot erase cache
fastboot format cache and that never worked.
I tried that factory image before and resulted in the same, however, I will at sometime attempt to do the final of 7.1.1 once it is available sometime in December 2016 and hopefully will resolve the issue.
I will stay on DP1 right now as i find the battery extremely excellent, the Visual VM is back now, and i notice some notifications are coming through better than in 7.0. (I read an article earlier today about notifications and the pixel not coming through)
Thanks in Advance for the people that did come through so far and wanted to thank you for your input on the matter and if i don't have a pixel by December I will try this out.

OOS 5.1.4 boots fine, TWRP doesn't ("remote: Failed to load/authenticate boot image")

OOS 5.1.4 boots fine, TWRP doesn't ("remote: Failed to load/authenticate boot image")
Hello,
I am trying again from my previous post.
Context: I used TWRP by "fastboot boot twrp.img" without problems for many months. OOS 5.0.4 (Android 8.0). Was rooted using Magisk. Then I updated using OTA to 5.1.4 (Android 8.1) by accident. Had a pattern at the time. OOS 5.1.4 boots fine, I can use the phone. But now "fastboot boot twrp.img" fails.
The phone works fine, but without booting TWRP I can't root (or do any other updates/backups).
Details: I reboot into bootloader (the menu with red/yellow letters on top). I try "fastboot boot twrp.img" and just get stuck for 10s while the warning is on screen that my bootloader is unlocked. Then I drop into a black screen with "1+ fastboot" prompt. If I try "fastboot boot twrp.img" there again, I get error "remote: 'Failed to load/authenticate boot image: 00000050'".
I've tried removing the pattern, and different TWRP images:
twrp-3.2.3-x_blu_spark_v9.85_treble-op5_op5t.img
twrp-3.2.3-0-20181031-codeworkx-dumpling.img
twrp-3.2.1-x_blu_spark_v8.70-op5_op5t.img
twrp-3.2.3-1-dumpling.img
twrp-3.2.1-1-dumpling.img
Someone elsewhere suggested to flash TWRP into recovery. But given that I can't even boot TWRP, I am weary of doing this. It seems like a way to just kill the stock recovery.
Please help!!

Use 'fastboot boot filename.img' not flashboot

Bump121 said:
Use 'fastboot boot filename.img' not flashboot
Click to expand...
Click to collapse
Thank you for responding! You are right of course.
That was actually a typo in my post, I meant to write "fastboot boot twrp.img". fastboot is the command I used, flashboot doesn't exist (that I know of). My mind was probably thinking of "fastboot flash", which I am scared to do since I can't even get TWRP to boot. I will edit the post now.

znarg said:
Thank you for responding! You are right of course.
That was actually a typo in my post, I meant to write "fastboot boot twrp.img". fastboot is the command I used, flashboot doesn't exist (that I know of). My mind was probably thinking of "fastboot flash", which I am scared to do since I can't even get TWRP to boot. I will edit the post now.
Click to expand...
Click to collapse
Then Do One Thing (This will wipe all of your data)
go to fastboot and type all these one by one
1. fastboot erase cache
2. fastboot format cache
3. fastboot erase system
4.fastboot format system
5.fastboot erase userdata
6.fastboot format userdata
after running all these commands one by one all you need to do is reboot to fastboot again, then boot the .img file.
This Time I Guess It Will Work.

i cannot boot a gsi, always bootloop

so I've been trying to install a gsi for 5+ hours, I can never even get to the system boot animation. I've used permissiver, disable dm-verity, I've tried phh, erfans miui, oneui, oos, but cant get to the bootanimation. here are the steps i followed:
1. format
2. flash lineageos
3. wipe cache, dalvik, system, data
4 flash system.img gsi to system
5. flash permissiver and disable dmverity
6. reboot system
7. I get a redmi logo for 4 seconds, a black screen for 1 second and it keeps looping.
pls somebody help

You need to create a vendor.

hussain_mdj said:
You need to create a vendor.
Click to expand...
Click to collapse
pls elaborate, do i need to backup my current vendor, and then restore after installing the system.img?

I don't know why you have process steps like above, but basically the steps should be ( tested and used by me and all 2k members of my grp ) :
1st, you should be on stock, because GSI has only System images, and for a device to work, it need more than just a System images.
Boot into system, using adb reboot bootloader to get into bootloader mode ( or you can use hard keys, its up to you ). Execute these command in correct order :
fastboot devices ( check if device is connected )
fastboot reboot fastboot
fastboot --disable-verification flash vbmeta vbmeta.img ( remember to use patched vbmeta.img )
fastboot erase system
fastboot flash system system.img ( change to gsi's image file name )
fastboot -w
fastboot reboot bootloader
fastboot erase userdata
fastboot reboot
It may depends on what kind of device u have, but basically it should be like this. Try and feedback.