The title says it all, but I explain calmly how it happened.
I was trying to want to install the official version of LineageOS for my Zenfone 2 and after downloading all the necessary files, have formatted and clean everything (except the SD), trying to install the new custom rom and then have the same "error 7". Then I realized immediately that lacked the Bootloader for Marshmellow, so I tried to look for a ZIP file for this, being able to find it right for my smartphone. The folder was known as "M_BL_upgrade_for_zf2_ze551ml_6.0" and once I had entered the USB cable to my PC and started the "Upgrade.bat" program, after the strangely reboot bootloader returned closed (it was understood from the screen, which instead to be white background with black writing was black with white lettering), then I tried to go back in recovery mode, realizing that every time I tried to get in, it was as if I were locked in a deadly circle and then kept restart and then return to where we started ... you have any idea how to do it, maybe re-add the Recovery Mode standard via CMD?
Related
I used the easy rooting process from and once i was rooted i used ROM manager to download Liquid Gingersense 1.0 and saw there was no access to radio. So i went to download a new radio and was told to rename PG05IMG.ZIP. I went to put on SD card and saw that from the rooting process there was already a file with that name. I figured it was just the radio files needed for the rooting, so i replaced with the new .ZIP file. I then loaded the bootloader (down, and power) and tried to load the new .ZIP but to no avail it did not work. I don't remember exactly what i did from then to know but to problem........I truly believe my phone is bricked and I cant find anything that describes my problem.............
I cant power down while plugged in. It automatically loads the bootloader giving the four options bootloader, reboot(which still works properly, and loads up the phone without any problems), reboot bootloader, and power down. If I choose bootloader it automatically tries to read if i have anything on the card. Then i have the option of fastboot, recovery, factory reset, simlock, hboot usb, and image crc. If I choose recovery or factory reset it instantly changes to the white HTC screen and reloads the bootloader. Also to make matters worse, I had read that if you do the system update through the phone that it would erase the rooting done to your phone, I downloaded the newest update and tried to install. Now every time I turn the phone on it, on it's own, shuts down my phone to update the software but instead of updating the software it just opens the bootloader.
As of now I'm rooted with s=on
If my battery is low enough it wont try to upgrade with the new software.
I reformatted my SD card and that didn't work either.
I used Titanium Backup to load clockworkmod. When tried to use that, it would still load in the bootloader with the 3 androids on the bottom.
and the top of the bootloader there is white text with pink background that says *** Security Warning ***
So to sum up, I cant recover or factory reset(through my phone settings, or hard boot), I cant access clockworkmod to recover anything, and bootloader doesn't work.
I've only had this phone for a few days, so please help me fix it.
Thanks,
Bryce Morgan
Hello all.
I'm new to modifying my android (Galaxy S7 G930A) and could use some help. I have successfully rooted my phone, but have had some issues trying to flash a custom recovery. I was trying to flash TWRP but for some reason it didn't work, and I would always boot into the stock recovery.
Today, I screwed something up while trying to figure out my host of issues (I was also trying to figure out why I kept getting a "dm-verity verification failed" notice when flashing). Using the TWRP Manager app, I tried to install the recovery that way and it kept giving me an error that it was either already installed or encountered an issue of some kind. Knowing it wasn't installed, I looked for a different route. Long story short, I downloaded Flashify and then manually downloaded and flashed the TWRP recovery img and a "no-verity-opt-encrypt" file - which I read would fix the dm-verity error I was receiving.
I believe that's all I did before this recovery boot issue starting occurring.
Now, when attempting to boot into recovery (no matter what way, through an app, manually, etc) the blue text "Recovery Booting..." appears for half a second and then disappears. If I'm holding down the buttons it will flash again and disappear again, over and over. If I don't hold down the buttons, when it disappears the phone boots up as normal. So now I can't seem to access recovery at all. I wanted to try going the hard/factory reset route, but obviously can't because I can't access recovery.
Also, I don't know if this is related or not, but now my laptop will not recognize my phone at all. Doesn't give me any options - it will charge, but no connection. I was hoping to load it into Odin and do a stock reset to start from scratch before flashing a custom ROM.
Edit: I tested and connected to a different computer just fine, so there's obviously some miscommunication going on between my phone and laptop.
Can anyone help me out here? Sorry for the long post, I'm just really frustrated. :crying:
Hello everyone, I have lots of issues with this tablet since I bought it. It works painfully slow, yet resetting it doesn't change anything, still the same problem. I also tried to root it via Kingroot and it werk, however it took me lot of time due to the system being unresponsive / unstable and almost useless. It comes with android 4.0.3 and I also tried looking up for any possibilites to reinstall the firmware since I'm extremely sure it could be caused from the firmware it also got installed from the factory. I also tried searching for custom roms and other ways around for TWRP or any custom recovery, but no result. I also tried up with the Flashify app to try extracting / backing up / dumping the recovery and the kernel but the app freezes up. I also tried a possibility to update the firmware from their official page, hence it failed to do so since it gives an error in their flashing software that dosen't tell me nor it logs it what it could be caused up from the connecting part.
primux.es/producto/tablets/tablet-primux-siroco-2-101/189
(not sure if anyone understands spanish thought but I can translate if needed)
This is the page from where I tried to download and install their software and their firmware down below on the page. primuxcomputers.es/primux/siroco2upgrade.pdf
There are the instructions where I tried to follow but at the "Imagen 9: Icono" part got me stuck in there. It requests me to insert the cable in the tablet holding the "Home" button and while holding it, plugging in the USB cable throught PC, and tap quickly the "Power" button 3 times. However it gives me a red X icon and yet nothing shows up in the devices: No ID, no other kind of detection no logs no nothing. After it showed up the X on the status, it disconnects itself and it changes to ready / green icon and plugs itself in again but nothing really happens to detect it again thought.
I also tried to boot in recovery mode but nothing happens menawhile Flashify keeps on the rebooting in recovery mode in loop doing nothing else... I'm seriously in pain with this tablet. And if you ask me to return it, not gonna even bother doing that..
I seriously hope any answer very soon and don't get dissapointed by the ignorance of this topic..
Hi there,
I am a newbie and hoping that someone could help to give me some clear pointers about options that i could take to rescue my phone - I hope its not bricked.
I was attempting to install LineageOS 16 on my Oppo R7s. This is my second attempt at installing a ROM - I did it a couple of weeks ago with Project Spectrum, and it worked, but Project Spectrum didn't impress me, so i wanted to try lineage OS instead).
I entered developer mode and enabled USB debugging
I downloaded the LineageOS zip to my SD card, as well as a Google Apps zip.
I downloaded the TWRP app on my phone just in case it was needed, however I've never used that app and not 100% sure how to use it.
I rebooted in recovery mode, and tried to install from the LineageOS zip file. It didn't start installing, I got some error message which I cannot recall... so I tried wiping the application data first, to see if that would help (maybe that was my mistake??)
I then went back to the install menu, and tried to install the Google Apps package first.... it started downloading, but then crashed and black screened.
Now, when I try to power on the phone, I get the oppo logo, and then it briefly goes back to the install screen for a second, with a message on the screen saying: "updating please wait, do not remove battery, do not co other operations" - but this only lasts for a second, then it crashes.
When I try to reboot into recovery mode (Power key +volume down), it does the same thing. I cannot get back to the white recovery menu.
Is there any way that I can rescue the situation and get back into recovery mode to try again? Or get back to a functioning USB connection so I can load a new ROM zip to try that instead?
When I plug it into the power, I get no indication that the phone is charging.
I'm worried the battery will go flat.
I have ADB installed on my computer, but I dont really know how to use it - the only command I know is "adb push" to load the roms onto the SD Card
Any advice on how to get access again would be greatly appreciated!
Hello everyone,
This is my first post on this forum, sorry in advance if the format is not correct.
Here's my problem: I was given a SM-J710FN that displayed an overheating problem on the screen while the phone was not heating at all, as well as buttons at the bottom of the phone were not working anymore.
I reset the device to factory default, erased the data from the recovery mode and flashed the 8.1 Oreo version with a ROM STOCK J710FXXU6CSK1
After all these manipulations, the buttons still did not work and the overheating message still appeared, preventing the phone from being charged even when it was switched off.
So I thought of programmed obsolescence, and thought it was worth trying to downgrade the phone to 7.0 from version 8.1.
Could you help me on this subject and tell me what you think?
Sorry for the up
try flash a custom rom, it does not need buttons, like this https://www.google.com/url?sa=t&source=web&rct=j&url=https://m.youtube.com/watch?v=veWLleEULe4&ved=2ahUKEwigx7TjmoTvAhVUIIgKHWbJCjIQ28sGMAJ6BAgFEBc&usg=AOvVaw3xJ6phS4kotjx4fk6Ypfuq
home button work or not
Thank you for the answer, I really appreciate it
Here is the update since I followed the Youtube link you sent me:
I have transferred the Custom ROM (Pixel-AB-11-20200909-ErfanGSI.img-0125.7z) as well as H-VENDOR_V1.0.zip to the mobile phone via a USB cable plugged to my PC in the root of the phone in order to proceed to its installation.
I then used Odin to flash Orange Fox (also TWRP on other attempts) with AP, but when I get to the Orange Fox recovery screen, the .zip files do not appear in the files. When searching on the Internet, it is advisable to flash via Fastboot, but despite several attempts, I cannot detect the phone with Fastboot, but only ADB. Even the manipulation saying to install the drivers manually from the device manager doesn't work because a message saying that the file to be used doesn't contain a driver is displayed. (android_winusb.inf)
And I also notice that after having flash TWRP or Orange Fox, the phone can no longer boot on the system.
Have you got any advices?
I continued my tests on my side, I was able to better understand how TWRP and Orange Fox work, in fact to make it usable, you first have to FORMAT the /data (not swipe), so, make TWRP / Orange Fox operational.
I was then blocked during the installation of the personalized ROM with the error of the /vendor, following my research, it would be necessary to install a .zip dedicated to that (Mokee from what I saw)
But I did something I shouldn't have done, and I flashed the zip "twrp-3.2.1-0-20180414-codeworkx-dumpling" from the Orange Fox recovery, and since then, the phone is stuck at startup, and when I try to access Download Mode, I get stuck at the Warning Message because my volume buttons don't react.
Is it possible to do something about it or the phone will be forever bricked?
up