Develop Bugs

[SOLVED] P5210 bricked / locked on recovery

Hello,
I try to flash again Pimpdroid after full wipe, but it's not the good way...
I flash again latest stock Sammy ROM but the tablet reboot all time in recovery (TWRP).
I flash by odin but after few minutes flash fail.
I try to flash stock or Pimpdroid by CWM, but doesn't work too: locked on Sammy Tab 3 boot screen.
Sometimes on recovery I can read /system and /data can't be mounted.
I just want to wake up my tablet to use it. :good:

StreamingMT said:
Hello,
I try to flash again Pimpdroid after full wipe, but it's not the good way...
I flash again latest stock Sammy ROM but the tablet reboot all time in recovery (TWRP).
I flash by odin but after few minutes flash fail.
I try to flash stock or Pimpdroid by CWM, but doesn't work too: locked on Sammy Tab 3 boot screen.
Sometimes on recovery I can read /system and /data can't be mounted.
I just want to wake up my tablet to use it. :good:
Click to expand...
Click to collapse
Howdy there..... do you/didn't you make a backup.....
I got a fresh rooted backup

StreamingMT said:
Hello,
I try to flash again Pimpdroid after full wipe, but it's not the good way...
I flash again latest stock Sammy ROM but the tablet reboot all time in recovery (TWRP).
I flash by odin but after few minutes flash fail.
I try to flash stock or Pimpdroid by CWM, but doesn't work too: locked on Sammy Tab 3 boot screen.
Sometimes on recovery I can read /system and /data can't be mounted.
I just want to wake up my tablet to use it. :good:
Click to expand...
Click to collapse
You probably made the same mistake I made the first time which was wiping "system" before flashing Pimpdroid. You need to Odin back to stock my friend. Odin flash TWRP and this time just do a "regular" wipe (Dalvik cache, cache, data) and then flash Pimproid. Good luck.

Yeah, I know. But I only find *.zip who can't be used with Odin. Thus I decompress with 7zip and make a *.tar.
But after few minutes "Fail!".

StreamingMT said:
Yeah, I know. But I only find *.zip who can't be used with Odin. Thus I decompress with 7zip and make a *.tar.
But after few minutes "Fail!".
Click to expand...
Click to collapse
Go to http://www.sammobile.com/firmwares/ and search for your device there. Do not mind the language of any ROM's. It is only for restoring so that you will be able to flash a custom ROM. Like Pimpdroid.
The file you will download is a .zip but if you unpack you get a .tar.md5 which you can use with ODIN.
And remember next time flashing: do NOT wipe /system. I as well made the same mistake.
Good luck!

brokie said:
Go to http://www.sammobile.com/firmwares/ and search for your device there. Do not mind the language of any ROM's. It is only for restoring so that you will be able to flash a custom ROM. Like Pimpdroid.
The file you will download is a .zip but if you unpack you get a .tar.md5 which you can use with ODIN.
And remember next time flashing: do NOT wipe /system. I as well made the same mistake.
Good luck!
Click to expand...
Click to collapse
...and also to make it easier delete the ".md5" so its just a ".tar" file before you put it in Odin.t
...another tip...make sure you use a native usb, not a hub...or something similar like that
Sent from my Blutiful Note3

Thank you for your answer. But in my first post I explain I have tried to install via TWRP / CWM / Odin a ROM. The stock rooted one from Restless (Not Pimpdroid):
http://forum.xda-developers.com/showthread.php?t=2625805
I flashed with TWRP: All done but bootloop on recovery.
I flashed with CWM: All done but reboot on Samy logo for hours.
I flash with Odin: Start the job by flashing all the small stuff, after few minutes copying the ROM I have a "Fail!" from Odin.
I can flash recoveries. But with CWM and TWRP I read in dedicated locations there is problem with mounting and/or formating partitions:
https://drive.google.com/folderview?id=0B62i2-Agz8wwb3BpZGxnN3VZaEU&usp=sharing

Ok with the Sammobile ROM:
http://www.sammobile.com/firmwares/3/?download=26250
Doesn't work with Restless stock ROM. There is a gap of 400MB between the both...
Thank you all. :good::silly::laugh:

[Q] ADB sideload with TWRP fails for 4.4.3 OTA (Nexus 7 LTE)

