as you guys know June update killed a lot of athenes and same thing happened with my athene. and the BlankFlash is also not working after this update. so is there any update for blankFlash, post a link here.
no updated blankflash ... we should wait la
:crying::crying::crying::crying::crying::crying::crying::crying::crying::crying::crying::crying::crying::crying::crying::crying::crying::crying::crying:
siddhesh9146 said:
as you guys know June update killed a lot of athenes and same thing happened with my athene. and the BlankFlash is also not working after this update. so is there any update for blankFlash, post a link here.
Click to expand...
Click to collapse
sad..... my athne toooooo dead .... we should hope get updated soon... most of moto g4 plus athene dead ...... i dont who gonna make new updated blankflash to recover....... thanks in advance who make new one..... or any other solution... already a post is here but it didnot work out at allll..... pls someone geeks solve this
...... ISSUES LOTS OF MOTO G4 PLUS DEADDD..... EVERYTHING TRIED NO LUCK[ATHENE]XT1643]:crying::crying::crying::crying::crying::crying::crying::crying::crying::crying::crying:
tamil2692 said:
:crying::crying::crying::crying::crying::crying::crying::crying::crying::crying::crying::crying::crying::crying::crying::crying::crying::crying::crying:
sad..... my athne toooooo dead .... we should hope get updated soon... most of moto g4 plus athene dead ...... i dont who gonna make new updated blankflash to recover....... thanks in advance who make new one..... or any other solution... already a post is here but it didnot work out at allll..... pls someone geeks solve this
...... ISSUES LOTS OF MOTO G4 PLUS DEADDD..... EVERYTHING TRIED NO LUCK[ATHENE]XT1643]:crying::crying::crying::crying::crying::crying::crying::crying::crying::crying::crying:
Click to expand...
Click to collapse
Nothin
new blankflash HERE : https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-hardbrick-solved-guide-t3657761
Does not enter recovery or boot up system
as soon as the blankflash file is updated i flashed it and worked
then i flashed updated gpt and bootloader
then i tried to enter recovery mode but its not entering
and also when i unplug usb cable it is turning off
then i flashed stock rom
but still recovery and system booting are not working,enters only to fastboot that too on charging.
guyss please help me it means a lot to me.Thanks in advance
Geek_manoj said:
as soon as the blankflash file is updated i flashed it and worked
then i flashed updated gpt and bootloader
then i tried to enter recovery mode but its not entering
and also when i unplug usb cable it is turning off
then i flashed stock rom
but still recovery and system booting are not working,enters only to fastboot that too on charging.
guyss please help me it means a lot to me.Thanks in advance
Click to expand...
Click to collapse
Are you mentioning that your device only boots to fastboot now? If you press 'start', does that boot to system or not?
Which stock ROM did you flash, and can you confirm if the flash worked? How did your device brick in the first place?
echo92 said:
Are you mentioning that your device only boots to fastboot now? If you press 'start', does that boot to system or not?
Which stock ROM did you flash, and can you confirm if the flash worked? How did your device brick in the first place?
Click to expand...
Click to collapse
he didn't flashed stock rom yet, he is only trying to flash custom roms zips from recovery. someone please him that this won't work in this case:cyclops:
Blank Flash Files Moto G4 Plus
Yes I have the correct blank flash files for Moto G4 Plus. I was used it on my device XT1643 and it is working.
echo92 said:
Are you mentioning that your device only boots to fastboot now? If you press 'start', does that boot to system or not?
Which stock ROM did you flash, and can you confirm if the flash worked? How did your device brick in the first place?
Click to expand...
Click to collapse
yes,the device boots only to fastboot that too only when charged.if i press start that doesn't boot to system.I flashed "ATHENE_NPJS25.93-14-8_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip".I bricked by doing softare update after reflashing stock rom.it also doesnt enter recovery
---------- Post added at 02:09 AM ---------- Previous post was at 02:05 AM ----------
siddhesh9146 said:
he didn't flashed stock rom yet, he is only trying to flash custom roms zips from recovery. someone please him that this won't work in this case:cyclops:
Click to expand...
Click to collapse
sorry if you dont understand.but i flash stock rom "ATHENE_NPJS25.93-14-8_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip" in stock recovery.if u could help me please let me know.thanks in advance
Geek_manoj said:
yes,the device boots only to fastboot that too only when charged.if i press start that doesn't boot to system.I flashed "ATHENE_NPJS25.93-14-8_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip".I bricked by doing softare update after reflashing stock rom.it also doesnt enter recovery
---------- Post added at 02:09 AM ---------- Previous post was at 02:05 AM ----------
sorry if you dont understand.but i flash stock rom "ATHENE_NPJS25.93-14-8_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip" in stock recovery.if u could help me please let me know.thanks in advance
Click to expand...
Click to collapse
I knew that, that file was for flashing in fastboot mode
but you flashed in recovery
Geek_manoj said:
yes,the device boots only to fastboot that too only when charged.if i press start that doesn't boot to system.I flashed "ATHENE_NPJS25.93-14-8_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip".I bricked by doing softare update after reflashing stock rom.it also doesnt enter recovery
---------- Post added at 02:09 AM ---------- Previous post was at 02:05 AM ----------
sorry if you dont understand.but i flash stock rom "ATHENE_NPJS25.93-14-8_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip" in stock recovery.if u could help me please let me know.thanks in advance
Click to expand...
Click to collapse
As siddhesh9146 had mentioned, the Athene stock ROM cannot be flashed in stock recovery, it is not a flashable zip file. You need a computer and ADB set up, extract the zip on your computer and use the flashing commands in the fastboot ROM thread to flash a stock ROM.
Until you've flashed the stock ROM, I'm not even sure if you have stock recovery, or a stock system on your device. The supplied blank flash does not appear to have a functioning recovery included with it.
echo92 said:
As siddhesh9146 had mentioned, the Athene stock ROM cannot be flashed in stock recovery, it is not a flashable zip file. You need a computer and ADB set up, extract the zip on your computer and use the flashing commands in the fastboot ROM thread to flash a stock ROM.
Until you've flashed the stock ROM, I'm not even sure if you have stock recovery, or a stock system on your device. The supplied blank flash does not appear to have a functioning recovery included with it.
Click to expand...
Click to collapse
I m sorry.I must have described in a better way.I actually mean that i used computer extracted the firmware and then i ran oem_flash,which is the actual way i suppouse in fastboot mode(i ommited for fastboot as stock recovery in previous post,sorry).but i dont know why it still doesnt enter recovery or enter into system or work without plug.i even tried flashing updated gpt.bin and bootloader files again followed by the rom,but noting happened
---------- Post added at 04:24 PM ---------- Previous post was at 04:19 PM ----------
echo92 said:
As siddhesh9146 had mentioned, the Athene stock ROM cannot be flashed in stock recovery, it is not a flashable zip file. You need a computer and ADB set up, extract the zip on your computer and use the flashing commands in the fastboot ROM thread to flash a stock ROM.
Until you've flashed the stock ROM, I'm not even sure if you have stock recovery, or a stock system on your device. The supplied blank flash does not appear to have a functioning recovery included with it.
Click to expand...
Click to collapse
siddhesh9146 said:
I knew that, that file was for flashing in fastboot mode
but you flashed in recovery
Click to expand...
Click to collapse
hey,i ommited in the post telling that i did it in recovery(sorry for that)actually it doesnt enter recovery,which i already mentioned.thanks for being concerned
Geek_manoj said:
I m sorry.I must have described in a better way.I actually mean that i used computer extracted the firmware and then i ran oem_flash,which is the actual way i suppouse in fastboot mode(i ommited for fastboot as stock recovery in previous post,sorry).but i dont know why it still doesnt enter recovery or enter into system or work without plug.i even tried flashing updated gpt.bin and bootloader files again followed by the rom,but noting happened
---------- Post added at 04:24 PM ---------- Previous post was at 04:19 PM ----------
hey,i ommited in the post telling that i did it in recovery(sorry for that)actually it doesnt enter recovery,which i already mentioned.thanks for being concerned
Click to expand...
Click to collapse
So, you booted your device to the bootloader screen (not to recovery), connected your device to your computer, and you've flashed using the OEM_flash script, and yet you're unable to reboot to recovery?
Sounds like your stock ROM flash did not work the first time, leaving you without a recovery or a system. Try the following just to confirm:
1) Ensure your adb folder contains the extracted NPJS25.93-14-8 stock ROM (all the files), should be about 2 GB for the stock ROM. Also confirm that the OEM flash script is in the same location (so your adb folder should have the stock ROM, the flash script and the adb and fastboot.exe and adb.dlls)
2)Reboot your device to the bootloader (power down, then press the power and volume down keys to boot to bootloader) and connect your device to your computer.
3)In the adb terminal, type 'fastboot devices', without the quotes. If communicating, you should see your device respond with its serial number.
4)If communicating, run the OEM flash script again.
5)If your device does not boot properly, then reboot to bootloader.
5a)Copy each of the commands from the script (you can open the script in a text editor) and paste them in the adb terminal window and run each one by pressing Enter on your keyboard. You should see the command report [OKAY] if it's flashed. Any errors, let us know, that might point more accurately to what might be going on.
As an aside, this is one of the reasons why downgrading isn't a good idea....
echo92 said:
So, you booted your device to the bootloader screen (not to recovery), connected your device to your computer, and you've flashed using the OEM_flash script, and yet you're unable to reboot to recovery?
Sounds like your stock ROM flash did not work the first time, leaving you without a recovery or a system. Try the following just to confirm:
1) Ensure your adb folder contains the extracted NPJS25.93-14-8 stock ROM (all the files), should be about 2 GB for the stock ROM. Also confirm that the OEM flash script is in the same location (so your adb folder should have the stock ROM, the flash script and the adb and fastboot.exe and adb.dlls)
2)Reboot your device to the bootloader (power down, then press the power and volume down keys to boot to bootloader) and connect your device to your computer.
3)In the adb terminal, type 'fastboot devices', without the quotes. If communicating, you should see your device respond with its serial number.
4)If communicating, run the OEM flash script again.
5)If your device does not boot properly, then reboot to bootloader.
5a)Copy each of the commands from the script (you can open the script in a text editor) and paste them in the adb terminal window and run each one by pressing Enter on your keyboard. You should see the command report [OKAY] if it's flashed. Any errors, let us know, that might point more accurately to what might be going on.
As an aside, this is one of the reasons why downgrading isn't a good idea....
Click to expand...
Click to collapse
Hey,thanks for bothering.But,it didnt work.i have got no error.But still mobile enters only fastboot that too when charging( only fastboot again).
I tried to clear cache memory by booting my g4 plus in recovery mode. the phone hanged up and switched off now unable to boot. tried the blank flash file to update but the same is not working. Can any one help !!
Related
EDIT - UPDATED INSTRUCTIONS 12th May 2014
Due to the partition sizes being different in the GPE RUU it is not simply a case of flashing a sense rom in recovery. You will experience problems if you do this. This might involve getting the storage encrption message, bootloops, freezing etc etc.
This thread is specifically for users who have problems getting back to sense. Solution is below. If you have alternative solutions that have worked without issues please post.
I have tried to make them as simple as possible. This guide assumes you are S-Off otherwise how did you get here. (
This does not apply if you have installed a GPE ROM. You can flash as normal through recovery. (using instructions of new rom)
Thanks to @exad for his continuing support/assistance throughout the thread, as well as @graffixnyc for the GPE RUU and both he and @navalynt for finding the initial fixes.
It will be much easier if you have your new Rom on your external sdcard prior to starting this. It will also stop a number of problems if you have SuperCID (11111111) If you don't know how to - FASTBOOT Commands
1. Enter the command "fastboot oem readcid". Make and KEEP a note of your original CID.
2. Enter the command "fastboot oem writecid 11111111"
3. Enter the command "fastboot read cid" [it should confirm your CID is 11111111]
4. Press the volume down button twice on your phone and navigate to reboot bootloader, then hit power button to reboot the bootloader.
5. Bootloader will also say "CID-11111111" now to confirm (Thanks to @xl VipeR lx ) Also to @umjammerlammy for the GENTLE reminders to include this
Make sure the firmware file and twrp recovery are in your Android directory on your PC - Mine is
C:\Users\Grentuu\AppData\Local\Android\android-sdk\platform-tools\
During this process you may find that when you reboot the phone starts to boot into android. Mine did but simply had the GPE animated logo but never entered GPE. All you do is press Vol up and power for about 10 seconds to reset. As soon as it resets press vol down and power to get back to bootloader.
Flash 1.54.401.5 firmware from Here
Fastboot Method
Boot device into FASTBOOT mode either by adb reboot bootloader or Vol down & Power (device should show FASTBOOT USB)
Make sure the firmware file to be flashed is in your android folder
Open a command prompt from the folder where fastboot resides. (Hold shift key/right click in the dir to get menu - left click on Open Command Prompt here.)
Run the following commands:
fastboot oem rebootRUU (this will reboot the device into RUU mode in preparation for zip flashing)
fastboot flash zip 1.54.401.5-W_Splash.zip (the name of the zip should EXACTLY match the name of the file you're flashing)
It will fail the first time. Run the same command AGAIN until you see it has flashed successfully.
I repeat - Run the same command TWICE until you see it has flashed successfully.
Once complete, type fastboot reboot-bootloader The hyphen is required.
Some users have stated this firmware (1.54.401.5) did not work for them as they weren't GSM and reboots just threw them back to recovery. If this happens try a stock (your original e.g. T-mobile) firmware then follow the rest of the process.
Boot into stock recovery
Factory reset
Reboot into bootloader
Flash TWRP - command = fastboot flash recovery openrecovery-twrp-2.7.0.2-m8.img (The must match exactly the name of the recovery you are flashing and remember the recovery file must be in your android folder)
Boot into TWRP
Go into Wipe menu
do a full factory reset wipe
Reboot back into recovery
Install rom
Profit
These have worked for me everytime (Change count =19)
Thanks for this. I'm about to give it a shot now.
Sent from my HTC One_M8 using XDA Premium 4 mobile app
---------- Post added at 05:08 PM ---------- Previous post was at 04:40 PM ----------
For some reason the firmware wont flash in twrp. Should I sideload the firmware?
Sent from my GT-P5210 using XDA Premium 4 mobile app
To flash a firmware you must be in bootloader/fastboot mode.
Fastboot oem rebootRUU
Fastboot flash zip firmwarefilename.zip
Then again
Fastboot flash zip firmwarefilename.zip
Fastboot reboot-bootloader
exad said:
To flash a firmware you must be in bootloader/fastboot mode.
Fastboot oem rebootRUU
Fastboot flash zip firnwarefilename.zip
Then again
Fastboot flash zip firnwarefilename.zip
Fastboot reboot-bootloader
Click to expand...
Click to collapse
Thanks. Understood, I was just reviewing my steps for the conversion. I really just want to try out that new Sense rom and then I'll probably revert back. BRB...I'll let you know how it goes.
Bear in mind you must have S-off to flash a firmware that way.
exad said:
To flash a firmware you must be in bootloader/fastboot mode.
Fastboot oem rebootRUU
Fastboot flash zip firmwarefilename.zip
Then again
Fastboot flash zip firmwarefilename.zip
Fastboot reboot-bootloader
Click to expand...
Click to collapse
Those are the instructions in post 1 the original thread.
The issue is with people wanting to go back to sense
This thread is about returning to sense. Flashing a firmware is always the same. It's the firmware itself that's different...
Here is where I am at..
I converted to GP easily and it worked well.. I wanted to convert back so I installed twrp first, then through twrp installed the 1.54.401.5 firmware.
Installing that firmware removed twrp and the rom. So I am without an OS at all, and have stock recovery.
Is there anyway I can flash a custom recovery or a rom via the stock firmware/recovery?
My computer will not recognize adb devices. But it used to obviously.
I have an SD card.
Any help and I will be sooo grateful. (maybe even donate)
Thanks!
You can't flash a firmware through recovery... You can flash a stock recovery after the steps listed above if you like. See the stock backup thread.
You can flash any recovery through fastboot... Adb only works with the rom booted or with custom recovery booted.
Thanks will try it out.
exad said:
You can't flash a firmware through recovery... You can flash a stock recovery after the steps listed above if you like. See the stock backup thread.
You can flash any recovery through fastboot... Adb only works with the rom booted or with custom recovery booted.
Click to expand...
Click to collapse
So what do I do in this situation with no rom installed only 1.54 firmware and stock recovery.
Flash twrp
exad said:
Flash twrp
Click to expand...
Click to collapse
I have no rom installed, so it wont show in adb devices.
PunchLick said:
I have no rom installed, so it wont show in adb devices.
Click to expand...
Click to collapse
You flash recovery via fastboot, no need for a rom.
Just make sure you have the proper fastboot drivers from htc.
Dmaxon said:
You flash recovery via fastboot, no need for a rom.
Just make sure you have the proper fastboot drivers from htc.
Click to expand...
Click to collapse
ADB devices shows no devices. If i had custom recovery this would be so much easier, but im using 1.54.401.5 firmware with stock recovery and no ROM.
Just dont know what to do to get a working device again. All i can do is boot into stock recovery, hboot and fastboot.. but computer shows no device.
PunchLick said:
ADB devices shows no devices. If i had custom recovery this would be so much easier, but im using 1.54.401.5 firmware with stock recovery and no ROM.
Just dont know what to do to get a working device again. All i can do is boot into stock recovery, hboot and fastboot.. but computer shows no device.
Click to expand...
Click to collapse
I would recommend the All-In-One Toolkit. This will allow you to fastboot the recovery, even though the pc doesn't recognize it. This has worked for me in the past.
Meanwhile, I get the following error message when attempting to flash the 1.54...
Any suggestions guys???
Problem solved. I had not supercid. After I did that, I was able to successfully flash 1.54...
Why post steps if your not willing to help?
The steps in the OP can still cause issues for some people.
Sent from my HTC One_M8 using Tapatalk
Ideas4ya said:
I would recommend the All-In-One Toolkit. This will allow you to fastboot the recovery, even though the pc doesn't recognize it. This has worked for me in the past.
Meanwhile, I get the following error message when attempting to flash the 1.54...
Any suggestions guys???
Problem solved. I had not supercid. After I did that, I was able to successfully flash 1.54...
Click to expand...
Click to collapse
Can you elaborate a little on which options etc, because that sounds fantastic and would help me so much!
PunchLick said:
Can you elaborate a little on which options etc, because that sounds fantastic and would help me so much!
Click to expand...
Click to collapse
When you open the all in one...the 3rd option on the top right is what you need. Follow the step, even if fastboot says device is not connected, this will still send the recovery to your device as long as you're in the bootloader.
I will never understand why people play with there phones and have no understanding of adb and fastboot commands with the bootloader. if people would learn that first there wouldn't be so many threads when they get stuck. tool kits are bad it makes people lazy. but I appreciate the devs who make them
So yeah I accidentally wiped my partitions as if I were installing a rom. Am I screwed until I get to a pc?
P.s. Out of all days to delete my backup rom file ?
Just set it to boot loader mode and flash stock images...I'm sure there's a tutorial on how to do it..I have the program installed on my computer ready for any time I brick my phone lol but I don't remember the name of the program right now
Edit: heres the link to the method I use http://forum.xda-developers.com/showthread.php?t=3258493
I'm assuming the OP doesn't have a PC due to the last statement he made. I would say yes, nothing you can do until you can get to a PC and flash stock images via Fastboot. Unless you have a ROM zip on your phone that is....which I'm assuming you don't.
You're kinda stuck, you need a PC to flash the factory images. TWRP can't flash OTA's anyway, so don't try that again either. I'd strongly recommend not using a toolkit to flash the factory images too. I have a detailed guide here:
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
Hey guys, having a similar issue than zachbuilds. While rooting my nexus 6p on NRD9M, I formatted to system partition for root to stick and noticed twrp stated I have no OS installed. At that point I was going to flash stock image file when my nexus reverted from default MTP to charge only and now my Mac is unable to recognize my device Ann's now adb is non operable. I tried to fastboot adb commands but that isn't working either. Any one have any suggestions. I'm on stock with twrp custom recovery, no other changes were made to my device. Also, recovery and bootloader are accessible. Thanks for any help given.
Snakielols1984 said:
Hey guys, having a similar issue than zachbuilds. While rooting my nexus 6p on NRD9M, I formatted to system partition for root to stick and noticed twrp stated I have no OS installed. At that point I was going to flash stock image file when my nexus reverted from default MTP to charge only and now my Mac is unable to recognize my device Ann's now adb is non operable. I tried to fastboot adb commands but that isn't working either. Any one have any suggestions. I'm on stock with twrp custom recovery, no other changes were made to my device. Also, recovery and bootloader are accessible. Thanks for any help given.
Click to expand...
Click to collapse
Can fastboot see your device when you're in bootloader?
Yes fastboot is able to reconize my device.
Snakielols1984 said:
Yes fastboot is able to reconize my device.
Click to expand...
Click to collapse
Best just to flash back to factory images. Be cautious if you've flashed the Android N OTA though, there are some strange things going on with people trying to flash back to M. Read up before you flash.
I've actually tried flashing stock images but every time I tried to run fastboot command I get these errors, "command not found" and I believe the other erro is "file path not found". There's another error that I can't remember off the top of my head what it. When I get home I'll try to run the commands again and see what errors I get
---------- Post added at 11:09 PM ---------- Previous post was at 11:08 PM ----------
elfrosto said:
Best just to flash back to factory images. Be cautious if you've flashed the Android N OTA though, there are some strange things going on with people trying to flash back to M. Read up before you flash.
Click to expand...
Click to collapse
on another note I have not flashed Android N OTA. I downloaded that and install via OTA.
wrong thread
so just attempted to flash stock images and I get an error "cannot load bootloader-angler-angler-03.54.img". the tutorial I am using is Heisenberg's How-To Guide For Beginners. I followed the instructions step by step. Please is anyone can chime in, please do. Greatly appreciated!
Snakielols1984 said:
so just attempted to flash stock images and I get an error "cannot load bootloader-angler-angler-03.54.img". the tutorial I am using is Heisenberg's How-To Guide For Beginners. I followed the instructions step by step. Please is anyone can chime in, please do. Greatly appreciated!
Click to expand...
Click to collapse
What bootloader version are you on currently? Although updated bootloader is recommend, you should be able to skip this step without any issues.
Sorry for late response but currently I am bootloader: angler-3.58
---------- Post added at 12:27 AM ---------- Previous post was at 12:19 AM ----------
This is the error I get when using fastboot commands to flash stock images "error: cannot load 'MacintoshHD/angler/images/radio-angler-angler-03.61.img'". I received same error when trying to flash bootloader
Snakielols1984 said:
Sorry for late response but currently I am bootloader: angler-3.58
---------- Post added at 12:27 AM ---------- Previous post was at 12:19 AM ----------
This is the error I get when using fastboot commands to flash stock images "error: cannot load 'MacintoshHD/angler/images/radio-angler-angler-03.61.img'". I received same error when trying to flash bootloader
Click to expand...
Click to collapse
Please post the entire command you are using, as written in your terminal prompt. "No command" sounds like an unrecognized command is being issued. We must use ./ in addition to the fastboot or adb command in order for OSX to execute the action. If following Heisenberg's guide for fastboot, the lone change you need to make for OSX is:
./fastboot devices
./fastboot flash
./fastboot reboot
./ADB devices
Try this out and post your results.
Sent from my Nexus 5X using Tapatalk
Just throwing this out there, it is possible to flash an OTA in TWRP. You still need a PC but its do-able.... I flashed Android N Final to my 6P yesterday by copying the OTA zip (uploaded thanks to another member) to SD, Wiped device as I normally would with any other ROM (left SD intact obviously), Flashed OTA ZIP, rebooted straight to bootloader after flash, fastboot erase boot, fastboot erase recovery, fastboot flashed DECRYPTED BOOT.img (which can be found easily), fastboot flashed TWRP 3.0.2-1 (version just released for N), fastboot format userdata, fastboot format cache, reboot from bootloader directly into TWRP, flashed superSU 2.74, reboot system..... Phone runs beautifully. Not a single issue. Entire process from start to finish was less than 10 minutes.
Its not the most practical route but it does indeed work. OTA just hes to contain the entire Image. I should also mention that this was a jump from a Marshmallow based rom (RR) so you don't have to be on an N preview in order to do this....
First of all i want to say thankyou to the xda community who help people like us and build rooting and other flashing softwares.
So, this is probably my first post on xda, first for sure when i'm stuck and asking for help
Background of the Problem:
I was on OS 2.1.2 rooted with twrp recovery. (was really happy with my phone)
MM 3.0.2 upgrade comes and i decide to upgrade my phone manually (since ota was disabled due to root)
All goes well in first try..(did a dirty flash) OP2 3.0.2 runs smoothly
However, i found out i had lost root and couldn't boot into recovery.
I ignored for a month when i decided it was too hard to go on without root now..
So i searched through a few forums, went into fastboot tried oem unlocking.. failed.. Stuck hard in the bootloop..
Searched for about 3hours and used the MSM tool to finally unlock bootloader.. but still stuck at bootloop and no luck with recovery.. I couldn't boot into my installed rom(3.0.2)
I flashed recovery from OOS 2.1.2 or 2.0.1 and booted into recovery and flashed 2.1.2 again..
So now, 2.1.2 runs fine on my phone
I have refered to these guides/files while trying to install 3.0.2 or trying to recover my phone
http://forum.xda-developers.com/onep...s-3-x-t3392826
https://www.androidfilehost.com/?w=f...f4a13afecc347f
https://www.androidfilehost.com/?w=f...9e2340a15d9033
https://forums.oneplus.net/threads/u...plus-2.347607/
http://forum.xda-developers.com/oneplus-2/general/zip-oxygenos-3-x-t3392826
PROBLEM:
Whenever i update my phone to 3.0.2, it stucks at the bootloop (showing oneplus logo and cmd showing it in fastboot mode)
i lose recovery and rom
i have tried flashing grarak recovery and hybrid recovery (both of which i believe are modded recovery for OOS MM)
In cmd, fastboot flash command completes without any problem but the phone doesnt boot to recovery and both give an error while giving the fastboot boot command
" downloading boot.img
OKAY
booting...
FAILED (remote: dtb not found)"
finished. "
Please suggest me something so that i can boot into 3.0.2 without bootloop problem.. 3.0.2 runs really smooth..
and additionally if possible, i would like to root but thats secondary.
Thankyou guys in advance. Please help a brother out
Sahaj4 said:
First of all i want to say thankyou to the xda community who help people like us and build rooting and other flashing softwares.
So, this is probably my first post on xda, first for sure when i'm stuck and asking for help
Background of the Problem:
I was on OS 2.1.2 rooted with twrp recovery. (was really happy with my phone)
MM 3.0.2 upgrade comes and i decide to upgrade my phone manually (since ota was disabled due to root)
All goes well in first try..(did a dirty flash) OP2 3.0.2 runs smoothly
However, i found out i had lost root and couldn't boot into recovery.
I ignored for a month when i decided it was too hard to go on without root now..
So i searched through a few forums, went into fastboot tried oem unlocking.. failed.. Stuck hard in the bootloop..
Searched for about 3hours and used the MSM tool to finally unlock bootloader.. but still stuck at bootloop and no luck with recovery.. I couldn't boot into my installed rom(3.0.2)
I flashed recovery from OOS 2.1.2 or 2.0.1 and booted into recovery and flashed 2.1.2 again..
So now, 2.1.2 runs fine on my phone
I have refered to these guides/files while trying to install 3.0.2 or trying to recover my phone
http://forum.xda-developers.com/onep...s-3-x-t3392826
https://www.androidfilehost.com/?w=f...f4a13afecc347f
https://www.androidfilehost.com/?w=f...9e2340a15d9033
https://forums.oneplus.net/threads/u...plus-2.347607/
http://forum.xda-developers.com/oneplus-2/general/zip-oxygenos-3-x-t3392826
PROBLEM:
Whenever i update my phone to 3.0.2, it stucks at the bootloop (showing oneplus logo and cmd showing it in fastboot mode)
i lose recovery and rom
i have tried flashing grarak recovery and hybrid recovery (both of which i believe are modded recovery for OOS MM)
In cmd, fastboot flash command completes without any problem but the phone doesnt boot to recovery and both give an error while giving the fastboot boot command
" downloading boot.img
OKAY
booting...
FAILED (remote: dtb not found)"
finished. "
Please suggest me something so that i can boot into 3.0.2 without bootloop problem.. 3.0.2 runs really smooth..
and additionally if possible, i would like to root but thats secondary.
Thankyou guys in advance. Please help a brother out
Click to expand...
Click to collapse
Follow this step one by one ..
1. Flash this recovery via firstboot
https://drive.google.com/file/d/0B0OiN2evbEPuNk5KejhvLWsyeDg/view?usp=drivesdk
2. Now boot into recovery and flash this zip firmware .
https://drive.google.com/file/d/0B0OiN2evbEPucnBkUGZIdlZCSnM/view?usp=drivesdk
3. Now boot into new recovery and flash oxygen os 3.x.x .
That's it.
4. If camera or other sensor not work flash this persist.img file via firstboot.
https://drive.google.com/file/d/0B0OiN2evbEPueVNEQTdUSHJYTHM/view?usp=drivesdk
Jyoti_re said:
Follow this step one by one ..
1. Flash this recovery via firstboot
https://drive.google.com/file/d/0B0OiN2evbEPuNk5KejhvLWsyeDg/view?usp=drivesdk
2. Now boot into recovery and flash this zip firmware .
https://drive.google.com/file/d/0B0OiN2evbEPucnBkUGZIdlZCSnM/view?usp=drivesdk
3. Now boot into new recovery and flash oxygen os 3.x.x .
That's it.
4. If camera or other sensor not work flash this persist.img file via firstboot.
https://drive.google.com/file/d/0B0OiN2evbEPueVNEQTdUSHJYTHM/view?usp=drivesdk
Click to expand...
Click to collapse
Heyy.. Thanks a lot Jyoti_re! It worked out perfectly..
I have done till step 3.. The phone booted into 3.0.2
The sensors are not working. I will flash the presist.img as you said in step 4
However, i have encountered a problem. My OP2 is a 64 GB version. But now the internal storage shows 7gb free out of 9.66 GB.. Earlier it used to show 54GB instead of 9.66..
What should i do?
Thanks again
Yes u must have to flash persist.img via firstboot mode by typing [ fastboot flash persist ] for sensor correctly working.
Install es file explorar from play store and check which folder taking More space
don't forget to press thanks if I helped u.
Thanks a lot Jyoti! /
Yeah i got it.. Flashed the persist img.
i searched through the forums.. somehow my device got the 16gb version img.. i dont know how..
i had to flash userdata64G.img as well
Now it all works perfectly.. sensors are working.. data storage is back at 54gb..
Thanks a lot! I had been stuck on this bootloop since 3 days..
and i pressed the thanks button.. i will press it 100 times over if possible Thanks again! Cheers!
Just to confirm.. Can i flash supersu via recovery now to get root? i hope it wont lead me to bootloops.. If there is some specific supersu file to flash for OOS 3.0.2 please guide me to it.. Thanks!
Sahaj4 said:
Just to confirm.. Can i flash supersu via recovery now to get root? i hope it wont lead me to bootloops.. If there is some specific supersu file to flash for OOS 3.0.2 please guide me to it.. Thanks!
Click to expand...
Click to collapse
Flash this SuperSU
https://drive.google.com/file/d/0B0OiN2evbEPuZk1KSk1hYUpEazA/view?usp=drivesdk
don't forget to press thanks if I helped u.
OP2 stuck in bootloop on upgrading from 2.0.2 to 3.0.2
Hi guys and thanks to all xda developers community for helping us. I'm trying to root my op2 via fastboot,using the comand fastboot oem unlock,but always having this message: <remote oem unlock is disabled>. And when i try to use volume down+power to get in recovery mode the op2 vibrate and flashes the screen and do nothing. I'm not having access to do anything with the op2. Please help...
ciroportugues said:
Hi guys and thanks to all xda developers community for helping us. I'm trying to root my op2 via fastboot,using the comand fastboot oem unlock,but always having this message: <remote oem unlock is disabled>. And when i try to use volume down+power to get in recovery mode the op2 vibrate and flashes the screen and do nothing. I'm not having access to do anything with the op2. Please help...
Click to expand...
Click to collapse
Have u enabled OEM unlocking in developer option ??
No i forgot to enable...
No i forgot to enable... What can i do now?
---------- Post added at 06:44 AM ---------- Previous post was at 06:39 AM ----------
Jyoti_re said:
Have u enabled OEM unlocking in developer option ??
Click to expand...
Click to collapse
No iforgot to enable...
What can i do now?
ciroportugues said:
No i forgot to enable... What can i do now?
---------- Post added at 06:44 AM ---------- Previous post was at 06:39 AM ----------
No iforgot to enable...
What can i do now?
Click to expand...
Click to collapse
Go thru "METHOD 1" of this post and fill free to contact if u face any problem.
https://forums.oneplus.net/threads/...ck-guide-for-a-hard-bricked-oneplus-2.347607/
Jyoti_re said:
Go thru "METHOD 1" of this post and fill free to contact if u face any problem.
https://forums.oneplus.net/threads/...ck-guide-for-a-hard-bricked-oneplus-2.347607/
Click to expand...
Click to collapse
Hi. I tried to do every steps in method 1,but when i try to enter to recovery mode my op2 vibrate and flash the screen till i stop pressing the power button,and never get into recovery mode.
ciroportugues said:
Hi. I tried to do every steps in method 1,but when i try to enter to recovery mode my op2 vibrate and flash the screen till i stop pressing the power button,and never get into recovery mode.
Click to expand...
Click to collapse
After use the recovery tool the op2 restarts and stuck into powered by android nothing more happens.
ciroportugues said:
After use the recovery tool the op2 restarts and stuck into powered by android nothing more happens.
Click to expand...
Click to collapse
What does the Device Manager show when you connect your phone? By what name is it identified?
Thanks for reply. When i put press volume+and- shows qualcomm hs-usb qdloader9008 (com29),and when i put into fastboot shows android bootloader interface,and when stucks into start shows the same(android bootloader interface).
---------- Post added at 10:06 PM ---------- Previous post was at 09:37 PM ----------
Sahaj4 said:
What does the Device Manager show when you connect your phone? By what name is it identified?
Click to expand...
Click to collapse
Thanks for reply. When i put press volume+and- shows qualcomm hs-usb qdloader9008 (com29),and when i put into fastboot shows android bootloader interface,and when stucks into start shows the same(android bootloader interface).
When you are in fastboot mode..
Try giving the command
"fastboot continue"
or
"fastboot reboot-bootloader"
"fastboot continue"
(without quotes) if your system files are not corrupt, it will boot you into your rom.. and then enable oem unlocking from settings
Tried this commands and the system reboots and stucks on the screen powered by android.
---------- Post added at 12:27 AM ---------- Previous post was at 12:25 AM ----------
Sahaj4 said:
When you are in fastboot mode..
Try giving the command
"fastboot continue"
or
"fastboot reboot-bootloader"
"fastboot continue"
(without quotes) if your system files are not corrupt, it will boot you into your rom.. and then enable oem unlocking from settings
Click to expand...
Click to collapse
Tried this commands but the sistem reboots and stucka on powered by android
ciroportugues said:
Tried this commands and the system reboots and stucks on the screen powered by android.
---------- Post added at 12:27 AM ---------- Previous post was at 12:25 AM ----------
Tried this commands but the sistem reboots and stucks on powered by android
Click to expand...
Click to collapse
Hi. want to know if you anymore command to help me? thanks for help
ciroportugues said:
Hi. want to know if you anymore command to help me? thanks for help
Click to expand...
Click to collapse
I don't know much.. only as much as i have tried..
try running the command
fastboot oem device-info
if your device is unlocked, you are lucky! then there are many options
but if your device is locked.. then as far as i know, msm tool is your only saviour
try using this guide to unbrick your phone
https://forums.oneplus.net/threads/...ck-guide-for-a-hard-bricked-oneplus-2.347607/
Hello,
I tried to root my Zenfone 2 ZE500KL but i didn't see that the method don't work with Android 6. Now, when I start my phone i have the message "ERROR: Can't load invalid boot image" with the ASUS Logo.
I tried a lot of things using ADB, like go to the recovery mode for format, installing from the ROM again from my SD. But the message stay...
I need your help now, car I don't find anything... Thanks !
CzeroXCI said:
Hello,
I tried to root my Zenfone 2 ZE500KL but i didn't see that the method don't work with Android 6. Now, when I start my phone i have the message "ERROR: Can't load invalid boot image" with the ASUS Logo.
I tried a lot of things using ADB, like go to the recovery mode for format, installing from the ROM again from my SD. But the message stay...
I need your help now, car I don't find anything... Thanks !
Click to expand...
Click to collapse
Download this boot.img for Marshmallow v.13.10.7.1
https://drive.google.com/file/d/0B7F3ZXr565GkV2N3WjBoeEZXUUU/view?usp=drivesdk
The command from fasboot mode:
fastboot flash boot boot.img
Muminek111 said:
Download this boot.img for Marshmallow v.13.10.7.1
https://drive.google.com/file/d/0B7F3ZXr565GkV2N3WjBoeEZXUUU/view?usp=drivesdk
The command from fasboot mode:
fastboot flash boot boot.img
Click to expand...
Click to collapse
My phone version is 13.10.10.34 can I flash this boot image????
Sharashchandra said:
My phone version is 13.10.10.34 can I flash this boot image????
Click to expand...
Click to collapse
You need to boot.img from stock rom v 13.10.10.34.
Stock rom you can download from Asus website and then extract boot.img from this stock rom.
Sharashchandra said:
My phone version is 13.10.10.34 can I flash this boot image????
Click to expand...
Click to collapse
Plz help I used twrp v2.8.7.7seven max then
Its booted and showing in modified partition.ileave it as it is and I just backup the system but after backup when I press reboot system it will just freezed .then manually I switched on its showing "ERROR: Can't load invali boot image" two phones are under same condition plz help me its my friends phone.
Help me as fast as possible
---------- Post added at 01:13 PM ---------- Previous post was at 01:11 PM ----------
Muminek111 said:
You need to boot.img from stock rom v 13.10.10.34.
Stock rom you can download from Asus website and then extract boot.img from this stock rom.
Click to expand...
Click to collapse
Plz help I used twrp v2.8.7.7seven max then
Its booted and showing in modified partition.ileave it as it is and I just backup the system but after backup when I press reboot system it will just freezed .then manually I switched on its showing "ERROR: Can't load invali boot image" two phones are under same condition plz help me its my friends phone.
Help me as fast as possible
Sharashchandra said:
Plz help I used twrp v2.8.7.7seven max then
Its booted and showing in modified partition.ileave it as it is and I just backup the system but after backup when I press reboot system it will just freezed .then manually I switched on its showing "ERROR: Can't load invali boot image" two phones are under same condition plz help me its my friends phone.
Help me as fast as possible
---------- Post added at 01:13 PM ---------- Previous post was at 01:11 PM ----------
Plz help I used twrp v2.8.7.7seven max then
Its booted and showing in modified partition.ileave it as it is and I just backup the system but after backup when I press reboot system it will just freezed .then manually I switched on its showing "ERROR: Can't load invali boot image" two phones are under same condition plz help me its my friends phone.
Help me as fast as possible
Click to expand...
Click to collapse
I don't understand what your problem.
For Marshmallow use this TWRP.
https://drive.google.com/file/d/0B7F3ZXr565GkY28yUjhfRkd5MUk/view?usp=drivesdk
Another possibility how to fix your phone is flash stock rom from stock recovery. It's the easiest way.
Muminek111 said:
I don't understand what your problem.
For Marshmallow use this TWRP.
https://drive.google.com/file/d/0B7F3ZXr565GkY28yUjhfRkd5MUk/view?usp=drivesdk
Another possibility how to fix your phone is flash stock rom from stock recovery. It's the easiest way.
Click to expand...
Click to collapse
After flashing also the same problem persists
Thankyou
Sharashchandra said:
After flashing also the same problem persists
Thankyou
Click to expand...
Click to collapse
Do you tried to flash Asus stock rom v.13.10.10.34(1.4gb) from Asus stock recovery v.13.10.10 34. I don't mean flash from TWRP.
Hello M having ASUS ZenFone 2 laser ze550kl model with marshmallow version.. I tried to unlock boot loader but m unable to do so.. Please help me..
just flash this zip https://yadi.sk/d/0NFnYyTG36XzWv using TWRP recovery(in menu "install").
just flash this..
it works perfectly fine
make sure you use the latest TWRP for your device.
Hey bro you can watch this video and follow the steps then your phone will definitely right back.....
https://youtu.be/_Ca10N-XQJk
I have also this problem .
But i can't enter in the recovery menu , it doesn't work.
P.S. sorry for my english
Muminek111 said:
Do you tried to flash Asus stock rom v.13.10.10.34(1.4gb) from Asus stock recovery v.13.10.10 34. I don't mean flash from TWRP.
Click to expand...
Click to collapse
Well, i can feel some doubt in your post...but h*ll yeah! I'm currently facing the same problem; where flashing stock rom, downloaded from their site, using their stock recovery, adb, and adb sideload....
the rom flashes successfully, but still boots with the same error...To be frank, i'm fed up...and almost about giving up on this phone...
-i believe i'll give it another shot this very night, trying different methods...funny ones though; if and when they work, i will definitely update my post again... my phone version is Z00ED, in case anybody cares to know -
UPDATE:
=======
Aaaaaanyway, I downloaded 2 kinds of stock roms from the Asus official site;
1. UL-ASUS_Z00E-WW-13.1010.1612.53-user (the latest:- M) and...
2. UL-ASUS_Z00E-WW-12.8.5.222-user (and older version:- actually, the pre-installed version)
after flashing the first one over and over again; after and before wiping my phone and cache over and over again, NOTHING HAPPENED; no change!!! still kept throwing back the error message.
So I decided to flash the second one, and for a split second, I was happy cos the error had disappear...only for me to wait for eternity and in vain for the phone to boot (that is, even if it could). suddenly, I realized what had happen....the phone couldn't boot pass the ASUS logo, neither could it load recovery again (as it used to). It only boots into ADB, but of course, that will require USB DEBUG MODE to be ON to be able for the phone to be detected through ADB (which is far from possible due to the numerous wipes I performed).
CURRENT SITUATION: I can't ADB, I can't get into recovery, and I'm stacked with the logo at boot......when the phone is completely turned off and placed on charge, the battery shows an empty battery with the loading (status) sign (but it charges, even without the OS being able to display the process).
Don't know whether anyone is facing same, or I can start a new thread with this? and I need help before taking it to a 3rd party repairs (since we don't hv Asus customer care in our country yet).
Will be glad to find help.
PS: The computer still detects the phone as an ADB Android device, and to me, that's a beacon of hope.
abodan09 said:
Well, i can feel some doubt in your post...but h*ll yeah! I'm currently facing the same problem; where flashing stock rom, downloaded from their site, using their stock recovery, adb, and adb sideload....
the rom flashes successfully, but still boots with the same error...To be frank, i'm fed up...and almost about giving up on this phone...
-i believe i'll give it another shot this very night, trying different methods...funny ones though; if and when they work, i will definitely update my post again... my phone version is Z00ED, in case anybody cares to know -
Click to expand...
Click to collapse
This problem will resolve to open the bootloader.
Muminek111 said:
This problem will resolve to open the bootloader.
Click to expand...
Click to collapse
I don't think I got that...do u mind explaining further??? thank you!
abodan09 said:
I don't think I got that...do u mind explaining further??? thank you!
Click to expand...
Click to collapse
You can not flash the older version stock rom from stock recovery.
Flash latest stock rom.
Download this twrp: https://drive.google.com/file/d/0B7F3ZXr565GkY28yUjhfRkd5MUk/view?usp=drivesdk
Download this ulock bootloader: https://drive.google.com/file/d/0B7F3ZXr565GkMWNwUkZJa1BUVUU/view?usp=drivesdk
Download this supersu: https://drive.google.com/file/d/0B7F3ZXr565GkOTcxb2VPbmQzT2M/view?usp=drivesdk
Restart to fasboot mode.
Command: fastboot boot twrp.img
From twrp flash first zip ulock bootloder then flash zip supersu.
Reboot.
---------- Post added at 08:39 PM ---------- Previous post was at 08:15 PM ----------
Android 6
Must be first opened bootloader then can modified boot image.
Same ERROR,you just need to flash the unlock bootloader file
UnlockBL.zip
Click to expand...
Click to collapse
https://goo.gl/nVq9e7
i have installed new firmware on my zenfone laser 2 (ze500kl),but when restarts it says error cant load invalid boot image...then i fastbooted boot.img..but when i restarts the phone it again shows the errror...
pls help me..
christin7 said:
i have installed new firmware on my zenfone laser 2 (ze500kl),but when restarts it says error cant load invalid boot image...then i fastbooted boot.img..but when i restarts the phone it again shows the errror...
pls help me..
Click to expand...
Click to collapse
Test:
Try to flash boot.img of your firmware version from fastboot mode but use command: fastboot boot boot.img. Reboot system. Then let me know.
Originally posted by: Azpre
Hello
A while ago, I tried to root my Essential Phone using magisk. I unlocked the bootloader, flashed twrp, but when I tried to install the magisk zip file, it failed, and I was stuck in a bootloop.
Easy problem to solve right? I wiped everything from my phone (including the ROM), downloaded a stock ROM (.ZIP file, and I think that’s what ****ed everything up) and when I tried to install it, it failed once again. Therefore, I downloaded another stock ROM file (this time as a .img file) and tried to installed it.
But what I ended up doing, was installing some other .img file as the boot image (on twrp), and after that, my phone kept restarting endlessly. I couldn’t access the recovery mode (if I tried to press the vol down + start buttons, or just the start button, the process would repeat, so I leaved my phone there until it run out of battery, now its off).
I was despaired and tried to search every inch of the internet for a solution, and obviously, I could not find it.
Any help would be greatly appreciated
Thanks for your attention.
(Im not sure if this is really a soft brick, I named this thread wit my basic knowlage, sorry if Im wrong)
Use
fastboot unlock_critical
Then flash your full stock formware to both slots
You can get in the bootloader right?
Azpre said:
Originally posted by: Azpre
Hello
A while ago, I tried to root my Essential Phone using magisk. I unlocked the bootloader, flashed twrp, but when I tried to install the magisk zip file, it failed, and I was stuck in a bootloop.
Easy problem to solve right? I wiped everything from my phone (including the ROM), downloaded a stock ROM (.ZIP file, and I think that’s what ****ed everything up) and when I tried to install it, it failed once again. Therefore, I downloaded another stock ROM file (this time as a .img file) and tried to installed it.
But what I ended up doing, was installing some other .img file as the boot image (on twrp), and after that, my phone kept restarting endlessly. I couldn’t access the recovery mode (if I tried to press the vol down + start buttons, or just the start button, the process would repeat, so I leaved my phone there until it run out of battery, now its off).
I was despaired and tried to search every inch of the internet for a solution, and obviously, I could not find it.
Any help would be greatly appreciated
Thanks for your attention.
(Im not sure if this is really a soft brick, I named this thread wit my basic knowlage, sorry if Im wrong)
Click to expand...
Click to collapse
From my understanding ... After you get the bootloader unlocked and the critical partition as the poster above stated. Pretty sure, Magisk, when booted into the android OS should be installed.. After that you can patch the boot image(to include root) without root! And then, fastboot flash boot (path/to/boot.img).
For not being able to boot into TWRP .... Did you use the command fastboot boot twrp.img? Or fastboot flash recovery twrp.img ?
If you used the boot command - TWRP will not stick.
If you used the flash command and cannot access TWRP, IDK, you may be on the wrong partition. I personally had a bit of difficulty with there being two partitions. Just made it a bit confusing...
As the above poster asked, .... Are you able to get to the bootloader? If so, I don't think all is lost... I'm thinking you'll just have to do some fastboot commands again, like, fastboot boot TWRP.img . Then you should be able to just press the volume a time or two to boot to recovery. As @BakedTator asked
---------- Post added at 05:44 PM ---------- Previous post was at 05:42 PM ----------
BakedTator said:
Use
fastboot unlock_critical
Then flash your full stock formware to both slots
You can get in the bootloader right?
Click to expand...
Click to collapse
Was that advise sound enough???
---------- Post added at 05:49 PM ---------- Previous post was at 05:44 PM ----------
Azpre said:
Originally posted by: Azpre
Hello
A while ago, I tried to root my Essential Phone using magisk. I unlocked the bootloader, flashed twrp, but when I tried to install the magisk zip file, it failed, and I was stuck in a bootloop.
Easy problem to solve right? I wiped everything from my phone (including the ROM), downloaded a stock ROM (.ZIP file, and I think that’s what ****ed everything up) and when I tried to install it, it failed once again. Therefore, I downloaded another stock ROM file (this time as a .img file) and tried to installed it.
But what I ended up doing, was installing some other .img file as the boot image (on twrp), and after that, my phone kept restarting endlessly. I couldn’t access the recovery mode (if I tried to press the vol down + start buttons, or just the start button, the process would repeat, so I leaved my phone there until it run out of battery, now its off).
I was despaired and tried to search every inch of the internet for a solution, and obviously, I could not find it.
Any help would be greatly appreciated
Thanks for your attention.
(Im not sure if this is really a soft brick, I named this thread wit my basic knowlage, sorry if Im wrong)
Click to expand...
Click to collapse
https://forum.xda-developers.com/essential-phone/help/partition-t3733811. Check out this thread, it may help or give you some understanding.
BakedTator said:
Use
fastboot unlock_critical
Then flash your full stock formware to both slots
You can get in the bootloader right?
Click to expand...
Click to collapse
This is what I got when I tried to use this command
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot unlock_critical
fastboot: usage: unknown command unlock_critical
yesterday I couldn't find a way to access the bootloader, but for some reason when I gave another shot today it worked
going to try flash twrp once again
Azpre said:
This is what I got when I tried to use this command
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot unlock_critical
fastboot: usage: unknown command unlock_critical
yesterday I couldn't find a way to access the bootloader, but for some reason when I gave another shot today it worked
going to try flash twrp once again
Click to expand...
Click to collapse
fastboot flashing!!! fastboot flashing unlock_critical
From HERE - !!!
https://forum.xda-developers.com/essential-phone/development/stock-7-1-1-nmj20d-t3701681
dirtyreturn said:
From my understanding ... After you get the bootloader unlocked and the critical partition as the poster above stated. Pretty sure, Magisk, when booted into the android OS should be installed.. After that you can patch the boot image(to include root) without root! And then, fastboot flash boot (path/to/boot.img).
For not being able to boot into TWRP .... Did you use the command fastboot boot twrp.img? Or fastboot flash recovery twrp.img ?
If you used the boot command - TWRP will not stick.
If you used the flash command and cannot access TWRP, IDK, you may be on the wrong partition. I personally had a bit of difficulty with there being two partitions. Just made it a bit confusing...
As the above poster asked, .... Are you able to get to the bootloader? If so, I don't think all is lost... I'm thinking you'll just have to do some fastboot commands again, like, fastboot boot TWRP.img . Then you should be able to just press the volume a time or two to boot to recovery. As @BakedTator asked
---------- Post added at 05:44 PM ---------- Previous post was at 05:42 PM ----------
Was that advise sound enough???
---------- Post added at 05:49 PM ---------- Previous post was at 05:44 PM ----------
https://forum.xda-developers.com/essential-phone/help/partition-t3733811. Check out this thread, it may help or give you some understanding.
Click to expand...
Click to collapse
thanks for the thread man, helped alot
I managed to flash twrp by some miracle, I remember my device entering a bootloop once I tried to access the bootloader menu, but now its all good. I waited for the Essential run out of battery, then I plugged-in my pc the fastboot commands were working once again
going to try install a boot image now
dirtyreturn said:
fastboot flashing!!! fastboot flashing unlock_critical
From HERE - !!!
https://forum.xda-developers.com/essential-phone/development/stock-7-1-1-nmj20d-t3701681
Click to expand...
Click to collapse
oh my god Im such a dumbass, sorry
I had this problem tonight also. In my case I suspect it had to do with the install of magisk in which I checked both boxes and patched the bootloader. on reboot I was stuck on boot. Just wanted to add my solution. I got the pie back to stock zip here https://forum.xda-developers.com/essential-phone/development/stock-7-1-1-nmj20d-t3701681 then I put it into the adb folder and ran the flashall.bat script. I tried the no wipe one and it saved my information. very happy I didnt have to resetup my phone in the end.