I was running the June patch version of the TWRP flashable stock builds (had hard bricked my phone before so cannot use full stock firmware until and unless I get my hands on the stock Oreo firmware).
As the official Oreo update is out, (https://drive.google.com/file/d/1ZmtSW40oZi1EXD0PsRib3dqIeF9vauAY/view) I downloaded the zip file and placed it in my internal storage and tried to apply the update, which took me to TWRP, and the update failed. I rebooted to see if everything was ok and it was.
Then, I tried to revert to the stock firmware of the latest edition (to see if I could apply the update) and each time I tried to run the commands or run the flash file, it failed because I was not able to flash the stock recovery. It showed 'N/A' instead of 'bad key' every time on the screen before booting into TWRP.
I wanna get back to full stock! Help guys!
roydhritiman said:
I was running the June patch version of the TWRP flashable stock builds (had hard bricked my phone before so cannot use full stock firmware until and unless I get my hands on the stock Oreo firmware).
As the official Oreo update is out, (https://drive.google.com/file/d/1ZmtSW40oZi1EXD0PsRib3dqIeF9vauAY/view) I downloaded the zip file and placed it in my internal storage and tried to apply the update, which took me to TWRP, and the update failed. I rebooted to see if everything was ok and it was.
Then, I tried to revert to the stock firmware of the latest edition (to see if I could apply the update) and each time I tried to run the commands or run the flash file, it failed because I was not able to flash the stock recovery. It showed 'N/A' instead of 'bad key' every time on the screen before booting into TWRP.
I gave up and tried to go back to the TWRP build I was using before, and I get this error on TWRP. Why is this happening? (I had formatted my data after entering TWRP, is this th reason?)
Please help guys! Need to get my phone back and running!
Here is an image of what's going on -
Click to expand...
Click to collapse
If you're able to get into bootloade,try flashing stock rom without the bootloader,gpt codes so you
Don't lose your bootloader and flash the stock rom.
riyan65 said:
If you're able to get into bootloade,try flashing stock rom without the bootloader,gpt codes so you
Don't lose your bootloader and flash the stock rom.
Click to expand...
Click to collapse
I tried that, no success
riyan65 said:
If you're able to get into bootloade,try flashing stock rom without the bootloader,gpt codes so you
Don't lose your bootloader and flash the stock rom.
Click to expand...
Click to collapse
i tried this and am still getting the same error when im trying to flash the stock recovery:
fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (20580 KB)...
OKAY [ 0.497s]
writing 'recovery'...
(bootloader) Image size exeeded partition limits
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.497s
whats wrong?
roydhritiman said:
i tried this and am still getting the same error when im trying to flash the stock recovery:
fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (20580 KB)...
OKAY [ 0.497s]
writing 'recovery'...
(bootloader) Image size exeeded partition limits
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.497s
whats wrong?
Click to expand...
Click to collapse
Could you post the all errors while you getting in stock rom flash
roydhritiman said:
sending 'recovery' (20580 KB)...
OKAY [ 0.497s]
writing 'recovery'...
(bootloader) Image size exeeded partition limits
whats wrong?
Click to expand...
Click to collapse
The error shows clearly that you messed up the partition table (GPT).
nicolap8 said:
The error shows clearly that you messed up the partition table (GPT).
Click to expand...
Click to collapse
I think the problem is, since I was hardbricked, I needed to use blankflash to revive my bootloader. There was no proper working blankflash for the g5 plus last year, so had to use the Albus blankflash to revive the bootloader. Is that the reason why I can't flash the stock ROM? If yes, could you tell me how to get back to the g5 plus' native bootloader via its own blankflash?
roydhritiman said:
I think the problem is, since I was hardbricked, I needed to use blankflash to revive my bootloader. There was no proper working blankflash for the g5 plus last year, so had to use the Albus blankflash to revive the bootloader. Is that the reason why I can't flash the stock ROM? If yes, could you tell me how to get back to the g5 plus' native bootloader via its own blankflash?
Click to expand...
Click to collapse
By using mmcblk0 file I think we can get original bootloader of Moto g5 plus
riyan65 said:
By using mmcblk0 file I think we can get original bootloader of Moto g5 plus
Click to expand...
Click to collapse
Can you guide me with that process?
roydhritiman said:
Can you guide me with that process?
Click to expand...
Click to collapse
Here it is https://forum.xda-developers.com/moto-g5s/how-to/guide-how-to-create-mmcblk0-img-device-t3803176
riyan65 said:
Here it is https://forum.xda-developers.com/moto-g5s/how-to/guide-how-to-create-mmcblk0-img-device-t3803176
Click to expand...
Click to collapse
I'm somewhat of a noob, so could you explain what exactly does this process do?
roydhritiman said:
I'm somewhat of a noob, so could you explain what exactly does this process do?
Click to expand...
Click to collapse
You need a memory card of about your device storage or more than that. And a working device of same model. The mmcblk0 file is used as temporary bootloader of Moto g5 plus until you flash your original bootloader, the mmcblk0 file need to store in Memory card with image type so it can be used as temporary bootloader. After you get the Moto g5 plus bootloader in your device you don't need to have memory card you can use it as regular. This mmcblk0 method is used to recover a hard bricked device by flashing temporary bootloader on it and after flashing stock rom it can used normally.
---------- Post added at 05:29 PM ---------- Previous post was at 05:27 PM ----------
You can ask someone to put mmcblk0 file on XDA so you get your original bootloader.
riyan65 said:
You need a memory card of about your device storage or more than that. And a working device of same model. The mmcblk0 file is used as temporary bootloader of Moto g5 plus until you flash your original bootloader, the mmcblk0 file need to store in Memory card with image type so it can be used as temporary bootloader. After you get the Moto g5 plus bootloader in your device you don't need to have memory card you can use it as regular. This mmcblk0 method is used to recover a hard bricked device by flashing temporary bootloader on it and after flashing stock rom it can used normally.
---------- Post added at 05:29 PM ---------- Previous post was at 05:27 PM ----------
You can ask someone to put mmcblk0 file on XDA so you get your original bootloader.
Click to expand...
Click to collapse
No , no and no! You told a lot of incorrect statement.
The SD card MUST be bigger than your phone internal memory.
You are copying the ENTIRE internal memory of a phone to the SD card then copy back to your phone rewriting ALL. Not only the bootloader. Also the foundamental partitions that are unique to every phone. Read the 3d on 0 IMEI here in this forum for a good explanation.
nicolap8 said:
No , no and no! You told a lot of incorrect statement.
The SD card MUST be bigger than your phone internal memory.
You are copying the ENTIRE internal memory of a phone to the SD card then copy back to your phone rewriting ALL. Not only the bootloader. Also the foundamental partitions that are unique to every phone. Read the 3d on 0 IMEI here in this forum for a good explanation.
Click to expand...
Click to collapse
I have saw many people are using 32gb memory card for 32 gb of internal storage, so I have said that and once we get bootloader we are going to remove the memory card so we can install stock rom. IMEI lost is a small problem in front of a hard brick device as imei lost problem also have been solved.
riyan65 said:
I have saw many people are using 32gb memory card for 32 gb of internal storage, so I have said that and once we get bootloader we are going to remove the memory card so we can install stock rom. IMEI lost is a small problem in front of a hard brick device as imei lost problem also have been solved.
Click to expand...
Click to collapse
Many people write only to move digits...
If the free space of the SD card is less than the size of internal memory the procedure will abort.
IMEI lost still a problem, read better!
In some state using an IMEI duplicated is punible by law...
Related
Firstly good morning. I'm sorry for poor English. I'm from Brazil. I bought my phone yesterday, eager to unlock your bootloader and make root. I'm have bricked my phone. He no longer starts, is looped boot, I can access the fastboot mode and recovery mode. But the phone not does start. What must I do to revive it? It is without root and your bootloader is still locked. I thank the understanding and help.
My device is ASUS_Z00LD (KE550KL) 1GB RAM 8GB ROM.
* No root (I've bricked trying install rooted fw version)
*No unlocked
*Only fastboot mode work (adb not)
*Boot can be changed
*Recovery can be changed
*System not can be changed
**edit**
1)In adb sideload method, appears the error: adb sideload file... : cannot read <filename.zip>
2) Fastboot mode, the last process say this:
C:\Users\gusta\Desktop\Flashtools\FlashTools>fastboot flash system system.img
target reported max download size of 268435456 bytes
erasing 'system'...
OKAY [ 0.012s]
sending sparse 'system' (259338 KB)...
OKAY [ 8.595s]
writing 'system'...
FAILED (remote: size too large)
finished. total time: 8.620s
Click to expand...
Click to collapse
*Edit*
i've proceed with this tutorial http://www.asus.com/zentalk/tw/thread-148390-1-1.html (DONT WORK KKKKK)
And my phone dont start now, pc recongnize the phone as :QHSUSB_BULK
damn! HEHE
[]'s
Download asus firmware from its site. Put file into sd card. Go to recovery and select update from sd card. Select the firmware file you downloaded. And you good to go
sagar321 said:
Download asus firmware from its site. Put file into sd card. Go to recovery and select update from sd card. Select the firmware file you downloaded. And you good to go
Click to expand...
Click to collapse
Thanks for atention. I've using TWRP in this moment. I dont know wich as my original firmware, just remember it was 6.0.1 or similar.
My device is ASUS_Z00LD (KE550KL) 1GB RAM 8GB ROM.
* No root (I've bricker trying install rooted fw version)
*No unlocked
*Only fastboot mode work (adb not)
*Boot can be changed
*Recovery can be changed
*System not can be changed
I've tryed to install this version: UL-Z00L-WW-21.40.1220.1708-user, and show this error in TWRP:
Update process ended with ERROR: 7
Error installing zip file '/sdcard/UL-Z00L-WW-21...
Click to expand...
Click to collapse
Any sugestion? Thanks! :fingers-crossed:
colonho said:
Thanks for atention. I've using TWRP in this moment. I dont know wich as my original firmware, just remember it was 6.0.1 or similar.
My device is ASUS_Z00LD (KE550KL) 1GB RAM 8GB ROM.
* No root (I've bricker trying install rooted fw version)
*No unlocked
*Only fastboot mode work (adb not)
*Boot can be changed
*Recovery can be changed
*System not can be changed
I've tryed to install this version: UL-Z00L-WW-21.40.1220.1708-user, and show this error in TWRP:
Any sugestion? Thanks! :fingers-crossed:
Click to expand...
Click to collapse
You download the basic version (eg: 16.xx.xx.x)and try the same method, the package you downloaded is MM version and it will not support the LP Recovery.
There's a solution
Colonho, did you found the solution? Você encontrou a solução? Estou com o mesmo problema.
I accidentally bricked my xt1562 while attempting to flash a rom. I wiped the phone using twrp and when it rebooted it was stuck on the 'WARNING BOOTLOADER UNLOCKED' screen.
I attempted to flash the stock rom using adb but it shows the following error.
C:\Users\devya\Desktop\Fastboot+ADB\Win32>fastboot flash partition gpt.bin
sending 'partition' (32 KB)...
OKAY [ 0.005s]
writing 'partition'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.505s
PLEASE HELP!
can u paste the commands here to see them?
devyadav0399 said:
I accidentally bricked my xt1562 while attempting to flash a rom. I wiped the phone using twrp and when it rebooted it was stuck on the 'WARNING BOOTLOADER UNLOCKED' screen.
I attempted to flash the stock rom using adb but it shows the following error.
PLEASE HELP!
Click to expand...
Click to collapse
I'd advice you use the original image to flash for your country and device which was 5.1 via ADB following the steps described in the forum.
https://forum.xda-developers.com/mo...de-how-to-flash-factory-image-return-t3261486
Dio-Genes said:
I'd advice you use the original image to flash for your country and device which was 5.1 via ADB following the steps described in the forum.
https://forum.xda-developers.com/mo...de-how-to-flash-factory-image-return-t3261486
Click to expand...
Click to collapse
Thanks dude for the quick response. I'll get onto it.
if u flash the stock marshmallow firmware...u have to add sparsechunk 7,8 and 9 in the commands with the same way they appear...
bytheway...here is the latest with october patch yesterday new flashable rom zip...u only have to flash supersu after flashed rom.good luck.
https://forum.xda-developers.com/showthread.php?t=3533559
kos25k said:
if u flash the stock marshmallow firmware...u have to add sparsechunk 7,8 and 9 in the commands with the same way they appear...
bytheway...here is the latest with october patch yesterday new flashable rom zip...u only have to flash supersu after flashed rom.good luck.
https://forum.xda-developers.com/showthread.php?t=3533559
Click to expand...
Click to collapse
I tried that once before and got the same error message until I used the original firmware, 5.1 which was the one it was originally shipped with. That's why I gave that advice.
ok dude glad to hear.now from twrp i think u can flash latest MM flashable. (not sure through if u first have to flash 6.0 MM)
So for some background, I was on EMUI 4.1 and successfully flashed to EMUI 5.
Then, I wanted to rollback so I flashed recovery again and stock firmware. I tried flashing with fastboot and didn't work. I tried using Huawei recovery 3-button method, no luck either.
Errors using fastboot flashing:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash system "F:\SYSTEM.img"
target reported max download size of 471859200 bytes
sending sparse 'system' 1/6 (445721 KB)...
OKAY [ 17.780s]
writing 'system' 1/6...
FAILED (remote: sparse flash write failure)
finished. total time: 17.822s
Click to expand...
Click to collapse
Error with 3-button method:
Software install failed!
Incompatibility with current version.
Please download the correct update package.
Click to expand...
Click to collapse
When I was booting into Revolution recovery, I could not mount SD card and some other partitions so maybe that has something to do with the 3-button method problem... Furthermore, I don't know how to check which version exactly my phone is, all I know is that it was VNS-L31.
Now I'm stuck with a phone that is constantly rebooting so how do I proceed?
First of all...
Please tell me you have a backup of your Nougat ROM. If yes, restore it.
I have failed to go back to MM several times like you before.
It really is a question of using the right files.
First, flash the OEMInfo that is provided here in the forums.
Second, flash the right firmware. This one is tricky. For me, ONLY VNS-L31 Version C150 worked. No other.
Flashing with fastboot always never works. It always gives an error on system. So you need to find a firmware that works with 3-button method.
Your task now is the get back to working Nougat, since you did something wrong.
Unlock BL, flash Nougat recovery with fastboot.
Then,
easiest is like I said restoring a backup.
If you don't have one, try flashing the Revolution ROM by BadWolf.
Schlengge said:
First of all...
Please tell me you have a backup of your Nougat ROM. If yes, restore it.
I have failed to go back to MM several times like you before.
It really is a question of using the right files.
First, flash the OEMInfo that is provided here in the forums.
Second, flash the right firmware. This one is tricky. For me, ONLY VNS-L31 Version C150 worked. No other.
Flashing with fastboot always never works. It always gives an error on system. So you need to find a firmware that works with 3-button method.
Your task now is the get back to working Nougat, since you did something wrong.
Unlock BL, flash Nougat recovery with fastboot.
Then,
easiest is like I said restoring a backup.
If you don't have one, try flashing the Revolution ROM by BadWolf.
Click to expand...
Click to collapse
Have just solved the problem with the steps from here.
From my understanding, it seems that I lost almost everything, device info, OEM info, recovery... So no technique was working.
The solution in brief was:
1. Go into bootloader to flash recovery (I used Revolution Recovery)
2. In recovery, flash OEM info.
3. Then used the 3-button method to install stock version for the appropriate model (which I could see from OEM info).
4. Unlocked bootloader, triggering a factory reset. (I was stuck in infinite boot before this point.)
As you say Schlengge, it is a matter of using the right files! Thanks. Problem solved.
Hey everyone, I just bricked my LG G6. I was trying to use Uppercut and LGUP to flash a stock firmware, but it wouldn't detect my phone, so i followed this post: https://forum.xda-developers.com/showpost.php?p=70446385&postcount=70
Once I did that and restarted my phone, it got stuck in bootloop and it will display this: "Your device has failed routine safety check and will not boot."
Right now, I can only access fastboot and download mode, but download mode doesn't stick and my PC doesn't detect the phone in download mode, only Fastboot. I can't enter recovery.
Please help guys I don't want my phone to be scrap metal
P.S.: Was running LineageOS prior to bootloop.
Have you tried flashing anything from fastboot?
If you phone has bootloader unlocked then flash twrp via fastboot. If not contact LG for a service
---------- Post added at 07:00 AM ---------- Previous post was at 06:59 AM ----------
Also wiping misc is a very bad idea
boksquare said:
Hey everyone, I just bricked my LG G6. I was trying to use Uppercut and LGUP to flash a stock firmware, but it wouldn't detect my phone, so i followed this post: https://forum.xda-developers.com/showpost.php?p=70446385&postcount=70
Once I did that and restarted my phone, it got stuck in bootloop and it will display this: "Your device has failed routine safety check and will not boot."
Right now, I can only access fastboot and download mode, but download mode doesn't stick and my PC doesn't detect the phone in download mode, only Fastboot. I can't enter recovery.
Please help guys I don't want my phone to be scrap metal
P.S.: Was running LineageOS prior to bootloop.
Click to expand...
Click to collapse
Did you relock the bootloader ?
cory733 said:
Have you tried flashing anything from fastboot?
Click to expand...
Click to collapse
No I have not. Should I? What should I flash thru fastboot?
jimbomodder said:
If you phone has bootloader unlocked then flash twrp via fastboot. If not contact LG for a service
Ok I will try that
---------- Post added at 07:00 AM ---------- Previous post was at 06:59 AM ----------
Also wiping misc is a very bad idea
Click to expand...
Click to collapse
numpea said:
Did you relock the bootloader ?
Click to expand...
Click to collapse
No I did not. Should I? I bricked my HTC One once doing this and I remember locking bootloader would make things harder to fix for me.
Sometimes getting the phone detected in download mode can be tricky, often you will have to play around with different usb cables and / or computers.
I would try flashing TWRP in fastboot. See if you can get into TWRP, then you can try flashing a rom.
cory733 said:
Sometimes getting the phone detected in download mode can be tricky, often you will have to play around with different usb cables and / or computers.
I would try flashing TWRP in fastboot. See if you can get into TWRP, then you can try flashing a rom.
Click to expand...
Click to collapse
I don't really have lots of USB cables or computers at my disposal though.. Do I just keep trying until it works, and even if so, how do I know when the phone is detected in download mode?
I also found out that even though I can enter fastboot, my bootloader is somehow locked again, and I can't flash the unlock bin so I can't even get a custom recovery to be flashed on there. Any other ideas or is my phone dead for good?
New update:
- I entered fastboot and tried flashing TWRP but bootloader is locked. Tried to flash unlock bin but i get this:
target reported max download size of 536870912 bytes
sending 'unlock' (1 KB)...
OKAY [ 0.039s]
writing 'unlock'...
(bootloader) Error!!
(bootloader) Bootloader Unlock key write fail
FAILED (remote failure)
finished. total time: 0.080s
I'm super desperate at this point. Will LG fix my device if I send it to them? I know warranty is out the window but would they fix it for a payment?
boksquare said:
New update:
- I entered fastboot and tried flashing TWRP but bootloader is locked. Tried to flash unlock bin but i get this:
target reported max download size of 536870912 bytes
sending 'unlock' (1 KB)...
OKAY [ 0.039s]
writing 'unlock'...
(bootloader) Error!!
(bootloader) Bootloader Unlock key write fail
FAILED (remote failure)
finished. total time: 0.080s
I'm super desperate at this point. Will LG fix my device if I send it to them? I know warranty is out the window but would they fix it for a payment?
Click to expand...
Click to collapse
maybe you locked the bootloader at some point with twrp !
maybe your unlock.bin is corrupted you need either unlock bootloader or try to flash kdz via download mode accessing
if you can't do that, LG center is the only way good luck
Why were you originally trying to flash stock firmware?
cory733 said:
Why were you originally trying to flash stock firmware?
Click to expand...
Click to collapse
I realized the visual appeal of custom OSes no longer attract me as much as full usability (Using google pay or fingerprint in some apps) and stability as I used to when I was young. I wanted to flash stock firmware and just keep root and xposed to enhance my stock experience.
Update 2:
I contacted LG and they quoted me a minimum of $300 and up for repairs.. Really hope someone has a fix to my issue or any other suggestions. I'm thinking about taking to a phone repair store but I doubt they will be able to fix this. I live in Houston, TX area if anybody has store suggestions. Thank you
So what rom were you on? And how did you flash it without TWRP? Can you go through from start to finish exactly what you did?
so im trying this since yesterday
Please help me ive been trying to find solution everything flashes except when i try flashing vendor.img it says vendor error : buffer overreads occured due to invalid sparse header how can i fix this my device is redmi7A with unlocked bootloader using original cable on usb2 slot trying to unbrick it since yesterday using latest flashtool and drivers using this firmware eu version Xiaomi_Redmi_7A_V11.0.3.0.QCMEUXM_20200728.0000.00_EEA_10_XFT also would like to mention i unlocked bootloader installed twrp and formated all partitions (brave man i am) tryed using the default firmware upgrade tool also tryed manually installing vendor.img from the firmware but no success tryed formating the partition under twrp to ext2 and returned it to ext4 didnt try to change the size or anything ....this all because the default firmware couldnt install game me vendor error ... at this point im giving up on it ... if anyone knows what must be done hes welcome :fingers-crossed:
here is the msg :
fastboot flash vendor vendor.img
target reported max download size of 535821312 bytes
sending 'vendor' (290176 KB)...
OKAY [ 9.152s]
writing 'vendor'...
FAILED (remote: buffer overreads occured due to invalid sparse header)
finished. total time: 12.419s
....last time i ever buy a chinese device from 5-6 different firmwares i could test only 2 because the others didnt have all the files required in the images folder .....chinese piece of trash and thats it...no way of restoring my device even with the default firmware i still cannot understand did i do something wrong or what......
What says when you tried to flash the vendor with twrp?
first check if you using the newest fastboot version via: fastboot --version
are u sure that you have the EEA Hardware?
when u have access to twrp(recovery) try sideload via adb sideload
and here is a how to flash manually link:
[TUTORIAL] How to flash a factory image | Return to stock | Unroot/SAVE your Nexus 5
How to flash a factory image | Return to stock | Unroot your Nexus 5 Hello Nexus 5 Users! I see many users that don't know how to restore their Nexus 5 to stock. It may come in handy, either when you want to RMA your phone, or you want to...
forum.xda-developers.com
plstanchev said:
....last time i ever buy a chinese device .....chinese piece of trash and thats it...
Click to expand...
Click to collapse
this could happen to you with any device! for me the 7A is a really great device. if you unlocked your bootloader you know that there is always a chance to brick your phone! so take responsibility for your actions and don't blame the manufacturer.
PS: if you use more dots and enter it would be much more better to read through your post if someone is trying to help :/
I am also not responsible if anything goes wrong.
May be your download file is corrupted, have you checked the integrity of that file, the extension (.tgz) fastboot firmware.
And flash them with mitool and always download from official site.