Hi All,
My Nexus 7 LTE is rooted with TWRP.
I've downloaded the OTA for 4.4.3 from one of the posts in the forums. It updates my razorg from KOT49H to KTU84L.
After using adb sideload, the update zip file is transferred successfully to my device, but it fails with the error message
Code:
"/system/bin/surfaceflinger" has unexpected contents.
error excuting updater binary in zip '/data/media/0/sideload.zip
Does anyone have any idea what could be causing the update to fail?
I've already restored to a stock kernel (from franco kernel) as well as uninstalled xposed framework.
Thanks!

Install stock recovery and take ota as normal. Then reinstall twrp and reroot.
If you fail update I have a backup I made with twrp you can use. Just need to extract it to your twrp backup folder and restore. It's 100% stock and was made after wiping data. Can't post a link to my Dropbox right now because of my post count but if you need it I an send it to you by other means.

Thanks for that. I think I might have to flash stock recovery and give it a shot, although I have a feeling even if I do that, it might not work as my tablet is no longer stock, since I've installed apps which made changes, such as FKU as well as CF-Lumen.

endlesstrail said:
Thanks for that. I think I might have to flash stock recovery and give it a shot, although I have a feeling even if I do that, it might not work as my tablet is no longer stock, since I've installed apps which made changes, such as FKU as well as CF-Lumen.
Click to expand...
Click to collapse
To get the OTA to work with either a stock or custom recovery the unexpected contents error will have to be fixed first. Somehow the surfaceflinger file was changed, that's a new one for me so I have no idea what could have changed it. I could upload a copy of mine if you want to try it but I do have the wifi version and don't know if they are the same. Otherwise you will need to fastboot flash the system image for the version you are running now for the update to work. Instead of doing that I would download the 4.4.3 factory image and extract the radio, system, and boot images and fastboot flash those. The bootloader did not change so that does not need to be flashed. Before flashing the images I would download the newest supersu zip and put it in your device storage, then flash the images, once that is done do not reboot, boot into recovery instead and flash the supersu zip then wipe cache and dalvik then reboot. Should take less than 15 minutes. ; )
You could also flash the factory image but that will install the stock recovery, lose root and completely wipe your device. If you are using windows you can open the flash-all.bat with a text editor like notepad and remove the -w from the text, that will prevent the userdata image from being flashed which wipes your device.

Thanks for your reply, wantabe.
I guessed as much, that if I couldn't figure out what changed the surfaceflinger, I might as well do a complete flash back to stock, which was what I did. Now it's just a matter of flashing back TWRP, restoring all the apps and waiting for 4.4.4 :good:

S2 not booting past CM logo

Okay, everything seemed fine on my s2 until the latest CM download. I install it though CWM and it seems fine but then it says
set_metadata_recursive: some changes failed
E:Error in /sdcard/firmware/cm-11-20140619-NIGHTLY-hercules.zip
(Status 7)
Installation aborted
Click to expand...
Click to collapse
Firmware is just the folder name for where i keep the files i may flash to it. I have tried other
I tried to install CM 10.2.0 and it seems to work. but then when i try and boot, it goes to the splash screen and just stays there. Did I do something wrong that is causing this?

Spud37 said:
Okay, everything seemed fine on my s2 until the latest CM download. I install it though CWM and it seems fine but then it says
Firmware is just the folder name for where i keep the files i may flash to it. I have tried other
I tried to install CM 10.2.0 and it seems to work. but then when i try and boot, it goes to the splash screen and just stays there. Did I do something wrong that is causing this?
Click to expand...
Click to collapse
"Set metadata recursive" probably means you are using a recovery that is too old.

@Spud37
Yes, it means your recovery is outdated. Here is a download link for the latest TWRP that you can flash in Odin as PDA. http://techerrata.com/file/twrp2/hercules/openrecovery-twrp-2.7.1.0-hercules.tar
This link came from teamwins website (teamw.in)
Sent from my SGH-T989

