Related
Hey guys, I have a Star A2000 with Froyo rooted. While I was trying to modify my original status bar, the phone blocked and I had to reboot it. I rebooted it but for over one hour it's loading whithout booting into the homescreen. I tryed with the factory reset but nothing. I can't load any rom from Linux, and so I can't fully on the device. Any suggestion? I want to bring back everything! Anybody knows how I can do so? Without the flashing cable is it possible to restore or put back the original system and settings?
recovery menu
Turn off the phone
press vol up and power button in the same time
that will bring you to the recovery menu - press home key to see options
navigate trough options with vol up and down and meniu
take care - reset to factory my wipe your imei off. if you are lucky this might not happen
also read here:http://forum.xda-developers.com/wiki/index.php?title=Chinese_Clones_MTK6516
I've tried this way all the time but it seems to don't work
Is there not an update.zip in other to install the original rom? Because I'm not with the flashing cable so I can't use it to flash. Is there any other way I can do it?
If you cant access the recovery by using power button + volume up key at the same time when turning on the phone then the recovery partition is not working (should show up with android ! screen or custom recovery) - If you cant boot in to the recovery menu or the system partition containing the OS you have likely bricked your phone, the only chance you may have in my opinion is a factory reset - which you say has failed or connect usb while phone is booting and hope you can get an ADB connection (which is possible due to a bug but only seems to work intermittantly - I have managed to fix a brick via this stroke of luck before)
Having a backup as well as a working recovery or system partition is the key to playing with your phone - one partition should always be working to restore the other when or if it fails.
[email protected] said:
If you cant access the recovery by using power button + volume up key at the same time when turning on the phone then the recovery partition is not working (should show up with android ! screen or custom recovery) - If you cant boot in to the recovery menu or the system partition containing the OS you have likely bricked your phone, the only chance you may have in my opinion is a factory reset - which you say has failed or connect usb while phone is booting and hope you can get an ADB connection (which is possible due to a bug but only seems to work intermittantly - I have managed to fix a brick via this stroke of luck before)
Having a backup as well as a working recovery or system partition is the key to playing with your phone - one partition should always be working to restore the other when or if it fails.
Click to expand...
Click to collapse
HI !
I´m on the same situation.
After install de CW recovery, made 3 nandroid backups of different states of my phone and tryed to flash 3 different ROM MODs (including the ICS 4, hahaha) i bricked my A2000-GPS.
I´m able to enter CW recovery menu using PWR+VOL.UP and navigate as well. I wiped all data, cache partition and try to restore all my backups one by one... Nothing brings back my OS... I still stucked into boot screen (the first one, i´m not entering in the boot_logo image...
After many tryes, i wiped all data again and made a factory reset using CW recory: Nothing...
I notice that i´m loose the factory recovery mode (PWR + VOL.Down)... And i also never made an IMEI backup. Could be that?
I apreciate any help. Any light in the end of tunel, hahaha
Kind regards!
------------------------------
Updating:
- I´m using the ClockworkMod Recovery V4.0.0.5.
- My CWM recovery is able to read my SD card, so i can put any .img or .zip file inside it.
I format the folders:
/boot
/cache
/data
/system
Into "Mounts ans Storage" menu.
After I recovery one of my nandroid backups. Normal rebooting and.........................
NOTHING ! I´m still stucked into first boot img.
It´s normal this screen delays like 15 ~ 20min. to disapear?
Hi.
related with CWM I also have a weird issue.
My wife's old A2000 is now in my hands to play with it. The phone was virgin (stock rom no rooted).
I rooted the phone and installed cwm/rom manager.
The weird issue is:
1) If I click in Rom Manager option " Reboot into CWM" the phone reboot in CWM with all options working including rom backup.
2) starting with th phone off I press the keys power + vol.up Iget not the CWM but the "fatory Mode" green menu with 6 options (Full test, Test Report, Clear flash, version and Reboot).
3) pressing power + vol.down it simply boot normay the system.
What can be wrong with this "ex-virgin" A2000?
Hello,
I am not sure what happened, but here is the story.
First, I tried to root the phone using the 1-click method, only to later realize that it does not work as the phone I had was running the latest OTA update. I wanted to reset my phone to factory default and I proceeded to do that.
Now, when my phone starts I see the small recovery menu and a lot of red letters stating that the system could not mount, find or open recovery directories, files or logs. (On the screen is this info Enter ok key,Select vol up/down Rebot system now, apply update from scard,wipe data/factory reset,wipe cache partition But nothing will move courser,then blow that in red is E:failed to open/res/recovery.fstab(no such file or directory) E:unknown volume for path[/cache/recovery/command with a lot more then in yellow letters #manual mode# and the same messages)
When I enter the download mode, and tried to use Odin or ADB, neither one can detect my device. I tried installing different samsung drivers on my system to no solution to being able to detect the device. Is this due to Windows not being able to initiate the drivers correctly, because when I connect the phone in Download mode, Windows has a pop-up show up that says "Drivers not recognized, your device might not work properly".
Does this mean the phone is bricked or is there something I can do to restore the phone?
Informatic_dev said:
Hello,
I am not sure what happened, but here is the story.
First, I tried to root the phone using the 1-click method, only to later realize that it does not work as the phone I had was running the latest OTA update. I wanted to reset my phone to factory default and I proceeded to do that.
Now, when my phone starts I see the small recovery menu and a lot of red letters stating that the system could not mount, find or open recovery directories, files or logs. (On the screen is this info Enter ok key,Select vol up/down Rebot system now, apply update from scard,wipe data/factory reset,wipe cache partition But nothing will move courser,then blow that in red is E:failed to open/res/recovery.fstab(no such file or directory) E:unknown volume for path[/cache/recovery/command with a lot more then in yellow letters #manual mode# and the same messages)
When I enter the download mode, and tried to use Odin or ADB, neither one can detect my device. I tried installing different samsung drivers on my system to no solution to being able to detect the device. Is this due to Windows not being able to initiate the drivers correctly, because when I connect the phone in Download mode, Windows has a pop-up show up that says "Drivers not recognized, your device might not work properly".
Does this mean the phone is bricked or is there something I can do to restore the phone?
Click to expand...
Click to collapse
did you try a different usb port? also I'd try heimdall and see if that works and sees your phone. which stock odin package are yup trying to flash?
I did manage to recover to the stock EH03 rom, by doing the first couple of steps in section 4 of the Guide for installing Rom (http://forum.xda-developers.com/showthread.php?t=1238070).
At this point, I cannot get root on my phone. I tried using 1 click root methods and those fail to install SU. I tried using the manual method of pushing rage.bin file using ADB, but that also failed.
I tried flashing some of the ROMs from section 4 of the above guide, but they cant seem to install on my phone. When I try to install through recovery, I get the picture of the android on the side and a failed install and either get stuck with the Samsung logo or a recovery boot loop.
Am I missing a step or something in order to root the phone or load a custom ROM? Is it possible that my phone cannot be rooted due to a lock somewhere?
Thanks.
Informatic_dev said:
I did manage to recover to the stock EH03 rom, by doing the first couple of steps in section 4 of the Guide for installing Rom (http://forum.xda-developers.com/showthread.php?t=1238070).
At this point, I cannot get root on my phone. I tried using 1 click root methods and those fail to install SU. I tried using the manual method of pushing rage.bin file using ADB, but that also failed.
I tried flashing some of the ROMs from section 4 of the above guide, but they cant seem to install on my phone. When I try to install through recovery, I get the picture of the android on the side and a failed install and either get stuck with the Samsung logo or a recovery boot loop.
Am I missing a step or something in order to root the phone or load a custom ROM? Is it possible that my phone cannot be rooted due to a lock somewhere?
Thanks.
Click to expand...
Click to collapse
You should have read a little but noe I'm going to tell you what to do head over to droid styles guide here http://forum.xda-developers.com/showthread.php?t=1238070 now download cwmfixedforcm7.zip and atlas 2.2.zip and put it on your computer now download this. http://downloads.noshufou.netdna-cdn.com/superuser/Superuser-3.1.3-arm-signed.zip put it on the root of your SD card now power on your computer run Odin as AMINISTRATOR put the atlas.zip in the pit space in Odin check mark beside the place that said PDA and put the cwm.zip there now put your phone in download mode hook it to the computer and when Odin recognizes it press start wait for it to say PASS it may take up to 20min when its done reboot the while while holding the volume buttons, Home key button, power button when you see the Samsung logo flash twice let go of the volume up button and the home key button continue holding volume down button and the power button you should now boot into a menu with blue text now release the buttons navigate with the VOLUME BUTTONS AND THE POWER BUTTON TO SELECT go to install zip from SD now choose zip from SD navigate to the .zip I told you to put on your SD card select it then you will see a bunch of no's and a yes select yes AFTER its finished press go back then press reboot system now ONCE IT REBOOTS CONGRATS YOUR ROOTED AND SHOULD HAVE SUPERUSER!!!
Sent from my SCH-I500 using Tapatalk 2
I managed to get it working, maybe the SU.tar was corrupted as it worked this time. Thanks.
I am trying to root my T-mo Galaxy S5 using the Philz touch recovery CWM. I got thru and put the phone in download mode, use odin v1.85 and load the tar.md5 file into the PDA section, i have tried 6.26.2 version of philz and also the 6.26.6 version, same issue with either one. It goes through and seems to work successfully, it says PASS in Odin at the end and my phone reboots normally. I then shut off my phone and hold the vol up + Home + Pwr keys to boot into Recovery mode.
When i do, i get one blue line saying "recovery booting..."
Then a quick screen showing an android bot with its belly open and little spinning wireframe orb in its belly with the words "installing system update..."
then as the attached screenshot shows, is what i see next...
in red at top it says:
Android system recovery <3e>
KOT49H.G900TUVU1ANCH
Volume up/down to move highlight;
power button to select.
My choices to scroll thru on screen are....
reboot system now
apply update from ADB
apply update from external storage
wipe data/factory reset
wipe cache partition
apply update from cache
In the background is an image of a droid bot laying down with a red yield sign over his open belly and the words "No Command"
at the bottom of hte screen in yellow it says...
# MANUAL MODE #
-- Appling Multi-CSC...
Applied the CSC-code : TMB
Successfully applied multi-CSC.
Any ideas what this is and how i can get to the regular Philz touch CWM recovery so i can install custom ROMS?
Things maybe slightly different about my S5, i have a wireless charging accept pad installed on top of my battery and touching the two wireless charging nodes on the back of the phone so i can wirelessly charge.
I also have a gear fit paired with my phone, which i cant imagine is causing any issues.
thanks,
Devo
Image lives at: dropbox.com/s/bfzetvhnb00mx69/2014-05-02%2015.58.11.jpg
andyshannon3 said:
I am trying to root my T-mo Galaxy S5 using the Philz touch recovery CWM. I got thru and put the phone in download mode, use odin v1.85 and load the tar.md5 file into the PDA section, i have tried 6.26.2 version of philz and also the 6.26.6 version, same issue with either one. It goes through and seems to work successfully, it says PASS in Odin at the end and my phone reboots normally. I then shut off my phone and hold the vol up + Home + Pwr keys to boot into Recovery mode.
When i do, i get one blue line saying "recovery booting..."
Then a quick screen showing an android bot with its belly open and little spinning wireframe orb in its belly with the words "installing system update..."
then as the attached screenshot shows, is what i see next...
in red at top it says:
Android system recovery <3e>
KOT49H.G900TUVU1ANCH
Volume up/down to move highlight;
power button to select.
My choices to scroll thru on screen are....
reboot system now
apply update from ADB
apply update from external storage
wipe data/factory reset
wipe cache partition
apply update from cache
In the background is an image of a droid bot laying down with a red yield sign over his open belly and the words "No Command"
at the bottom of hte screen in yellow it says...
# MANUAL MODE #
-- Appling Multi-CSC...
Applied the CSC-code : TMB
Successfully applied multi-CSC.
Any ideas what this is and how i can get to the regular Philz touch CWM recovery so i can install custom ROMS?
Things maybe slightly different about my S5, i have a wireless charging accept pad installed on top of my battery and touching the two wireless charging nodes on the back of the phone so i can wirelessly charge.
I also have a gear fit paired with my phone, which i cant imagine is causing any issues.
thanks,
Devo
Click to expand...
Click to collapse
Philz Touch doesn't root your phone, CF-AutoRoot does. You can find it here: http://forum.xda-developers.com/showthread.php?p=51421053
andyshannon3 said:
I am trying to root my T-mo Galaxy S5 using the Philz touch recovery CWM. I got thru and put the phone in download mode, use odin v1.85 and load the tar.md5 file into the PDA section, i have tried 6.26.2 version of philz and also the 6.26.6 version, same issue with either one. It goes through and seems to work successfully, it says PASS in Odin at the end and my phone reboots normally. I then shut off my phone and hold the vol up + Home + Pwr keys to boot into Recovery mode.
When i do, i get one blue line saying "recovery booting..."
Then a quick screen showing an android bot with its belly open and little spinning wireframe orb in its belly with the words "installing system update..."
then as the attached screenshot shows, is what i see next...
in red at top it says:
Android system recovery <3e>
KOT49H.G900TUVU1ANCH
Volume up/down to move highlight;
power button to select.
My choices to scroll thru on screen are....
reboot system now
apply update from ADB
apply update from external storage
wipe data/factory reset
wipe cache partition
apply update from cache
In the background is an image of a droid bot laying down with a red yield sign over his open belly and the words "No Command"
at the bottom of hte screen in yellow it says...
# MANUAL MODE #
-- Appling Multi-CSC...
Applied the CSC-code : TMB
Successfully applied multi-CSC.
Any ideas what this is and how i can get to the regular Philz touch CWM recovery so i can install custom ROMS?
Things maybe slightly different about my S5, i have a wireless charging accept pad installed on top of my battery and touching the two wireless charging nodes on the back of the phone so i can wirelessly charge.
I also have a gear fit paired with my phone, which i cant imagine is causing any issues.
thanks,
Devo
Click to expand...
Click to collapse
I used Odin v3.07 to root Chainfires root and then I used the Philz recovery tar file to get the recovery... maybe you can Odin back to stock with Odin v3.07 and try that method with a fresh start.
I know its kinda late for this answer but what you have to do is disable the auto reboot option , now hit start when it shows you pass on the odin screen you can manually remove the battery and proceed to power the phone into the recovery mode and its done
I have the same problem as well. Have you found any solution to this?
Zororasto said:
I have the same problem as well. Have you found any solution to this?
Click to expand...
Click to collapse
You need to disable the auto-reboot option in Odin before installing the custom recovery. If you do not do this, android will reboot normally which will cause the custom recovery to be replaced by the stock recovery.
So disable auto-reboot, when the Odin status bar is full and Odin says PASS, you have to manually boot your phone into recovery (home, vol+, and power) and immediately install the latest supersu zip
dynospectrum said:
Philz Touch doesn't root your phone, CF-AutoRoot does.
Click to expand...
Click to collapse
Technically correct but misleading and off-point to the point of being incorrect. CF-autoroot is usually dependent on having a specific version of android. However, on any version of android, you can install a custom recovery (TWRP or Philz) with Odin, immediately boot into that recovery (without first booting into normal android) and flash the latest supersu zip file. This method is safe, easy, and universal in the fact that it works with any version of android.
I have the H933 variant of the V30. I want to wipe the partition cache after the Oreo update. I have tried the Pwr + down arrow. And then release power button and hold again at the boot screen. The only option I have is to factory reset the phone. I don't get the normal recovery options. Any help would be appreciated.
ern88 said:
I have the H933 variant of the V30. I want to wipe the partition cache after the Oreo update. I have tried the Pwr + down arrow. And then release power button and hold again at the boot screen. The only option I have is to factory reset the phone. I don't get the normal recovery options. Any help would be appreciated.
Click to expand...
Click to collapse
When I reboot into recovery, I am given the same choice on my US998. I choose factory reset, then I choose factory reset again. After all that, I get a screen that shows the "unlocked device" message for a moment and then finally TWRP.
I have had a situation where TWRP was NOT installed and when I did this my phone was completely erased...
Since then I have installed Quick Reboot Pro (free!) from the Google Play store. If your phone is rooted it gives you an option to boot into recovery. It goes straight to recovery and doesn't need any of the other (risky in my opinion) steps
ern88 said:
I have the H933 variant of the V30. I want to wipe the partition cache after the Oreo update. I have tried the Pwr + down arrow. And then release power button and hold again at the boot screen. The only option I have is to factory reset the phone. I don't get the normal recovery options. Any help would be appreciated.
Click to expand...
Click to collapse
Turn Off Your device.
Now Press and Hold Volume Down+Power button for 2-3 Seconds Until LG Logo Appears.
Release the volume down Button (hold power) Press and Hold them Again.
Hold the Buttons until the Recovery Mode Screen Appears.
Now You Are in the Recovery mode of Your device.
i succeeded only when gave up and approved Factory Reset then it finally switched to Recovery mode. Took 1 hour to find out, not a single guide on the internet or here was correct. I wonder if the reset really happened? Is reset prerequisite to run recovery mode?
doggydog2 said:
i succeeded only when gave up and approved Factory Reset then it finally switched to Recovery mode. Took 1 hour to find out, not a single guide on the internet or here was correct. I wonder if the reset really happened? Is reset prerequisite to run recovery mode?
Click to expand...
Click to collapse
Not if you are rooted. If the WTF guide I tell people to install a reboot recovery app that will take them straight to recovery.
doggydog2 said:
i succeeded only when gave up and approved Factory Reset then it finally switched to Recovery mode. Took 1 hour to find out, not a single guide on the internet or here was correct. I wonder if the reset really happened? Is reset prerequisite to run recovery mode?
Click to expand...
Click to collapse
worst case you could always use fastboot...
if your phone has twrp recovery, then it won't reset the phone. if you are running stock it will.
Agree with chazz though, assuming you have root and a bootable rom - reboot recovery is the best option
I never did really figure out why the lg phones can't boot directly into recovery using the buttons
If you install a terminal app, you can also get into recovery that way - "su" and then "reboot recovery".
I posted this on yt
I just realized magisk has the option to reboot to recovery. I've only used super su in the past.
well of course we have tons of apps, and recovery choice in power menu. but the boot shortcuts is the concern. those really suck.. can't even memorize them. need to write it down on the back of the phone
+1 here for confusion. I uninstalled Magisk after it strangely stopped working during the night and also could only to fastboot. After googling I also did the button dance to reset and yes then yes then got to twrp.
Nothing lost but strange way to go on (rooted device)
Actually, as I thought I had reset everything I updated to 21a so wasn't an entirely wasted 30 mins or so
How to solve it problem, anyone have same?
homedist said:
How to solve it problem, anyone have same?
Click to expand...
Click to collapse
this guy can help you ...
homedist said:
How to solve it problem, anyone have same?
Click to expand...
Click to collapse
I think I had the same issue. After OTA update, device requested a reboot. But it never rebooted completely and I got a message like this:
Code:
Android Recovery
Nokia/Crystal_00ww/CTL_sprout
9/PPR1.180610.....
user/release-keys
Use volume up/down and power.
Can't load Android system. Your data may be corrupt. If you continue to get this message, you may need to perform a factory data reset and erase all user data stored on this device.
Try again
Factory data reset
Supported API:3
Boot Reason: enablefilecrypto_failed
I took the SIM card off, connected a USB cable and launched the command:
Code:
fastboot getvar current-slot
I got the result:
Code:
current-slot: b
So i set the current slot to a and rebooted the device:
Code:
fastboot set_active a
fastboot reboot bootloader
Then, in Download Mode I pressed and held Volume Up and Power Key together until I saw No Command screen. At this moment I pressed and held Power Key and pressed Volume Up key until I saw the recovery options:
Code:
Android Recovery
Nokia/Crystal_00WW/CTL_srpout
10/QKQ1.190828.002/00WW_4_08B
user/release-keys
Use volume up/down and power.
Reboot system now
Reboot to bootloader
Apply update from ADB
Apply update from SD card
Wipe data/factory reset
Mount /system
View recovery logs
Run graphics test
Run locale test
Power off
Supported API:3
Boot Reason: (null)
Take into account that you should be seeing version 10 and not 9 in this Android Recovery screen. Version 10 has the name: 10/QKQ1.190828.002/00WW_4_08B. If you are seeing version 9 you have to set the other slot as active with fastboot command.
Once in the recovery menu, I selected Apply update from ADB and uploaded the Android 10 update with adb command:
Code:
adb sideload 29ad191f90eedc643ed008dc06c81ed3c5b5565a.zip
After applying the update, the next reboot took a while but finally the device started and I had not to wipe the data.
Thanks to xda-developers.com and techmesto for instructions about Nokia 7.1 recovery mode
Thank you so much
After wasting a few days trying to sort it out, these instructions helped me finally. Thank you so much
ubywan said:
I think I had the same issue. After OTA update, device requested a reboot. But it never rebooted completely and I got a message like this:
Code:
Android Recovery
Nokia/Crystal_00ww/CTL_sprout
9/PPR1.180610.....
user/release-keys
Use volume up/down and power.
Can't load Android system. Your data may be corrupt. If you continue to get this message, you may need to perform a factory data reset and erase all user data stored on this device.
Try again
Factory data reset
Supported API:3
Boot Reason: enablefilecrypto_failed
I took the SIM card off, connected a USB cable and launched the command:
Code:
fastboot getvar current-slot
I got the result:
Code:
current-slot: b
So i set the current slot to a and rebooted the device:
Code:
fastboot set_active a
fastboot reboot bootloader
Then, in Download Mode I pressed and held Volume Up and Power Key together until I saw No Command screen. At this moment I pressed and held Power Key and pressed Volume Up key until I saw the recovery options:
Code:
Android Recovery
Nokia/Crystal_00WW/CTL_srpout
10/QKQ1.190828.002/00WW_4_08B
user/release-keys
Use volume up/down and power.
Reboot system now
Reboot to bootloader
Apply update from ADB
Apply update from SD card
Wipe data/factory reset
Mount /system
View recovery logs
Run graphics test
Run locale test
Power off
Supported API:3
Boot Reason: (null)
Take into account that you should be seeing version 10 and not 9 in this Android Recovery screen. Version 10 has the name: 10/QKQ1.190828.002/00WW_4_08B. If you are seeing version 9 you have to set the other slot as active with fastboot command.
Once in the recovery menu, I selected Apply update from ADB and uploaded the Android 10 update with adb command:
Code:
adb sideload 29ad191f90eedc643ed008dc06c81ed3c5b5565a.zip
After applying the update, the next reboot took a while but finally the device started and I had not to wipe the data.
Thanks to xda-developers.com and techmesto for instructions about Nokia 7.1 recovery mode
Click to expand...
Click to collapse
ubywan said:
I think I had the same issue. After OTA update, device requested a reboot. But it never rebooted completely and I got a message like this:
[...]
Then, in Download Mode I pressed and held Volume Up and Power Key together until I saw No Command screen. At this moment I pressed and held Power Key and pressed Volume Up key until I saw the recovery options:
Click to expand...
Click to collapse
I managed to get to the Download mode successfully but then I am stuck at the highlighted step - cannot enter to recover menu to do sideload. Can you explain exactly how you did that ? Pressed power, released , and then pressed volume up? Or pressed sequentially and then released together ? Or pressed sequentially and released sequentially?
I did perform factory data reset earlier, not sure if this is causing my issues. Or maybe I am doing the key combination wrongly from your instructions...
ubywan said:
I think I had the same issue. After OTA update, device requested a reboot. But it never rebooted completely and I got a message like this:
Code:
Android Recovery
Nokia/Crystal_00ww/CTL_sprout
9/PPR1.180610.....
user/release-keys
Use volume up/down and power.
Can't load Android system. Your data may be corrupt. If you continue to get this message, you may need to perform a factory data reset and erase all user data stored on this device.
Try again
Factory data reset
Supported API:3
Boot Reason: enablefilecrypto_failed
I took the SIM card off, connected a USB cable and launched the command:
Code:
fastboot getvar current-slot
I got the result:
Code:
current-slot: b
So i set the current slot to a and rebooted the device:
Code:
fastboot set_active a
fastboot reboot bootloader
Then, in Download Mode I pressed and held Volume Up and Power Key together until I saw No Command screen. At this moment I pressed and held Power Key and pressed Volume Up key until I saw the recovery options:
Code:
Android Recovery
Nokia/Crystal_00WW/CTL_srpout
10/QKQ1.190828.002/00WW_4_08B
user/release-keys
Use volume up/down and power.
Reboot system now
Reboot to bootloader
Apply update from ADB
Apply update from SD card
Wipe data/factory reset
Mount /system
View recovery logs
Run graphics test
Run locale test
Power off
Supported API:3
Boot Reason: (null)
Take into account that you should be seeing version 10 and not 9 in this Android Recovery screen. Version 10 has the name: 10/QKQ1.190828.002/00WW_4_08B. If you are seeing version 9 you have to set the other slot as active with fastboot command.
Once in the recovery menu, I selected Apply update from ADB and uploaded the Android 10 update with adb command:
Code:
adb sideload 29ad191f90eedc643ed008dc06c81ed3c5b5565a.zip
After applying the update, the next reboot took a while but finally the device started and I had not to wipe the data.
Thanks to xda-developers.com and techmesto for instructions about Nokia 7.1 recovery mode
Click to expand...
Click to collapse
To do the fastboot commands the phone should be turned off or on? And one question, I can't install the drivers which are in my phone https://imgur.com/a/5LOskR5 the setup doesn't open..
Piotr_M said:
I managed to get to the Download mode successfully but then I am stuck at the highlighted step - cannot enter to recover menu to do sideload. Can you explain exactly how you did that ? Pressed power, released , and then pressed volume up? Or pressed sequentially and then released together ? Or pressed sequentially and released sequentially?
Click to expand...
Click to collapse
Press both at the same time and don't release them until the "No command" screen appears. There will be a restart in-between screens.
JaggerJam said:
To do the fastboot commands the phone should be turned off or on? And one question, I can't install the drivers which are in my phone the setup doesn't open..
Click to expand...
Click to collapse
If the phone is turned off, run the command and turn the phone on. The command will wait until the device is available.
Regarding the drivers, I have tested these commands from a linux machine where it is not necessary to install drivers.
---------- Post added at 01:51 PM ---------- Previous post was at 01:17 PM ----------
After runinng a few days with Android 10 the 2019-12 patch update popped up. I installed and reboot the phone but I got a similar error when the phone upgraded from Android 9 to Android 10:
Code:
Android Recovery
Nokia/Crystal_00WW/CTL_sprout
10/QKQ1.190828.002/00WW_4_08B
user/release-keys
Use volume up/down and power.
Cannot load Android system. Your data may be corrupt. If
you continue to get this message, you may need to perform
a factory data reset and erase all user data stored on this
device.
-----
Try again
Factory data reset
I tried the same instructions than I posted before without success, this time with the patch: 04dbc995492eb40f43593f984e723ec6a9b90f0f.zip from android.googleapis.com/packages/ota-api/nokia_ctlsprout_crystal00ww/. Anyway, a factory data reset works and the phone is running again. But if you don't disable "System Settings -> System -> Developer Options -> Automatic system updates" the patch keeps trying to install and then you have to reset your device.
I will wait until another patch will be released.
After applying the update and installing it with adb success state 0. I have rebooted the system now.
Still it is prompting me the same "Cannot load Android System"
Do i need to wipe the user data as well?
I have the same problem today after I tried to reboot.
So I went through this page
1) Downloaded the tools and adb file.
2) Connected the phone to computer and my PC detects it for a brief moment of about 1 to 2 seconds.
3) When I run the .\fastboot.exe getvar current-slot command, it waits for detecting the device but nothing happens. I select the "try again"option while the phone is connected to PC and the fastboot command still waiting for device but nothing happens.
Any idea of how to proceed further or did I miss anything?
Note: I didn't try factory reset yet. I'm hoping to recover my data. I have a lot of photos and videos that I don't want to loose.
Hello, thanks a lot!
I tried both slots a & b but I still see version 9 on top of the android recovery screen. So I ddon't dare going further an apply update from adb...
How can I update to Android Recovery
Nokia/Crystal_00WW/CTL_sprout
10/QKQ1.190828.002/00WW_4_08B ?
It keeps getting worse and worse : on slot B i'm always stuck in "Download mode" and slot A still android recovery version 9...
Anyone an idea?
Gagandeepskohli said:
After applying the update and installing it with adb success state 0. I have rebooted the system now.
Still it is prompting me the same "Cannot load Android System"
Do i need to wipe the user data as well?
Click to expand...
Click to collapse
I too have the same issue. adb ends with status 0 and am back to the bootloop as after restart.
ubywan said:
Press both at the same time and don't release them until the "No command" screen appears. There will be a restart in-between screens.
If the phone is turned off, run the command and turn the phone on. The command will wait until the device is available.
Regarding the drivers, I have tested these commands from a linux machine where it is not necessary to install drivers.
---------- Post added at 01:51 PM ---------- Previous post was at 01:17 PM ----------
After runinng a few days with Android 10 the 2019-12 patch update popped up. I installed and reboot the phone but I got a similar error when the phone upgraded from Android 9 to Android 10:
Code:
Android Recovery
Nokia/Crystal_00WW/CTL_sprout
10/QKQ1.190828.002/00WW_4_08B
user/release-keys
Use volume up/down and power.
Cannot load Android system. Your data may be corrupt. If
you continue to get this message, you may need to perform
a factory data reset and erase all user data stored on this
device.
-----
Try again
Factory data reset
I tried the same instructions than I posted before without success, this time with the patch: 04dbc995492eb40f43593f984e723ec6a9b90f0f.zip from android.googleapis.com/packages/ota-api/nokia_ctlsprout_crystal00ww/. Anyway, a factory data reset works and the phone is running again. But if you don't disable "System Settings -> System -> Developer Options -> Automatic system updates" the patch keeps trying to install and then you have to reset your device.
I will wait until another patch will be released.
Click to expand...
Click to collapse
Same problem, I did the adb install for Android 10 and and as soon as the security patch gets updated, we are back to square 1 into the reset loop with each restart
still no google security january 2020 for nokia7.1 ?
Same here for my mother's phone, as soon as 01/2020 security update gets installed, phone gets stuck and need to reset. Had this three times now.
Disabled automatic updates now in developer options.
Please confirm if a fix was published or found.
ubywan said:
Press both at the same time and don't release them until the "No command" screen appears. There will be a restart in-between screens.
If the phone is turned off, run the command and turn the phone on. The command will wait until the device is available.
Regarding the drivers, I have tested these commands from a linux machine where it is not necessary to install drivers.
---------- Post added at 01:51 PM ---------- Previous post was at 01:17 PM ----------
After runinng a few days with Android 10 the 2019-12 patch update popped up. I installed and reboot the phone but I got a similar error when the phone upgraded from Android 9 to Android 10:
Code:
Android Recovery
Nokia/Crystal_00WW/CTL_sprout
10/QKQ1.190828.002/00WW_4_08B
user/release-keys
Use volume up/down and power.
Cannot load Android system. Your data may be corrupt. If
you continue to get this message, you may need to perform
a factory data reset and erase all user data stored on this
device.
-----
Try again
Factory data reset
I tried the same instructions than I posted before without success, this time with the patch: 04dbc995492eb40f43593f984e723ec6a9b90f0f.zip from android.googleapis.com/packages/ota-api/nokia_ctlsprout_crystal00ww/. Anyway, a factory data reset works and the phone is running again. But if you don't disable "System Settings -> System -> Developer Options -> Automatic system updates" the patch keeps trying to install and then you have to reset your device.
I will wait until another patch will be released.
Click to expand...
Click to collapse
January security patch released.
i am getting an 'update package is older than the current build, expected a build newer than timestamp 1581332319 but package has timestamp 1573729404 and downgrade not allowed.'
i then tried the different zip file above and got 'package is for source build 00WW_4_08B but expected 00WW_4_08E.'
any ideas? i feel like i am so close to fixing this but just need the right update file!
knudsenda said:
i feel like i am so close to fixing this but just need the right update file!
Click to expand...
Click to collapse
No you are not! (Sorry to disappoint you, but I am in the same boat)
The instructions above are a bit outdated, the 04dbc995 file is 00WW_4_08B. There are other versions in https://forum.xda-developers.com/nokia-7-1/help/nokia-7-1-ota-update-ddls-t3866999/page9 for example d5c7c8ca7305ed19067b7e66b9b6525216161a90 is for version 00WW_4_08D, which was installed on my slot b.
But I could NOT find a file for 00WW_4_08E so I think we are stuck at the moment.
Greetings
I tried the file below and it says its for 00WW_4_08D! Anyone have the file for the 'E' version?
d5c7c8ca7305ed19067b7e66b9b6525216161a90.zip
same story here
I've got the same problem. Something in the Jan update screwed up my wife's phone. It will do the update fine, but on the next boot, it is stuck and you have to wipe the phone. I've tried doing the update with adb. It appears to load fine, but on the next boot, same story. Nokia only suggests sending it in, and of course we're of warranty. Doesn't look like anybody has a feb update that will work with my phone either(wrong version). Does anybody know if you can skip updates? Like apply the feb, but not the jan one? Thanks.
Somehow I got the January update to take hold. Here's what I think I did, although I rebooted so many times, I am not entirely certain if this is the exact sequence of events.
1. Applied update as you normally would. Phone gets in boot-loop and eventually ends with the "enablefilecrypto" error.
2. Proceeded with wiping phone, got to boot. Enabled developer options rebooted with adb to fastboot.
3. Phone was on slot a, changed to slot b.
4. Rebooted to recovery by holding power and up volume. Then power + up volume to start recovery.
5. Sideloaded feb update from the url provided in the updated download thread on this forum. I verified that this url is the same that my phone provides. Note that on previous attempts I had tried installing the jan update, but that never worked and it always reverted back to dec update after the mandatory wipe. Feb update appeared to work, although it threw an error about logs not existing.
6. Now I rebooted phone. Not totally sure, but i think it went into a boot-loop (flashing "android one" screen every 10 seconds or so for a while) but finally came up with the ecrypto message, with option to wipe or retry. I wiped and phone finally booted. Once it booted and I got through the initial setup, I found that Jan update has been applied but not Feb. This is weird, as I don't think I ever got Jan update successfully installed on either a or b. At this point if I try and install the updates through the normal method, it will not work and the final result will be the ecrypto error message or worse! So I have turned off updates for now.
I did get into a bootloop once where it would only boot to the bootloader screen and most normal methods would not get me out of it. I found that if changed the active slot with fastboot, it would then start flashing the "android one" screen a few times. While it's doing that if I held down volume up and power it would eventually get to the recovery screen. From here rebooting seemed to eventually work.
Anyhow what a cluster of a situation. Nokia doesn't offer much help but to send it in for $58. Not sure I want to waste any more time on this thing.