Hi everyone last night i decided to root my ohone. I have had it for a while but for some reason hadn't got round to doing it.
I followed all the instructions firstly unlocking bootloader, TWRP then installing no verity and magisk etc and every looked to be good phone starts up with the the your device has been unlocked message and something about bad id key but then would start like normal and set about installing all my apps etc again for the phone to be back to how it was just rooted.
However tonight i restarted my phone and when it's went to start up it throws me into the fast loader screen wtih your device didnt stat up successfully use the software repair assistant on computer to repair your device.
I had only been installing my usual apps/ new luancher etc... however the only thing i think that could have caused an issue was i checked for an android version update and it found i already had the most up to date one so nothing was downloaded but possibly just checking has caused an issue ?
Any help with this would be appreciated.
I can still boot into team win recovery mode but was hoping as i've now installed everything a new... i could resolve this without another fresh install if possible ?
Thanks
fendertele said:
Hi everyone last night i decided to root my ohone. I have had it for a while but for some reason hadn't got round to doing it.
I followed all the instructions firstly unlocking bootloader, TWRP then installing no verity and magisk etc and every looked to be good phone starts up with the the your device has been unlocked message and something about bad id key but then would start like normal and set about installing all my apps etc again for the phone to be back to how it was just rooted.
However tonight i restarted my phone and when it's went to start up it throws me into the fast loader screen wtih your device didnt stat up successfully use the software repair assistant on computer to repair your device.
I had only been installing my usual apps/ new luancher etc... however the only thing i think that could have caused an issue was i checked for an android version update and it found i already had the most up to date one so nothing was downloaded but possibly just checking has caused an issue ?
Any help with this would be appreciated.
I can still boot into team win recovery mode but was hoping as i've now installed everything a new... i could resolve this without another fresh install if possible ?
Thanks
Click to expand...
Click to collapse
You could try reflashing the boot.img
What does getvar all say?
Code:
fastboot getvar all
Related
I want to start out stating that i am very familiar with android's but have never experienced anything like this.
The first thing I tried was to oem unlock it from fastboot, which it claimed to do however i am skeptical as nothing else seems to stick, attempted to install cwm and TWRP neither with any success, even though it says the action was performed successfully.
The strangest thing is that i deleted all the apps on the device from settings/app, but when i rebooted my device they all came back!
All i wanted to do was do a factory reset, which also claims to finish successfully but after rebooting from recovery mode, i am back where i started.
App Updates also do not work as every time the tablet reboots, the apps have to be re-updated.
Its like the tablet is stuck in a read only state and when it reboots all changes are lost.
Like i said, this thing is acting weird and i have no idea where to go from here. Any help would be greatly appreciated!
[Update: Tried RSDLite, same results, Result is PASS however after system reboot everything is the same.]
Another update, tried downloading HWI69 which is the stock rom, tried to fastboot each image but nothing sticks even though it seems to say it writes it to the system. I'm starting to think the NAND memory is locked up and cannot be written to anymore if that's even a possibility.
BUMP
I went to bed last night, did what I normally do, set my alarm and turned on sleep tracking. I woke up this morning to find that my phone had booted back into TWRP. I rebooted and found that after the LG screen it goes directly into TWRP which had replaced factory reset using bump. I tried to restore the phone using a saved backup and that didn't work. I tried to wipe it then restore and that didn't work. I am afraid that my phone is a lost cause and that I cannot get a replacement due to it booting to the TWRP screen every time it is turned on. The phone had been working fine for the past week since I had installed TWRP. Does anyone have any suggestions on what to do or what might have caused this?
Look in the lg g3 international forum there is a fix there your phone tried to flash a ota update
jerrycoffman45 said:
Look in the lg g3 international forum there is a fix there your phone tried to flash a ota update
Click to expand...
Click to collapse
Sounds awesome thanks.
All the times that I tried to it to flash a ROM itself it doesn't do it but it does it by itself.
Here is a link http://forum.xda-developers.com/showthread.php?t=2908290 after you fix it freeze software update with titanium backup
I cannot get the first step to work. ADB cannot see the device. I tried installing the Google USB Driver but that didn't work and TWRP ADB sideload doesn't work either.
EDIT: I put the zip on my phone using MTP and flashed it using TWRP but it still stuck booting into TWRP.
EDIT 2: Tried one more time again after flashing my backup ROM. Now it loads.
I can't help more on a road trip sorry
Try this, worked for me
Go to this website and do what ot says. http://forum.xda-developers.com/newreply.php?do=newreply&noquote=1&p=57453756 this should fix it. I had the same issue and this worked :good: sorry if im late.
Hello Guys,
I'm back again (I posted about this issue about 6-9 months ago, a couple users tried their best to help me with it, since than I haven't had any time to fix this issue).
History:
1. Brand new FRD-L14, bought the phone, used it for 1/2 day, fell, cracked screen, replaced it.
2. The phone worked there after, but the OS read "NRM-Test Keys", anyways since I had TWRP installed at that time, tried several different roll backs and such to install a full OS, never worked
3. I did encounter a problem where the fastboot screen would read "PHone Unlocked", but "FRP Locked", at which time I was unable to install anything the error when going through Adb/Fastboot would be "Error: Command No Allowed", a experienced user here did fix it remotely for me, no idea how, but anyways it worked, so back to #2
4. Now the phone has FRP Locked again. So I can get into fastboot, and stock recovery (which doesn't work, states device is unsupported), cannot instal TWRP as FRP is locked
What I need help with is to get rid of this dam FRP Locked issue. I don't understand why it keeps coming back despite me not logging in/putting in credentials when I install the OS.
As I am in the US, Huawei has no authorized repair centers. What a waste!
Any help or suggestions are welcome. Thanks.
coolest35 said:
Hello Guys,
I'm back again (I posted about this issue about 6-9 months ago, a couple users tried their best to help me with it, since than I haven't had any time to fix this issue).
History:
1. Brand new FRD-L14, bought the phone, used it for 1/2 day, fell, cracked screen, replaced it.
2. The phone worked there after, but the OS read "NRM-Test Keys", anyways since I had TWRP installed at that time, tried several different roll backs and such to install a full OS, never worked
3. I did encounter a problem where the fastboot screen would read "PHone Unlocked", but "FRP Locked", at which time I was unable to install anything the error when going through Adb/Fastboot would be "Error: Command No Allowed", a experienced user here did fix it remotely for me, no idea how, but anyways it worked, so back to #2
4. Now the phone has FRP Locked again. So I can get into fastboot, and stock recovery (which doesn't work, states device is unsupported), cannot instal TWRP as FRP is locked
What I need help with is to get rid of this dam FRP Locked issue. I don't understand why it keeps coming back despite me not logging in/putting in credentials when I install the OS.
As I am in the US, Huawei has no authorized repair centers. What a waste!
Any help or suggestions are welcome. Thanks.
Click to expand...
Click to collapse
Can you get to download mode for the sd card firmware update?
Okay. I was messing around with my firmware which I've done in the past. I've had a few problems then due to my phone model being obscure (Samsung Galaxy S6: SM-S906L). I've always had a copy of the firmware saved to my computer in the event of a bootloop or a similar issue, I figured I could just flash it with Odin to fix it. I have also done this in the past. After accidently wiping my phone, I went to re-install Magisk, but noticed my phone trying to push an update. I let it go through without much though and after it finished saw it didn't change much. I carried on with re-installing Magisk when I figured I might as well fix some problems I had with booting the phone (I would have to boot it into download mode then recovery to get it out of a bootloop each time I turned it off). I carried on with flashing my saved firmware to fix the problem. Everything flashed fine except the bootloader. It's come to my understanding now that because I let the update carry through with my phone, my saved firmware is no longer compatiable dispite the fact that it didn't change my android version. So now I have a bootloader installed that is meant for a higher update without my known ability to downgrade. Due to the obscurity of my phone model, I can't find anything to bring my firmware up to what my bootloader is at. So now my phone is stuck in a bootloop with the ability to access download mode, but recovery mode simply gives me a "recovery is not seandroid enforcing" error. I would greatly appreciate it if someone has any advise they could give me.
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...