jrc2 said:
@Spud37
Yes, it means your recovery is outdated. Here is a download link for the latest TWRP that you can flash in Odin as PDA. http://techerrata.com/file/twrp2/hercules/openrecovery-twrp-2.7.1.0-hercules.tar
This link came from teamwins website (teamw.in)
Sent from my SGH-T989
Click to expand...
Click to collapse
Well there is another issue with my phone that I have actually worked around for awhile now. The MircoUSB on the phone is broken. I bought an extra battery and swap it, I also just use the SD card to copy anything to the phone. Is there a way for me to flash the phone with the new TWRP from the sd card. Why would the older TWRP not install CM 10.2.0 ROM? Do I have to go older perhaps? Thanks though. Knowing is half the battle
EDIT: Going to try and install 10.1.0 and see if it will let me boot. I figure once I can get it to boot, it will be easier to update the Recovery on the phone.
EDIT 2: No problems or errors occured when I installed CM 10.1.0.zip. However it still got stuck in a boot loop. I did however find a file called superwipe for the T mobile S2. I am wondering if that could help
EDIT 3: Okay so the superwipe worked and i am now running 10.1.0, Is it possible to install a Recovery from the phone without using odin?

What all did you wipe when you installed 10.1? There is a way to update the recovery if you can get the phone to boot. What is the latest thing you got to boot on your phone?
Sent from my HP Slate 7 using Tapatalk

jrc2 said:
What all did you wipe when you installed 10.1? There is a way to update the recovery if you can get the phone to boot. What is the latest thing you got to boot on your phone?
Sent from my HP Slate 7 using Tapatalk
Click to expand...
Click to collapse
I had wiped everything, formatted and fixed permissions, it didn't work. It wasn't until i found the Superwipe that installation worked and i was able to boot to 10.1.0. How can i update/change the recovery from the phone.
Thanks

Spud37 said:
I had wiped everything, formatted and fixed permissions, it didn't work. It wasn't until i found the Superwipe that installation worked and i was able to boot to 10.1.0. How can i update/change the recovery from the phone.
Thanks
Click to expand...
Click to collapse
It is a lot more risky if your usb port doesn't work, since you can't flash back to stock in Odin if something goes wrong. I would recommend that you get someone to fix that USB port before you make too many changes.
DISCLAIMER: I am not responsible for anything that happens to your phone. These changes could brick your phone if something goes wrong. Proceed at your own risk!
Okay, now for the tutorial. These instructions are assuming that you are already rooted. Download this file and make sure you check the md5sum. Rename it to TWRP.img and move it to /storage/sdcard. This will make the next steps easier. If you move the file somewhere else, make a note of the location of the file. If you have not already, install the terminal emulator app form the Play Store. Open it and type the following lines in it.
Code:
su
[CLICK ENTER]
Code:
dd if=/storage/sdcard/TWRP.img of=/dev/block/mmcblk0p22
(Change the path to wherever you moved the file to) [CLICK ENTER]
Reboot into recovery and wipe cache and dalvik. Reboot. If recovery says that system recovery will override it on reboot, click fix. This should update your recovery.
Have a good afternoon,
jrc2

modified changes revert back after rebooting the device

my device has been running cm11 unofficial version for quite sometime now.. the 20140921 version.. but recently I've started having a problem that the phone restarts suddenly.. so., i tried doing a fresh flash again.. but i keep getting the assert error. and the phone restarts. I have the recovery image which grarak had posted in the thread. But i donno how to use it. And now the problem has worsened because once I install any new app, the phone restarts on its own and after which it restores it back to the time when the app wasnt there.. I'm not able to make any new nandroid backups too coz the device restarts again.. I thought it might be a CWM error, so I tried flashing TWRP.. but its again an img file which i donno what to do.. sighs. .. and also, if i try to do a fresh flash of the official version of cm11 now, using the recovery i have now, will it show the assert error again?? thanks a lot in advance... hope someone can get me out of this mess..

mids1810 said:
my device has been running cm11 unofficial version for quite sometime now.. the 20140921 version.. but recently I've started having a problem that the phone restarts suddenly.. so., i tried doing a fresh flash again.. but i keep getting the assert error. and the phone restarts. I have the recovery image which grarak had posted in the thread. But i donno how to use it. And now the problem has worsened because once I install any new app, the phone restarts on its own and after which it restores it back to the time when the app wasnt there.. I'm not able to make any new nandroid backups too coz the device restarts again.. I thought it might be a CWM error, so I tried flashing TWRP.. but its again an img file which i donno what to do.. sighs. .. and also, if i try to do a fresh flash of the official version of cm11 now, using the recovery i have now, will it show the assert error again?? thanks a lot in advance... hope someone can get me out of this mess..
Click to expand...
Click to collapse
Download an app called Rashr. It can be used to flash the img file.

