I begging by thanking everyone in this site for their great effort and support (this is the best site for these topic).
I have a problem with newly install lineageOS, I will explain the procedure I made so far:
-I have a sumsang note 3 neo with the code name: SM-N7505ZWADBT.
-I rooted my phone using: CF-Root-SM-N7505-5.1.1.zip and Odin3 v3.10.7 (after I tried other roots but they didn’t work).
-I then installed then: twrp-2.8.7.0-hlltexx-4.4.img.tar from their official website.
-When go to recovery mode the message: Recovery is not Seandroid Enforcing. I can still access the recovery mode and this warning only shows when I access recovery mode. Also if I do nothing and want to poweroff, they ask me that this machine seam not to have root installed, so I skipped it.
-I wiped the stock ROM without back up (huge mistake).
-I flashed then lineage-14.1-20170526-UNOFFICIAL-hllte.zip (without GAPPS, I don’t want them), which was successful beside two lines which appear in red saying: E: unknown command [log]
-I then turned on phone, ( Recovery is not Seandroid Enforcing doesn’t appear, it only appear in recovery mode).
-The lineageOS took to long for first boot, so I took off the battery and went back to recovery mode.
-After wiping and flashing multiple times, it worked and I could get the lineageOS running.
-When I enter they ask to parametrize the phone.
-Everything seam to work alright, except wifi, phone calls and camera: wifi adress show up but when I try to conenct they try logging but can’t, sms messages work fine but when I call I can’t hear anything and so the other person, speakers are working, camera does not work.
So there I gave a details approach of what I did to get to this situation, I tried to download stock firm with the same code but I couldn’t find the exact number (SM-N7505ZWADBT).
I would realy like to make lineageOS work, so if you can help me I would really appreciate it, also if it is impossible, then how to get my previous stock ROM.
Related
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:
Hi all,
well, to be honnest I already posted my story in the help thread but no answer came so I try with a new thread
We'll see if I'm luckier this way !
a few weeks ago I broke my screen and decided to change it myself.
Everything went fine (even restarted successfully my phone before applying the tape to fix the screen) until I finally tried to restart my phone after the repair is done.
Since then I'm not able to turn on my phone
Holding the power button starts fastboot mode, UP + power doesn't do anything and DOWN + power enters recovery. Weird !
Another weird thing: it only works if I'm not plugged. When I'm plugged nothing ever happens.
I suspected I could have damaged buttons or cables. I have looked carefully but nothing appears to be broken.
Here is what I already did without any result:
- I had access to the original recovery so wiped the cache
- I tried to recover the phone but that did not work so
- I installed twrk using adb (like here)
- and then installed the rom as explained here (I used the last release here, so it should be cm-13.0-20160819-SNAPSHOT-ZNH5YAO0IN-bacon.zip). It seemed to work but finally no, same situtation
- I tried this but so far not able to get the qualcomm port listed once the phone is on. It may be related to the fact that I have to unplug to boot it but I always got a Android bootloader interface listed.
Any idea someone ?
Thank you very much for your help !
Did you try to "fastboot reboot" while in fastboot mode?
Try flashing a CM14 rom. Mine came with CM12 so I tried flashing back to CM11 and I did flash it successfully through Fastboot but alas it won't boot. The boot logo loads but then I'm introduced to a black screen.. So I flashed back to a (at that time the latest stable) CM12.1 but same result. And I got worried. Then I decided to flash a CM13 rom which was a beta build (at that time newly released Android 6) and it booted into it alright! So I suggest flashing a CM14 and let me know how it does.
The problem seems be much deeper than just a broken screen. It may sometime affect the chipset of the cellphone.
For that we can't do anything.
For now you can try the following things :
1 . Flash the latest Cyanogen Firmware from the same place you have downloaded the snapshot cm13.
2. Flash recovery (TWRP) using adb.
3. Wipe
-System
-Data
-Cache and Dalvik Cache
4. Flash the latest Cyanogen Rom .
5. Boot into recovery.
6. Flash some gapps as per the Android version.( Open Gapps I recommend)
7. Boot back to recovery .
8. Boot into System.
This is the max you can do for now.
You can also check device forums for recovering from a bricked device post.
Go through the post and check if any symptoms matches yours. You'll find the answer right away.
And the last option you can do is going to service center, they will charge you mostly (even if in warranty as you have yourself tampered hardware of the phone.)
Hope it will help. Thanks
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!
I got my Nokia 3.1 in a bit of a weird situation trying to flash the stock ROM. I feel like it's a lost cause, but since I can still boot in recovery mode, there may still be a solution, I will explain in case someone can help.
It started when I tried to update from Android 8.0 to 10.0 (none of the previous OTA updates had worked and would always reboot in Oreo 8.0). This time, it didn't work and got the phone stuck in a boot loop.
The phone is still under warranty, but because I bought it overseas and there's no Nokia care centre here is New Zealand, I had no option but trying to repair it myself.
A wipe/factory reset didn't help, but after changing the active slot from B to A (using fastboot), it booted again in Oreo 8.0. Only problem is that I could no longer start a fresh Oreo 8.0 install without updating first and since all updates failed, I was stuck.
I suspect slot B is damaged or corrupt, hence the impossibility to update. To check it, I switched back the active slot to B after a factory reset, and that was not a great idea, the phone wouldn't even boot and looked hard-bricked.
But I still managed to use SP tool to download firmware, so I did that with the original Nokia 3.1 stock ROM (ES2).
However, I could not flash all files, I'm not too sure why.
I had the error message:
ERROR: STATUS_SEC_INSUFFICIENT_BUFFER
Verified boot is enabled
Please download signed image (sutinfo-verified.img) or disable verified boot
I didn't know how to do either of these, so I skipped the three problematic files: sutinfo.img, systeminfo_a.img, and cda_a.img (not sure what they do?).
It worked and un-bricked the phone, but it now boots to recovery mode only. What puzzles me is that I also no longer have access to fastboot, even when I reboot to bootloader (as if it skipped bootloader and went straight to recovery). I suspect it is because it still boots on slot B but I don't know how I can check that or change it back to slot A without fastboot access.
I tried using adb: adb shell getprop ro.boot_suffix but although it can see the device, it failed because it says device is unauthorized. I've tried all the fixes for this I found, to no avail.
So that's where I am, able to boot to recovery (but with adb unauthorized), able to flash firmware (except those files that must be signed), and unable to access fastboot.
I'm giving up hope that it's repairable, but I'd love to at least understand what happened, if someone has any idea...
Sorry for the long story...
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