Related
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
---
Hey guys !
So since i messed up with the recovery mode, i'm stucked in the fastboot with no Download mode (recovery doesnt work neither).
So after searching 3 days in the internet i found the acces to fast through adb by puting a new laf.img in order to restore the download mode and flash a stock firmware !
My problem is that when i try to enter the command on the cmd, i get severals errors, take a look :
Code:
C:\Program Files (x86)\Minimal ADB and Fastboot>adb devices
adb server is out of date. killing...
* daemon started successfully *
List of devices attached
C:\Program Files (x86)\Minimal ADB and Fastboot>adb shell
error: device not found
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot erase laf
erasing 'laf'...
FAILED (remote: failed to erase partition
)
finished. total time: 5.034s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash laf laf.img
target reported max download size of 2147483648 bytes
sending 'laf' (18432 KB)...
OKAY [ 0.581s]
writing 'laf'...
FAILED (remote: flash write failure)
finished. total time: 5.615s
Also command : "fastboot boot laf.img" result to "Failed(remote: dtb not found) instead of flash write failure..
Of course i have my G3 855 32GB in download mode (but it goes into fastmode), so when i try a command, lines are added in the screen etc..
Does that mean that my laf.img don't work? I assumed that so i try several, but does it have to be the exact same one as the one who was in my phone before( v20a if i record correctly ) or could it be from any 855 32GB version ?
I also thought it could be a recognition problem as when i type "adb devices" or "adb shell" nothing is found..
If someone has any clue or a link to some guide i'll be more than joyful, thanks in advance !
Try adb fastboot when writing command hope it helps
Anik49 said:
Try adb fastboot when writing command hope it helps
Click to expand...
Click to collapse
Hey thank you so much for answering !
What do you mean by that, i already download the adb/fastboot driver and launch a cmd in the directory they are at, writing "adb fastboot" has no result neither, can you be more specific please ?
cm13 recently messed up my phone in exactly the same way, no recovery and download mode would jump straght to fastboot. I followed this guide to the letter and am now back running again: http://open-freax.fr/guide-unbrick-your-lg-g3/
BigsyBiggins said:
cm13 recently messed up my phone in exactly the same way, no recovery and download mode would jump straght to fastboot. I followed this guide to the letter and am now back running again:
Click to expand...
Click to collapse
Well i hope my problem can be solved in a safer way, i dont like much to go on the hardware part, so I'll use it as my last hope, but thanks
Altought i think my device is recognized by fastboot in someway because it responds when i type commands in fastboot, and also when i reboot it.
But i'm getting this error :
Code:
error : command never completed
error : auto CMD12 error
error : command completed with errors
error : command timeout error
failed to send stop command
failed writing block @ 1
in the screen of my phone. Does that stand for Cyanogen mode which i was trying to put on my phone ?
I mean when you enter command in cmd use adb before any command also use cmd which one available on android sdk folder....also you can use this method if adb not workinhg properly http://forum.xda-developers.com/lg-g...-9008-t3072091
BigsyBiggins said:
cm13 recently messed up my phone in exactly the same way, no recovery and download mode would jump straght to fastboot. I followed this guide to the letter and am now back running again: http://open-freax.fr/guide-unbrick-your-lg-g3/
Click to expand...
Click to collapse
Like @BigsyBiggins said, this is the guide which could fix your phone. HW Part is not too hard!
Anik49 said:
I mean when you enter command in cmd use adb before any command also use cmd which one available on android sdk folder....also you can use this method if adb not workinhg properly
Click to expand...
Click to collapse
Oh ok ! Also your link is not working :s
I understand that the method can work but I think that the method i'm trying to use is really close to succeed, over my search on the internet, i saw lots of people who manage to succeed with it.
But i guess i must do something wrong. I downloaded the kdz file according to my IMEI.
Then I extracted the .dz file with LG Firmware Extract. Then I extracted the file named laf_393216.bin from the dz file. Changed his name into laf.img , put it into the fastboot directory.
Then i typed
Code:
fastboot format cache
fastboot erase laf
fastboot flash laf laf.img
in a cmd from the directory.
It all seemed to work, but then when i remove the battery and restart into download mode, it goes into fastboot after the download mode charging animation..
Also when i try to boot with fastboot boot laf.img i get the error (remote: dtb not found) on the cmd.
And ERROR: Unable to find suitable device tree for device(194/0x0001001/112/0) ERROR: getting device tree adress failed DTB offset is incorrect, kernel image does not have appended DTB)
Am I doing something wrong, should I changed more file than just laf ?
SisGG said:
Oh ok ! Also your link is not working :s
I understand that the method can work but I think that the method i'm trying to use is really close to succeed, over my search on the internet, i saw lots of people who manage to succeed with it.
But i guess i must do something wrong. I downloaded the kdz file according to my IMEI.
Then I extracted the .dz file with LG Firmware Extract. Then I extracted the file named laf_393216.bin from the dz file. Changed his name into laf.img , put it into the fastboot directory.
Then i typed
Code:
fastboot format cache
fastboot erase laf
fastboot flash laf laf.img
in a cmd from the directory.
It all seemed to work, but then when i remove the battery and restart into download mode, it goes into fastboot after the download mode charging animation..
Also when i try to boot with fastboot boot laf.img i get the error (remote: dtb not found) on the cmd.
And ERROR: Unable to find suitable device tree for device(194/0x0001001/112/0) ERROR: getting device tree adress failed DTB offset is incorrect, kernel image does not have appended DTB)
Am I doing something wrong, should I changed more file than just laf ?
Click to expand...
Click to collapse
I don´t know what exactly is the problem, maybe something with your win-driver, some crashed or drifted partitions or some broken files...
I just can repeat my advice: I was in the same situation with my phone after a failed cm13 update and i was trying and reading about 2 days how to solve it - after the above mentioned method, your phone would get out of this "coma".
Maybe somebody else here in this forum could help you with your mentioned method, sorry.
Ernesto0023 said:
I don´t know what exactly is the problem, maybe something with your win-driver, some crashed or drifted partitions or some broken files...
I just can repeat my advice: I was in the same situation with my phone after a failed cm13 update and i was trying and reading about 2 days how to solve it - after the above mentioned method, your phone would get out of this "coma".
Maybe somebody else here in this forum could help you with your mentioned method, sorry.
Click to expand...
Click to collapse
Well I think i'm still under warranty, so i dont wanna touch to much on the hardware.
So do you think, if i send it back without touching anything, saying i put it on charge one night and the next morning it was like this, the warranty could work?
If they found it's rooted or they understand you did something with your software your warrenty is void ?
SisGG said:
Well i hope my problem can be solved in a safer way, i dont like much to go on the hardware part, so I'll use it as my last hope, but thanks
Altought i think my device is recognized by fastboot in someway because it responds when i type commands in fastboot, and also when i reboot it.
But i'm getting this error :
Code:
error : command never completed
error : auto CMD12 error
error : command completed with errors
error : command timeout error
failed to send stop command
failed writing block @ 1
in the screen of my phone. Does that stand for Cyanogen mode which i was trying to put on my phone ?
Click to expand...
Click to collapse
Remove the battery, put it, press the volume + and connect to PC USB, if like entering download, what happens to us not to go, will leave the ****ing LoGo, Well, hold down the volume + and not let go, I think it is less for 2 minutes more. After a while, the computer tells us that something was connected, the phone will tell you who is in fastboot as I said before, if not let me fastboot flash boot files and the LAF, recovery ect, nothing happens, there is still a magic command.
fastboot boot laf.img
Keep it in the ****ing heart
miguexneox said:
Remove the battery, put it, press the volume + and connect to PC USB, if like entering download, what happens to us not to go, will leave the ****ing LoGo, Well, hold down the volume + and not let go, I think it is less for 2 minutes more. After a while, the computer tells us that something was connected, the phone will tell you who is in fastboot as I said before, if not let me fastboot flash boot files and the LAF, recovery ect, nothing happens, there is still a magic command.
fastboot boot laf.img
Keep it in the ****ing heart
Click to expand...
Click to collapse
I dont quite understand what u meant there :s
I already have acces on the fastboot, actually now, my phone goes instantly on fastboot whatever i do.. Though i cannot boot a laf.img downloaded and flashed .. :'(
SisGG said:
I dont quite understand what u meant there :s
I already have acces on the fastboot, actually now, my phone goes instantly on fastboot whatever i do.. Though i cannot boot a laf.img downloaded and flashed .. :'(
Click to expand...
Click to collapse
were u able to resolve this issue. I am in your shoes at the moment.
I have tried the qualcomm. The drivers doesnt seem to work for my phone .
I can't flash or the laf.img . the fastboot commands doesnt seem to work.
and I'm stuck in fastboot .
What can be done
datrmon said:
were u able to resolve this issue. I am in your shoes at the moment.
I have tried the qualcomm. The drivers doesnt seem to work for my phone .
I can't flash or the laf.img . the fastboot commands doesnt seem to work.
and I'm stuck in fastboot .
What can be done
Click to expand...
Click to collapse
You have several options:
- find your phone firmware, extract recovery.img and flash it back through fastboot(do exactly the same for the LAF partition to restore download mode)
- flash a custom recovery for your phone model, if it doesn't work try an older version of TWRP, also it can be that your phone is not d855 but d850 model, so try to flash a d850 custom recovery and see if it works(that was exactly my problem and why i got stuck in fastboot mode, because my phone is d850 model and in settings it says d855, so I flashed wrong TWRP)
Ghikya said:
You have several options:
- find your phone firmware, extract recovery.img and flash it back through fastboot(do exactly the same for the LAF partition to restore download mode)
- flash a custom recovery for your phone model, if it doesn't work try an older version of TWRP, also it can be that your phone is not d855 but d850 model, so try to flash a d850 custom recovery and see if it works(that was exactly my problem and why i got stuck in fastboot mode, because my phone is d850 model and in settings it says d855, so I flashed wrong TWRP)
Click to expand...
Click to collapse
Thanks for the response .
I am unable to flash files at all.
This is the error
D:\mfastboot-v2>fastboot flash laf laf.img
target max-download-size: 2048MB
sending 'laf' (18432 KB)...
OKAY [ 0.646s]
writing 'laf'...
FAILED (remote: flash write failure)
finished. total time: 5.726s
D:\mfastboot-v2>
datrmon said:
Thanks for the response .
I am unable to flash files at all.
This is the error
D:\mfastboot-v2>fastboot flash laf laf.img
target max-download-size: 2048MB
sending 'laf' (18432 KB)...
OKAY [ 0.646s]
writing 'laf'...
FAILED (remote: flash write failure)
finished. total time: 5.726s
D:\mfastboot-v2>
Click to expand...
Click to collapse
It seems that your phone's bootloader is locked, you can try to execute this command: "fastboot oem unlock", and then check state with "fastboot oem device-info". But some people says that it does nothing, so you can try and check for yourself.
You can also try to boot directly an image from fastboot for eaxmple:
Code:
fastboot boot laf.img
or
Code:
fastboot boot twrp.img
So if you could successfully boot a laf image you would be able to access download mode, and if you could boot a custom recowery then you could access ADB and to try to flash other partitions, or even flash a custom rom...
So,recently i switched from cm14.1 back to cm13 and when i did that, i forgot to downgrade the bootloader,so after i flashed the rom I went to the bootloader and made the downgrade,Successfully booted into cm13,but when i tried going to recovery to flash xposed,i found out there's bootloop ( stuck on asus logo ) ! Everytime i try to boot into bootloader or recovery! nothing works!
Saumitraa said:
So,recently i switched from cm14.1 back to cm13 and when i did that, i forgot to downgrade the bootloader,so after i flashed the rom I went to the bootloader and made the downgrade,Successfully booted into cm13,but when i tried going to recovery to flash xposed,i found out there's bootloop ( stuck on asus logo ) ! Everytime i try to boot into bootloader or recovery! nothing works!
Click to expand...
Click to collapse
if no boot loader you have to use unbrick threads.
If you had a flashed back a stock recovery and boot.img if on rooted mm bl with giovix modder tool , you could've downgraded via sd card and stock recovery ..in my link below
There were 2 different cm 13s , one with mm bl and one based on 5.
.
Unbricked
So i unbricked the phone! Everything was success! xfstk worked then i got the 4 color screen and after that the bootloader!
Extracted the .raw file and then flashed using commands, but when the phone tries to reboot, it gets stuck on the ASUS logo! waited half an hour for that! Service center people say that its a motherboard problem! Any advice ?
Saumitraa said:
So i unbricked the phone! Everything was success! xfstk worked then i got the 4 color screen and after that the bootloader!
Extracted the .raw file and then flashed using commands, but when the phone tries to reboot, it gets stuck on the ASUS logo! waited half an hour for that! Service center people say that its a motherboard problem! Any advice ?
Click to expand...
Click to collapse
did you get any error in any command. if you got bootloader it must work
flash xfstk again and and run these commands after extracting raw.. tell me if any of the command fails or give error
1. fastboot devices ( see if it is recognized: else plug out usb and plugin again)
2. fastboot oem erase_osip_header
3. fastboot oem start_partitioning
4. fastboot flash /tmp/partition.tbl partition.tbl
5. fastboot oem partition /tmp/partition.tbl
6. fastboot erase system
7. fastboot erase cache
8. fastboot erase data
9. fastboot erase APD
10. fastboot erase ADF
11. fastboot oem wipe splashscreen
12. fastboot oem stop_partitioning
13. fastboot flash splashscreen splash_sign.bin
14. fastboot flash token MFG_BOM_Full.bin
15. fastboot flash ifwi ifwi-prod.bin
16. fastboot flash boot boot_sign.bin
17. fastboot flash recovery recovery_sign.bin
18. fastboot flash fastboot droidboot_sign.bin
19. fastboot flash APD APD.img
20. fastboot flash system system.img
21. fastboot reboot
No errors
I flashed everything again, no errors whatsoever! The phone just wont boot! Stuck on Asus logo for an hour , then switched off the phone
Saumitraa said:
I flashed everything again, no errors whatsoever! The phone just wont boot! Stuck on Asus logo for an hour , then switched off the phone
Click to expand...
Click to collapse
Which build number raw file you use ?
Saumitraa said:
I flashed everything again, no errors whatsoever! The phone just wont boot! Stuck on Asus logo for an hour , then switched off the phone
Click to expand...
Click to collapse
send me log of cmd when you run commands
timbernot said:
Which build number raw file you use ?
Click to expand...
Click to collapse
This one : WW_ZE551ML_2.20.40.194_20160713
Can anyone pls tell me where I can download stock rom for (lenovo) p2 preferable in zip format . And is there any unbricking tutorial .
I want this too...? if anyone can help...
I have found the stock ROM, I bricked my device in the rooting process, and am unable to flash the complete stock image, because the device reports "unable to flash bootloader on unlocked device"
itsjustbilly said:
I have found the stock ROM, I bricked my device in the rooting process, and am unable to flash the complete stock image, because the device reports "unable to flash bootloader on unlocked device"
Click to expand...
Click to collapse
Hi, because you should not flash bootloader.
you can try those 2 solutions:
the fast one, it should work. The flashall command flash every.img files he find in the fastboot directory. So try to remove the bootlader.img and execute the flashall command.
the manual one (longer one):
Put only the recovery.img, boot.img, and the system.img files ( you should have something like 13 , named "systemchunk0/12.img") in your fastboot directory and flash with fastboot ( the command is always the same: fastboot flash recovery recovery.img, fastboot flash boot boot.img, and for every single part of system.img you should flash like "fastboot flash systemchunk0(until 12).img " so you flash flash 13 times the system with avery 13 parts .
Sorry for my english i hope you solved that
itsjustbilly said:
I have found the stock ROM, I bricked my device in the rooting process, and am unable to flash the complete stock image, because the device reports "unable to flash bootloader on unlocked device"
Click to expand...
Click to collapse
Then share it no
I'll post links when I get to my computer, but they're not Cwm flash able zips, they are fast boot files that you flash from DOS on a pc
---------- Post added at 09:39 AM ---------- Previous post was at 09:37 AM ----------
aleleo87 said:
Hi, because you should not flash bootloader.
you can try those 2 solutions:
the fast one, it should work. The flashall command flash every.img files he find in the fastboot directory. So try to remove the bootlader.img and execute the flashall command.
the manual one (longer one):
Put only the recovery.img, boot.img, and the system.img files ( you should have something like 13 , named "systemchunk0/12.img") in your fastboot directory and flash with fastboot ( the command is always the same: fastboot flash recovery recovery.img, fastboot flash boot boot.img, and for every single part of system.img you should flash like "fastboot flash systemchunk0(until 12).img " so you flash flash 13 times the system with avery 13 parts .
Sorry for my english i hope you solved that
Click to expand...
Click to collapse
I did try this, but I still have no signal because the modem file is part of the bootloader, and no modem means no mobile signal
itsjustbilly said:
I'll post links when I get to my computer, but they're not Cwm flash able zips, they are fast boot files that you flash from DOS on a pc
---------- Post added at 09:39 AM ---------- Previous post was at 09:37 AM ----------
I did try this, but I still have no signal because the modem file is part of the bootloader, and no modem means no mobile signal
Click to expand...
Click to collapse
Ah ok i didnt understand that you have this modem issue. I don't kno how to help you...you phone is bricked so you can test few solutions without more risks .
before flash the original recovery , boot and system by fastboot, you can try to install TWRP again and flash only the bootloader from TWRP (should support .zip and .img files). Then you turn the phone in fastboot mode and flash other stuff .
Taken from post 4 of the TWRP page on lenovo P2 forum
smaranramesh said:
Then share it no
Click to expand...
Click to collapse
Factory Images & Systemless Mode
Q: I messed up help me?!
So you screwed up and didn't follow Rule Number One in the IT-Handbook?
Which is: Always create a backup before working on a system?
Download the Factory State Images. Which are all flashable with fastboot: https://goo.gl/JTCwKj
Place the files you want replaced into the "Minimal ADB & Fastboot" installation directory and start it's shell:
If you want to flash back the stock image. Simply run:
Code:
Code:
fastboot flashall
You can also replace all partitions if required.
itsjustbilly said:
Download the Factory State Images. Which are all flashable with fastboot: https://goo.gl/JTCwKj
Click to expand...
Click to collapse
Thanks, I was on P2a42_S038...TMO (T-Mobile, checking OTA update = you are using latest software) flashed this P2a42_S048_ and got OTA info to download latest ROM P2a42_S062_170117_ROW (103MB) :good:
veimus said:
Thanks, I was on P2a42_S038...TMO (T-Mobile, checking OTA update = you are using latest software) flashed this P2a42_S048_ and got OTA info to download latest ROM P2a42_S062_170117_ROW (103MB) :good:
Click to expand...
Click to collapse
Witaj. Mozesz napisać jak wgrałeś czysty soft do Lenovo p2. Tez mam rom z t.mobile a nigdzie nie ma poradnika jak wgrać czysty soft.Pozdrawiam
itsjustbilly said:
Taken from post 4 of the TWRP page on lenovo P2 forum
Factory Images & Systemless Mode
Q: I messed up help me?!
So you screwed up and didn't follow Rule Number One in the IT-Handbook?
Which is: Always create a backup before working on a system?
Download the Factory State Images. Which are all flashable with fastboot: https://goo.gl/JTCwKj
Place the files you want replaced into the "Minimal ADB & Fastboot" installation directory and start it's shell:
If you want to flash back the stock image. Simply run:
Code:
Code:
fastboot flashall
You can also replace all partitions if required.
Click to expand...
Click to collapse
Is there an alternative download link? What is Mega? I want to avoid these third party download utility if I can...
I put the following into a BAT file and placed it into ADB / Fastboot directory:
Code:
fastboot flash partition gpt_both0.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash dsp adspso.bin
fastboot flash system systemchunk0.img
fastboot flash system systemchunk1.img
fastboot flash system systemchunk2.img
fastboot flash system systemchunk3.img
fastboot flash system systemchunk4.img
fastboot flash system systemchunk5.img
fastboot flash system systemchunk6.img
fastboot flash system systemchunk7.img
fastboot flash system systemchunk8.img
fastboot flash system systemchunk9.img
fastboot flash system systemchunk10.img
fastboot flash system systemchunk11.img
fastboot flash system systemchunk12.img
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot erase customize
fastboot erase clogo
pause
Extract all the files listed in the BAT file or simply extract the entire archive to ADB / Fastboot and launch the BAT file.
Does this work?? @Undesirable
the above post
Oh yeah, it unbricked me and put me back to stock so I could get OTA updates for Nougat. You need the archive posted earlier in the thread though.
@Undesirable Nice and elegant solution man! Typing all this stuff was so annoying.
For those who need an alternative download source, I offer this magnet link:
Code:
magnet:?xt=urn:btih:ef05ea3af4da8a0cbb137c10621942f3ae16d46f&dn=P2a42_S048_161111_ROW_fastboot.7z
It's slow unless lots of people help to seed it.
Is it possible to flash this firmware 2a42_S048_161111_ROW_fastboot.7z on the P2c72 with firmware build number: V3.5_1652_5.1342.1_ST_p2c72 ???
I bought this phone 4GB Ram/64GB from china, but I want to put the international firmware on it.
Thanks!
itsjustbilly said:
Taken from post 4 of the TWRP page on lenovo P2 forum
Factory Images & Systemless Mode
Q: I messed up help me?!
So you screwed up and didn't follow Rule Number One in the IT-Handbook?
Which is: Always create a backup before working on a system?
Download the Factory State Images. Which are all flashable with fastboot: https://goo.gl/JTCwKj
Place the files you want replaced into the "Minimal ADB & Fastboot" installation directory and start it's shell:
If you want to flash back the stock image. Simply run:
Code:
Code:
fastboot flashall
You can also replace all partitions if required.
Click to expand...
Click to collapse
how can I replace my data partition? It's not getting formatted due to an encryption error
If fastboot erase userdata doesn't work, then use TWRP to change user data file system to EXT4 then change it back to F2FS again.
Need help...
I flashed back the stock ROM (due to encryption error in custom 7.0 ROM) using fastboot commands, but my SIGNAL WON'T WORK after I started d phone . I've tried reflashing the stock firmware (and also custom ROMs) but my phone won't detect the signal. "About phone" settings show unknown baseband and IMEI... how to get it back
---------- Post added at 08:58 AM ---------- Previous post was at 08:06 AM ----------
I've flashed 'ROW' variant of stock ROM. Is there a different version for Indian variant?
hello i have big problem.
i unlocked bootloader with command fastboot flashing unlock / the show me unlock bootloader / Write YES
unlocked done, after unlock bootloader wipe data.
Then i try install custom TWRP..i download latest TWRP,then restart mobile to fastboot ..fastboot devices show me device,and i try
fastboot flash recovery recovery.img (show mi Failed remote: (recovery_a) No such partition
so next i try next commands:
fastboot getvar current-slot
fastboot set_active other
fastboot flash boot recovery.img /done
everithing see normally done without any problems.
Reboot phone and there its,,reboot in to fastboot. Mobile not starting im stuck in fastboot.
Can you help me please?
Merlousek said:
hello i have big problem.
i unlocked bootloader with command fastboot flashing unlock / the show me unlock bootloader / Write YES
unlocked done, after unlock bootloader wipe data.
Then i try install custom TWRP..i download latest TWRP,then restart mobile to fastboot ..fastboot devices show me device,and i try
fastboot flash recovery recovery.img (show mi Failed remote: (recovery_a) No such partition
so next i try next commands:
fastboot getvar current-slot
fastboot set_active other
fastboot flash boot recovery.img /done
everithing see normally done without any problems.
Reboot phone and there its,,reboot in to fastboot. Mobile not starting im stuck in fastboot.
Can you help me please?
Click to expand...
Click to collapse
In other Treble (a/b slots) based phones, the recovery is built into the boot rom. Likely you will need to re-flash the boot.img. That's what I would try first.
numbawon said:
In other Treble (a/b slots) based phones, the recovery is built into the boot rom. Likely you will need to re-flash the boot.img. That's what I would try first.
Click to expand...
Click to collapse
so what can i do? i dont have stock recovery,and twrp recovery dont start, what fastboot command can i try to repair? only what i have its global rom downloaded from nubia homepage but i dont now how to flash stock rom and repair all this i try miflash tool,but mi flash tool not support zip formats
You are going to need extract the global rom
Follow these instructions
Extract Android OTA Payload.bin File using Payload Dumper Tool
Learn how to dump and extract Android OTA Payload.bin file to get the boot.img (for rooting with Magisk), vendor.img, and other other partition images.
www.thecustomdroid.com
Once extracted, you should then be able to fastboot flash boot_(a or b) boot.img
numbawon said:
You are going to need extract the global rom
Follow these instructions
Extract Android OTA Payload.bin File using Payload Dumper Tool
Learn how to dump and extract Android OTA Payload.bin file to get the boot.img (for rooting with Magisk), vendor.img, and other other partition images.
www.thecustomdroid.com
Once extracted, you should then be able to fastboot flash boot_(a or b) boot.img
Click to expand...
Click to collapse
okey,,its look so verry hard for me so only way for me its wait for nubia unbrick tool for Red magic 6 like unbrick tool for red magic 5.
Merlousek said:
okey,,its look so verry hard for me so only way for me its wait for nubia unbrick tool for Red magic 6 like unbrick tool for red magic 5.
Click to expand...
Click to collapse
Several of us are in the waiting game for the unbrick tool at this point.
i try bumper what you send me but another im stuck here
Merlousek said:
i try bumper what you send me but another im stuck here
Click to expand...
Click to collapse
I'll see if I can get it all extracted for you and post it someplace. I've not done it myself, I just knew where the information was.
can do for me anybody download official rom V312 https://help.redmagic.gg/hc/en-us/articles/900006829463-RedMagic-6
and extract payload.bin via payload bumper all files and reupload for me please?
i need it for flash stock room via MIflash
Thanks for help.
Merlousek said:
can do for me anybody download official rom V312 https://help.redmagic.gg/hc/en-us/articles/900006829463-RedMagic-6
and extract payload.bin via payload bumper all files and reupload for me please?
i need it for flash stock room via MIflash
Thanks for help.
Click to expand...
Click to collapse
RedMagic6-6pro - Google Drive
drive.google.com
I've extracted both versions of the rom. The "output" folder in their respective paths contains all the extracted img files. All files are included for completeness.
numbawon said:
RedMagic6-6pro - Google Drive
drive.google.com
I've extracted both versions of the rom. The "output" folder in their respective paths contains all the extracted img files. All files are included for completeness.
Click to expand...
Click to collapse
thank you so much,and i have last question,,i try flash it with miflash,,boot on edl,i see device but mi flash say couldnt find flash script,, so what program use for flashing all files?
Merlousek said:
thank you so much,and i have last question,,i try flash it with miflash,,boot on edl,i see device but mi flash say couldnt find flash script,, so what program use for flashing all files?
Click to expand...
Click to collapse
Just use fastboot. Forget mi tool.
bs3pro said:
Just use fastboot. Forget mi tool.
Click to expand...
Click to collapse
what? fastboot? i have extracted all files from phyton like boot.img , system.img ... and what fastboot do you means?
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash boot boot.img
you mean this fastboot commands?
and flash all files from stock recovery in fastboot?
bs3pro said:
Just use fastboot. Forget mi tool.
Click to expand...
Click to collapse
what? fastboot? i have extracted all files from phyton like boot.img , system.img ... and what fastboot do youmeans?
fastboot flash system system.img
fastboot flash recovery recovery.img
like that?
another error when i try flash all files from fastboot
Thanks..i try this commands on screenshot in previous reply sometimes error but fastboot flash boot boot.img works and my nubia red magic 6 its on ALIVE..Thanks all for help, You are best.
Merlousek said:
Thanks..i try this commands on screenshot in previous reply sometimes error but fastboot flash boot boot.img works and my nubia red magic 6 its on ALIVE..Thanks all for help, You are best.
Click to expand...
Click to collapse
Nice job!
Merlousek said:
hello i have big problem.
i unlocked bootloader with command fastboot flashing unlock / the show me unlock bootloader / Write YES
unlocked done, after unlock bootloader wipe data.
Then i try install custom TWRP..i download latest TWRP,then restart mobile to fastboot ..fastboot devices show me device,and i try
fastboot flash recovery recovery.img (show mi Failed remote: (recovery_a) No such partition
so next i try next commands:
fastboot getvar current-slot
fastboot set_active other
fastboot flash boot recovery.img /done
everithing see normally done without any problems.
Reboot phone and there its,,reboot in to fastboot. Mobile not starting im stuck in fastboot.
Can you help me please?
Click to expand...
Click to collapse
What TWRP did you install? Make sure you're downloading a TWRP that's available for this device. So far, to my knowledge, there isn't a TWRP recovery for this device yet.
Hello there, how did u just unlock bootloader by fastboot command? didn't use OEM unlock option on dev setting?
Btw can you share me your twrp that you used?
I need it so badly my rom bugged stuck at google account setup