FoxyDrew said:
Download an app called Rashr. It can be used to flash the img file.
Click to expand...
Click to collapse
actually this problem is much more serious than that.... my device has kinda frozen in the present state... if i uninstall any apps and then restart the device the app remains there itself.. and if I try to install a new app, after restart, the app is nowhere to be seen.. so, in short, i cant install any new apps or make modifications to the previous ones... I'm not even able to install any other recovery due to this... it seems like there is some problem with the R/W rights.

mids1810 said:
actually this problem is much more serious than that.... my device has kinda frozen in the present state... if i uninstall any apps and then restart the device the app remains there itself.. and if I try to install a new app, after restart, the app is nowhere to be seen.. so, in short, i cant install any new apps or make modifications to the previous ones... I'm not even able to install any other recovery due to this... it seems like there is some problem with the R/W rights.
Click to expand...
Click to collapse
Youll have to boot into fastboot and flash the recovery. Press and hold volume up + power until the phone shuts down, then hold volume down + power until you get into Hboot. Then scroll down with the volume keys and select fastboot.
Check this out for how to flash the img files in fastboot http://androidforums.com/cdma-evo-3...lash-recovery-image-via-fastboot-sd-card.html

FoxyDrew said:
Youll have to boot into fastboot and flash the recovery. Press and hold volume up + power until the phone shuts down, then hold volume down + power until you get into Hboot. Then scroll down with the volume keys and select fastboot.
Check this out for how to flash the img files in fastboot http://androidforums.com/cdma-evo-3...lash-recovery-image-via-fastboot-sd-card.html
Click to expand...
Click to collapse
everything went well during the flashing process.. i had flashed a TWRP img.... but even this didnt solve the problem, even now its CWM as it was before.... Its just as it was before
C:\adb>fastboot flash recovery recovery.img
target reported max download size of 1298444288 bytes
sending 'recovery' (10540 KB)...
OKAY [ 1.528s]
writing 'recovery'...
OKAY [ 0.532s]
finished. total time: 2.065s

mids1810 said:
everything went well during the flashing process.. i had flashed a TWRP img.... but even this didnt solve the problem.... Its just as it was before
C:\adb>fastboot flash recovery recovery.img
target reported max download size of 1298444288 bytes
sending 'recovery' (10540 KB)...
OKAY [ 1.528s]
writing 'recovery'...
OKAY [ 0.532s]
finished. total time: 2.065s
Click to expand...
Click to collapse
Try a clean flash of the official CM11. If that doesn't work, tell me which variant your using.

FoxyDrew said:
Try a clean flash of the official CM11. If that doesn't work, tell me which variant your using.
Click to expand...
Click to collapse
tried that too quite many times.. it shows that "assert error thing", tried it with both the unofficial and official ones, and also I cant factory reset the device, if i do a factory reset and restart without flashing the rom, I'm stuck with the same rom, cant modify it whatsoever...
I'm using the a5dwg dual sim Indian variant

mids1810 said:
tried that too quite many times.. it shows that "assert error thing", tried it with both the unofficial and official ones, and also I cant factory reset the device, if i do a factory reset and restart without flashing the rom, I'm stuck with the same rom, cant modify it whatsoever...
I'm using the a5dwg dual sim Indian variant
Click to expand...
Click to collapse
Use THIS recovery.img file. Flash that in fastboot, reboot into recovery, then do a full wipe (factory reset, cache, dalvik cache, /system, /boot) and reflash the newest official CM11 nightly.

FoxyDrew said:
Use THIS recovery.img file. Flash that in fastboot, reboot into recovery, then do a full wipe (factory reset, cache, dalvik cache, /system, /boot) and reflash the newest official CM11 nightly.
Click to expand...
Click to collapse
this is the error which i get:
Installing update.....
assert failed: run_program("/system/bin/makelinks.sh") == 0
E: Error in / sorage/sdcard1/cm-11-20141025-NIGHTLY-a5_2.zip
(Status 7)
Installation aborted.

mids1810 said:
this is the error which i get:
Installing update.....
assert failed: run_program("/system/bin/makelinks.sh") == 0
E: Error in / sorage/sdcard1/cm-11-20141025-NIGHTLY-a5_2.zip
(Status 7)
Installation aborted.
Click to expand...
Click to collapse
Are you sure you flashed the recovery I linked you too. That's the EXACT error you get if you don't flash that recovery.

