Hi Everbody,
does a sideload in the recovery exist, in my one doesn't.
Why i do ask, i messed up my first Installation and made a factory reset for to install everything from Scratch. But during the new Installation i couldn't get the fingerprint running.
Doesn't matter in which way i tried to reset i couldn't get the fingerprint running (maybe someone know a solution).
The only chance,i think are left, ist to downgrade the firmware (10.5.2 IN21BA), but no sideload nochance.
Is there any ?, what do i wrong?
Cheers!
Related
Ok so today CyanogenMod released the m10 snapshot version for the A700 and before installing it, i decided to factory reset my tablet from CWM and then install the new version.
My tablet did run the cyanogenmod intro start up like all new devices but I found out that my music, videos, pictures, etc were still there even though I formatted from recovery. SO, I decided to factory reset from the settings, tablet reboots, won't start up! I've come to the conclusion that I might have reset my tablet to stock firmware even though there isn't any installed. I can open recovery but can't do anything other than scroll through the menus. Whenever I confirm an action the tablet bootloops. I think I can solve this by re-flashing the new rom but whenever I go to install zip the tablet reboots into a bootloop. Is there anyway to install the rom without recovery? Like using command prompt? And if that's not the case then could you help me solve this issue?
Many thanks to anyone who can help me out
SOLVED: After spending 7 non-stop hours on command prompt typing in fastboot and adb commands, managed to somehow luckily figure it out. I can't really explain how I did it but I did it
AusomBabs said:
Ok so today CyanogenMod released the m10 snapshot version for the A700 and before installing it, i decided to factory reset my tablet from CWM and then install the new version.
My tablet did run the cyanogenmod intro start up like all new devices but I found out that my music, videos, pictures, etc were still there even though I formatted from recovery. SO, I decided to factory reset from the settings, tablet reboots, won't start up! I've come to the conclusion that I might have reset my tablet to stock firmware even though there isn't any installed. I can open recovery but can't do anything other than scroll through the menus. Whenever I confirm an action the tablet bootloops. I think I can solve this by re-flashing the new rom but whenever I go to install zip the tablet reboots into a bootloop. Is there anyway to install the rom without recovery? Like using command prompt? And if that's not the case then could you help me solve this issue?
Many thanks to anyone who can help me out
SOLVED: After spending 7 non-stop hours on command prompt typing in fastboot and adb commands, managed to somehow luckily figure it out. I can't really explain how I did it but I did it
Click to expand...
Click to collapse
Good Job if You Could Explain For Latest Problem Solved. I Think this is the problem from cwm or maybe the latest rom of cwm snapshot, need to investigate for problem occured. before this update we never have this problem. "When Reset Factory Default within Setting than it will always bootlop". My a701 have this problem too. looks like @Flupkes Problem too, the different is i Reset it From Snapshot M7 this my old thread and could make the adb working because the usb slot problem.
Hello, I need serious help with my phone.
So, after a long while of having my phone rooted, and had a case of boot loop with twrp, I decided to go back to stock os and hung up the root days. I thought i did it right by getting a stock os and flashed it, and it worked for couple months, until yesterday.
My phone keeps going into Cyanogen Recovery, I tried rebooting so many times, once it did boot up to OS, but it went back after i restarted phone or it died.
Now I can't no longer get back, I thought factory resetting will work but it didn't. (Tried both wipe cache partition and Full factory reset option from the recovery) I found unroot your phone toolkits, thinking it could help fix my problem and just unroot/ give me back to OS (I wished i found this before flashing that custom stock rom).
But the toolkit doesn't work for me, it finds adb devices, but it cant find fast boot devices, because my phone cant even go into fast boot.
I tried manual, and the option from the recovery, it keeps going back to recovery. I have an option for apply update, and then apply from ADB, that was the only way for my pc to recognize my phone from adb devices. Any clues on how to fix?
Hi !
I may suggest you this thread https://forum.xda-developers.com/oneplus-one/general/tool-oneplus-one-return-to-stock-t2970390
Good luck !
xanthrax said:
Hi !
I may suggest you this thread https://forum.xda-developers.com/oneplus-one/general/tool-oneplus-one-return-to-stock-t2970390
Good luck !
Click to expand...
Click to collapse
Will try, Ill respond back if anything happens!
Hmm I'm still having trouble because, I can't get into fast boot for some reason. It's keep going back to Cyanogen recovery. It has the option to reload into bootloader, but goes into cyanogen recovery again.
There is an option in dev options, uncheck the "update cyanogen recovery" and flash twrp again
Sent from my SHIELD Tablet using Tapatalk
Hi everyone,
I hope I am in the right forum to post my query. I am trying to find a solution to the existing Problem. Before I get to describe the problem specifically I must make it clear that this is my first time on any android forum. While trying to find a solution for the existing problem, I had to google words like Bootloop, Softbrick, TWRP, Custom Recovery, Root, Flash, ROM etc. They still do not make much sense to me (I will be reading more about them in the coming days). So now you can imagine how big of a Noob I am.
Well, I own a Moto G 1st Gen XT1033. Since yesterday it is in a Bootloop. The phone boots completely at times but automatically restarts itself after a while. Sometimes I have 1-2 minutes at maximum to use the phone. Until now I have been able to delete quite a bit of data for example pictures and certain apps because I thought that Bootloop was happening because of no space on the memory. The last app that I installed 3 days back from Google Play after which this problem started occurring, I was also able to uninstall it. Until now I have tried wiping out Cache by going in the recovery mode but that didnt fix the Reboot problem. I also tried holding the Volume Up + Volume Down + Power button for 2 minutes (I read it on internet somewhere as a fix to the problem) but that didnt help either. I have never created a backup and I don't want to do a Factory Reset as a fix to the problem because I don't want to lose the data. I also tried to follow your solution for backing up data but I got lost. I don't know where to start from. Thats why I am writing here.
I don't know if my phone is rooted. I did turn on Developer Mode on my phone in the past (if this info helps).
I do not know which Android version I have but I am guessing that it is Lollipop.
I never installed TWRP or any Custom Recovery software on my phone before.
The battery is working ok.
What I am looking for is:
1) Step by step guide to create a backup
2) Resolving Bootloop issue if possible
Thanks
without custom recovery no data backup is possible.
u need to unlock your bootloader and install The Twrp recovery to perform the backup.
but only fix for you is factory reset.
jbanti said:
without custom recovery no data backup is possible.
u need to unlock your bootloader and install The Twrp recovery to perform the backup.
but only fix for you is factory reset.
Click to expand...
Click to collapse
Thank you @jbanti Apologize for my late response. As far as I know unlocking the bootloader will erase the memory. One can recover data by ADB Pull by using these Threads:
https://forum.xda-developers.com/moto-g/help/moto-g-1st-gen-xt1033-boot-loop-stock-t3357472 (Post #4)
https://forum.xda-developers.com/showthread.php?t=2426426
So I know that there it is possible using`adb pull` command to take backup of whole device but I don't know how. I get lost in the 2nd thread. Any lead would be appreciated
Thanks
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...
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