FoxyDrew said:
Are you sure you flashed the recovery I linked you too. That's the EXACT error you get if you don't flash that recovery.
Click to expand...
Click to collapse
Yes... I had tried using the recovery which you linked.. Is this problem in any ways related to this thread?
http://forum.xda-developers.com/showthread.php?t=2707378
I tried to add the wp_mod.ko file too... but there's no folder called as "modules" in the bin folder...
I feel its because of some problem with the read write issue.. since I'm not able to bring about any change in the system whatsoever except for changes made in the sd card.. they all get reverted after the reboot

mids1810 said:
Yes... I had tried using the recovery which you linked.. Is this problem in any ways related to this thread?
http://forum.xda-developers.com/showthread.php?t=2707378
I tried to add the wp_mod.ko file too... but there's no folder called as "modules" in the bin folder...
I feel its because of some problem with the read write issue.. since I'm not able to bring about any change in the system whatsoever except for changes made in the sd card.. they all get reverted after the reboot
Click to expand...
Click to collapse
In CM you can read and write to everywhere with no problem. You problem is weird, flash a RUU.

hmm...cant find a RUU for my variant though...

mids1810 said:
hmm...cant find a RUU for my variant though...
Click to expand...
Click to collapse
Well, try this Philz recovery, its the same one I'm using, and flash the newest build, which is the same one I'm using. If that doesn't work I honestly don't know what to tell you.

FoxyDrew said:
Well, try this Philz recovery, its the same one I'm using, and flash the newest build, which is the same one I'm using. If that doesn't work I honestly don't know what to tell you.
Click to expand...
Click to collapse
the same as before... cant get out of CWM..

mids1810 said:
Yes... I had tried using the recovery which you linked.. Is this problem in any ways related to this thread?
http://forum.xda-developers.com/showthread.php?t=2707378
I tried to add the wp_mod.ko file too... but there's no folder called as "modules" in the bin folder...
I feel its because of some problem with the read write issue.. since I'm not able to bring about any change in the system whatsoever except for changes made in the sd card.. they all get reverted after the reboot
Click to expand...
Click to collapse
@mids1810
Ok let's see, so your saying that the device won't allow to read or write, meaning 1 of 2 things.
Either you lost root access by uninstalling or modifying something, or
your device has accumulated too much background information / app data and it won't allow it to make any more changes due to limited or in other words, there's no space.
If you have CWM 6.0.4.7 then you will get the assert error every time. This is just to make sure you do have it flashed.
First thing's first.
-Go into your bootloader and go into fastboot mode. Plug it into the PC and it will say fastboot USB.
-Now download and run this .exe:
https://www.dropbox.com/s/7nn4a5xzx2pw7as/CWM_Recovery_en.exe?dl=1
-This will flash the latest 6.0.5.1 CWM automatically.
1. Now that you have the latest recovery installed,
-Boot into the recovery and wipe the CACHE and go into advanced options and wipe DALVIK CACHE. Do not press factory restore.
-Hit reboot device and test by installing an app to see if this fixes the issue.
2. If it still reboots after installing an app then download this .zip:
http://download.chainfire.eu/452/SuperSU/UPDATE-SuperSU-v2.02.zip?retrieve_file=1
-Put this zip on your SD card/internal storage
-Go into CWM and flash this .zip.
-Reboot the device and test again.
3. If BOTH of these steps failed then you will need to freshly install CM11.
-While the device is still on, put the latest CM11 on your device or recycle the same one that your using if you prefer its stability.
-Boot back into CWM and do a factory restore.
Factory restore is almost ALWAYS necessary for every time you flash CyanogenMod unless it is an update that specifically states it can be "dirty flashed" which is just a way of saying you flashed it without wiping all your information - data/cache/dalvik off of it.
Let me know how this goes for you. :laugh:

jaysoblitzed said:
@mids1810
Ok let's see, so your saying that the device won't allow to read or write, meaning 1 of 2 things.
Either you lost root access by uninstalling or modifying something, or
your device has accumulated too much background information / app data and it won't allow it to make any more changes due to limited or in other words, there's no space.
If you have CWM 6.0.4.7 then you will get the assert error every time. This is just to make sure you do have it flashed.
First thing's first.
-Go into your bootloader and go into fastboot mode.
Yeah i already had the CWM 6.0.5.1 running on my device, but I flashed it again just in case.... That didnt solve the issue.
Next I flashed the Super SU zip from my SD card(since anything I place in my internal storage vanishes once I reboot... even if rebooted in my recovery) That again didnt solve the problem
I did a fresh install of CM11, 20140921 which I am running at present due to the stability issue you mentioned.. (have tried with the official nightly a couple of times to no avail)... It shows the assert error just as before, all the time.
And yes, all the apps I uninstalled came back again, as always Completely out of any more ideas... And also I get quite many error messages often " so and so app stopped responding" and stuff
Click to expand...
Click to collapse

mids1810 said:
jaysoblitzed said:
@mids1810
Ok let's see, so your saying that the device won't allow to read or write, meaning 1 of 2 things.
Either you lost root access by uninstalling or modifying something, or
your device has accumulated too much background information / app data and it won't allow it to make any more changes due to limited or in other words, there's no space.
If you have CWM 6.0.4.7 then you will get the assert error every time. This is just to make sure you do have it flashed.
First thing's first.
-Go into your bootloader and go into fastboot mode.
Yeah i already had the CWM 6.0.5.1 running on my device, but I flashed it again just in case.... That didnt solve the issue.
Next I flashed the Super SU zip from my SD card(since anything I place in my internal storage vanishes once I reboot... even if rebooted in my recovery) That again didnt solve the problem
I did a fresh install of CM11, 20140921 which I am running at present due to the stability issue you mentioned.. (have tried with the official nightly a couple of times to no avail)... It shows the assert error just as before, all the time.
And yes, all the apps I uninstalled came back again, as always Completely out of any more ideas... And also I get quite many error messages often " so and so app stopped responding" and stuff
Click to expand...
Click to collapse
Did you try wiping JUST the Cache and the Dalvik cache WITHOUT doing a factory restore? These options are in CWMR.
Also, what is your device model? (a5_dug/chl/dwg/ul etc.)
If your not sure it says it at the top when your in the bootloader.
Click to expand...
Click to collapse

jaysoblitzed said:
mids1810 said:
Did you try wiping JUST the Cache and the Dalvik cache WITHOUT doing a factory restore? These options are in CWMR.
Also, what is your device model? (a5_dug/chl/dwg/ul etc.)
If your not sure it says it at the top when your in the bootloader.
Click to expand...
Click to collapse
yeah.. I did try.. without any difference in the results.
My device is the a5dwg dual sim Indian variant
Click to expand...
Click to collapse

jaysoblitzed said:
mids1810 said:
Did you try wiping JUST the Cache and the Dalvik cache WITHOUT doing a factory restore? These options are in CWMR.
Also, what is your device model? (a5_dug/chl/dwg/ul etc.)
If your not sure it says it at the top when your in the bootloader.
Click to expand...
Click to collapse
Follow this guide and restore your phone back to stock.
http://forum.xda-developers.com/desire-816/general/rombackup-t2811252
Its an TWRP nandroid backup of the original software, and if you have an updated version it will be able to update as well if you flash the stock recovery.
Click to expand...
Click to collapse

Please help me save my phone

FAILED (Do not allow to flash Bootloader image on Unlock device) & TWRP - Failed to mount '/firmware' (invalid argument)
I'm using the Lenovo p2a42 32gb 3gb version (India)
My phone is stuck in fastboot mode. Bootloader is unlocked.
I have the latest twrp - 3.2.2.0 as recovery.
I flashed everything except the modem and bootloader to stock.
Bootloader & modem wont flash - cannot flash unlocked bootloader error.
I have tried everything I can think of:
1. Restore to stock 7.1 (cannot flash bootloader error)
2. Relock Bootloader (not allowed error)
3. Even gave my phone to a repair guy as last resort.
No luck yet.
Its 17000 bucks worth.
And has been laid to waste due to my ****up.
I really want to repair it myself if possible.
Please help me if you can. I'm open to any and all ideas.
Thanks in advance.

Alright mate,
Download this HERE
Extract it.
Boot phone into bootloader/fastboot mode.
Connect it via cable.
Run flashall - stock reco.bat and wait until it is done. Your phone will reboot on its own.
Gimme some details if it doesn't work. Don't worry, it'll be fine.#
Also: NEVER RELOCK THE BOOTLOADER VIA COMMAND, that is a sure-way to **** it up much more.

sm00th4f3 said:
Alright mate,
Download this HERE
Extract it.
Boot phone into bootloader/fastboot mode.
Connect it via cable.
Run flashall - stock reco.bat and wait until it is done. Your phone will reboot on its own.
Gimme some details if it doesn't work. Don't worry, it'll be fine.#
Also: NEVER RELOCK THE BOOTLOADER VIA COMMAND, that is a sure-way to **** it up much more.
Click to expand...
Click to collapse
https://forum.xda-developers.com/lenovo-p2/help/stuck-bootloop-reboots-15-holding-power-t3837278
would it work for me?

LeonDsouza123 said:
https://forum.xda-developers.com/lenovo-p2/help/stuck-bootloop-reboots-15-holding-power-t3837278
would it work for me?
Click to expand...
Click to collapse
Seems like you have a faulty battery or something on your hardware side.
Fun fact: getting into recovery(twrp) is done via Fastboot since the button combo is a ***** and isn't reliable. The timing is too stupid done.
The one team rescue files always work as long as you're in Fastboot/bootloader mode.
It's worth the try

I can't thank you enough @sm00th4f3
You are my saviour. It worked perfectly & my phone is working now.
Thank you sooooo much & keep up the good work.

MadMelman said:
I can't thank you enough @sm00th4f3
You are my saviour. It worked perfectly & my phone is working now.
Thank you sooooo much & keep up the good work.
Click to expand...
Click to collapse
Glad it worked

I restored the stock firmware.
My phone boots to the start screen , after I select the language it's unable to detect or connect to the wifi or to the mobile network.
Therfore I cannot proceed to finish the setup.
TWRP shows a firmware error-
- failed to mount '/firmware' (invalid argument)
Please advice @sm00th4f3

MadMelman said:
I restored the stock firmware.
My phone boots to the start screen , after I select the language it's unable to detect or connect to the wifi or to the mobile network.
Therfore I cannot proceed to finish the setup.
TWRP shows a firmware error-
- failed to mount '/firmware' (invalid argument)
Please advice @sm00th4f3
Click to expand...
Click to collapse
You shouldn't restore stock firmware from backup.
After using rescue tool.
Setup your phone from zero.
Or skip through setup.
Reboot to bootloader.
Flash latest twrp 3.2.3 can be found on official website
Change data system format to ext4 if it's not already.
Wipe system, data, cache and dalvik
Flash custom ROM of your choice
Flash gapps
flash magisk for root if you need it
Wipe dalvik and cache
Reboot.
Setup phone.

sm00th4f3 said:
You shouldn't restore stock firmware from backup.
After using rescue tool.
Setup your phone from zero.
Or skip through setup.
Reboot to bootloader.
Flash latest twrp 3.2.3 can be found on official website
Change data system format to ext4 if it's not already.
Wipe system, data, cache and dalvik
Flash custom ROM of your choice
Flash gapps
flash magisk for root if you need it
Wipe dalvik and cache
Reboot.
Setup phone.
Click to expand...
Click to collapse
I followed your instructions. No luck yet.
After flashing the custom rom, the phone bootlooped.
I changed the data & system to ext4 , I get the failed to mount firmware error.
SCREENSHOT:
https://drive.google.com/file/d/1dhBIadnV-olRsWbQjeL8teoPCJeg2U2L/view?usp=sharing

MadMelman said:
I followed your instructions. No luck yet.
After flashing the custom rom, the phone bootlooped.
I changed the data & system to ext4 , I get the failed to mount firmware error.
SCREENSHOT:
https://drive.google.com/file/d/1dhBIadnV-olRsWbQjeL8teoPCJeg2U2L/view?usp=sharing
Click to expand...
Click to collapse
You really are new to this.
Use the rescue tool.
Let the phone boot.
Skip through setup.
Enable developer options.
Make sure and debugging is enabled.
Connect phone to pc.
Grant always access , which popups on phone.
Open a CMD, in the folder of your adb tools.
Use adb reboot bootloader.
Or use the button combo to get to bootloader /Fastboot mode
Flash twrp.
Boot twrp
Reboot to recovery twrp via reboot menu
Change file system of data to ext4
Reboot to recovery again via reboot menu in twrp.
Now use factory reset, then wipe system partition.
Flash custom ROM
Gapps
Magisk if wanted.
Reboot.
Wait max 10min.
Should work.

sm00th4f3 said:
You really are new to this.
Use the rescue tool.
Let the phone boot.
Skip through setup.
Enable developer options.
Make sure and debugging is enabled.
Connect phone to pc.
Grant always access , which popups on phone.
Open a CMD, in the folder of your adb tools.
Use adb reboot bootloader.
Or use the button combo to get to bootloader /Fastboot mode
Flash twrp.
Boot twrp
Reboot to recovery twrp via reboot menu
Change file system of data to ext4
Reboot to recovery again via reboot menu in twrp.
Now use factory reset, then wipe system partition.
Flash custom ROM
Gapps
Magisk if wanted.
Reboot.
Wait max 10min.
Should work.
Click to expand...
Click to collapse
I 'm new to this & I appreciate your help, but
I followed your instructions again yet the error remains the same.
My phone is not detecting any wifi or cellular data - so I cant proceed /skip the process of setting up my stock phone.
And when i flashed the custom rom, the firmware error shows up.
And believe me I've tried a lot, but it just wont work.
I've come too far to give up now, any suggestions?
Here is the screenshot:
https://drive.google.com/file/d/12VTE6xs1Kozg52DhQP3fgBbNeDptXz2j/view?usp=sharing

MadMelman said:
I 'm new to this & I appreciate your help, but
I followed your instructions again yet the error remains the same.
My phone is not detecting any wifi or cellular data - so I cant proceed /skip the process of setting up my stock phone.
And when i flashed the custom rom, the firmware error shows up.
And believe me I've tried a lot, but it just wont work.
I've come too far to give up now, any suggestions?
Here is the screenshot:
https://drive.google.com/file/d/12VTE6xs1Kozg52DhQP3fgBbNeDptXz2j/view?usp=sharing
Click to expand...
Click to collapse
Before flashing twrp.
Use Fastboot oem unlock
.
Try again without custom ROM this time .
I'm looking into it.

Still stuck at the start screen,
I might be wrong but here is what I think is wrong with the phone:
The modem just won't flash therefore no wifi or cellular data.
The firmware is corrupted.
Thanks for your continued support.

MadMelman said:
Still stuck at the start screen,
I might be wrong but here is what I think is wrong with the phone:
The modem just won't flash therefore no wifi or cellular data.
The firmware is corrupted.
Thanks for your continued support.
Click to expand...
Click to collapse
Hello, well i messed up my phone really bad. deleted the bootloader. Phone wasnt working. But then used blank flash to get things working again. Just that it only charges now when i run it in bootloader mode. Now what i think u can do is delete all partitions using fastboot. I dont know the terms or words to say, but you can try to delete all partitions and then flash them again and check. use the stock files or what you call those emmc, modem and those bin files that is used to flash via fastboot. It may help but can be risky. Well hope this makes any sense

Ryan Robert said:
Hello, well i messed up my phone really bad. deleted the bootloader. Phone wasnt working. But then used blank flash to get things working again. Just that it only charges now when i run it in bootloader mode. Now what i think u can do is delete all partitions using fastboot. I dont know the terms or words to say, but you can try to delete all partitions and then flash them again and check. use the stock files or what you call those emmc, modem and those bin files that is used to flash via fastboot. It may help but can be risky. Well hope this makes any sense
Click to expand...
Click to collapse
there is no need to erase your partitions.. Unless you want to brick your device for real.
But you can try it at your own discretion at risk.
i won't help any further since i don't know that much more concerning this kinda problem.
cheers

Fatal Error
MadMelman said:
I 'm new to this & I appreciate your help, but
I followed your instructions again yet the error remains the same.
My phone is not detecting any wifi or cellular data - so I cant proceed /skip the process of setting up my stock phone.
And when i flashed the custom rom, the firmware error shows up.
And believe me I've tried a lot, but it just wont work.
I've come too far to give up now, any suggestions?
Here is the screenshot:
https://drive.google.com/file/d/12VTE6xs1Kozg52DhQP3fgBbNeDptXz2j/view?usp=sharing
Click to expand...
Click to collapse
Hey buddy, I recently ran into same problem as yours. Have you found any working fix for this issue?
Please reply.