Database Info

[Q] Nexus S w/ CM 7.1.0 (no load & no recovery)

Can anyone help me with this Ive got a Nexus S, with the latest stable vers. of Cyanogen (update-cm-7.1.0-NS-signed) and ClockworkMod as the recovery image. Was working great then all of a sudden the phone will not load past the "Google" unlocked padlock image OR go into recovery mode. I can get into the bootloader alright (vol+ key & power button) and it confirms that the phone's still "UNLOCKED". All I get, on the screen, when I try to get into ClockworkMod is "Google" and the unlocked padlock image.
Can't even get into the SD card when I hook the phone up to my PC. Tried flashing CWM says that its sent and written but still wont load.
Any ideas how I can at least get into recovery mode? Once i'm in, in theory (if there's nothing terminal, hardware-wise) I can wipe the phone, mount the sd card, put a fresh vers. of CyanogenMod on it and start again.

Wrong section.

Soooooo moved.
Obligatory YOU MORON BLAH BLAH RABBLE RABBLE!!!!
....
Seriously though, what version of the Nexus S do you have? Just want to rule out any ID10T erros first. Second what CMW did you flash via fastboot? Thridly what was your fastboot command?

ackte11 said:
Can anyone help me with this Ive got a Nexus S, with the latest stable vers. of Cyanogen (update-cm-7.1.0-NS-signed) and ClockworkMod as the recovery image. Was working great then all of a sudden the phone will not load past the "Google" unlocked padlock image OR go into recovery mode. I can get into the bootloader alright (vol+ key & power button) and it confirms that the phone's still "UNLOCKED". All I get, on the screen, when I try to get into ClockworkMod is "Google" and the unlocked padlock image.
Can't even get into the SD card when I hook the phone up to my PC. Tried flashing CWM says that its sent and written but still wont load.
Any ideas how I can at least get into recovery mode? Once i'm in, in theory (if there's nothing terminal, hardware-wise) I can wipe the phone, mount the sd card, put a fresh vers. of CyanogenMod on it and start again.
Click to expand...
Click to collapse
How did you root it?
You just need to use fastboot to flash CWM & a new rom
Example for the rom:
fastboot update ROMFILENAME.ZIP -w
For more info on fastboot
http://wiki.cyanogenmod.com/wiki/Fastboot
Edit: There, got you the Cyanogenmod page. It's a step by step guide. Skip the bootloader unlocking section. Do all the rest.
http://wiki.cyanogenmod.com/wiki/Nexus_S:_Full_Update_Guide

slimdizzy said:
Soooooo moved.
Obligatory YOU MORON BLAH BLAH RABBLE RABBLE!!!!
....
Seriously though, what version of the Nexus S do you have? Just want to rule out any ID10T erros first. Second what CMW did you flash via fastboot? Thridly what was your fastboot command?
Click to expand...
Click to collapse
sorry bout posting in the wrong section. But Ive got the GT-I9020 version, Second I tried to flash versions 3.0.2.4-crespo, 4.0.0.2-crespo, and 5.0.2.0. Nothing responded.
$ fastboot flash recovery recovery-clockwork-4.0.0.2-crespo.img

ackte11 said:
sorry bout posting in the wrong section. But Ive got the GT-I9020 version, Second I tried to flash versions 3.0.2.4-crespo, 4.0.0.2-crespo, and 5.0.2.0. Nothing responded.
$ fastboot flash recovery recovery-clockwork-4.0.0.2-crespo.img
Click to expand...
Click to collapse
Do you have a working adb setup on your computer?
Put your device in fastboot mode ( VOL up + power button)
Make sure it's properly connected and interfacing with adb (you can type "adb devices" and you should see your device in the list)
If you don't see any string of characters after typing adb devices, then you don't have a working adb setup. You need either a standalone adb or the android SDK.

polobunny said:
How did you root it?
You just need to use fastboot to flash CWM & a new rom
Example for the rom:
fastboot update ROMFILENAME.ZIP -w
For more info on fastboot
---wiki.cyanogenmod.com/wiki/Fastboot
Edit: There, got you the Cyanogenmod page. It's a step by step guide. Skip the bootloader unlocking section. Do all the rest ---.cyanogenmod.com/wiki/Nexus_S:_Full_Update_Guide
Click to expand...
Click to collapse
tried that and got these results
$ fastboot update update-cm-7.1.0-NS-signed.zip -w
archive does not contain 'android-info.txt'
archive does not contain 'android-product.txt'
error: update package has no android-info.txt or android-product.txt

I have the android sdk but after "adb devices" its saying command not found

ackte11 said:
I have the android sdk but after "adb devices" its saying command not found
Click to expand...
Click to collapse
on a mac? also what about "fastboot devices"?

Linux Ubuntu 11.04 and Windows 7 "fastboot devices" recognizes it and shows the serial number. adb on windows runs the command but just comes up blank

ackte11 said:
Linux Ubuntu 11.04 and Windows 7 "fastboot devices" recognizes it and shows the serial number. adb on windows runs the command but just comes up blank
Click to expand...
Click to collapse
Alright. Try to flash CWM recovery first, as stated in the Cyanogenmod guide. Then once that's done, boot back into CWM and flash CM7.

Did that and it says that everything goes through, move down to recovery and it just loops the "google" padlock screen

ackte11 said:
Did that and it says that everything goes through, move down to recovery and it just loops the "google" padlock screen
Click to expand...
Click to collapse
Ah okay, maybe a corrupted boot.img
Download the full 2.3.6 rom for your model
i9020a
i9020t/i9023
You can get the model in fastboot mode at the top if you're unsure of which you own.
Extract the ZIP contents and grab hold of boot.img. Flash this boot.img using fastboot
Example: fastboot flash boot boot.img
Once that is done, reboot to fastboot and flash CWM. Then from CWM flash superuser and whichever ROM you want.

polobunny said:
Ah okay, maybe a corrupted boot.img
Download the full 2.3.6 rom for your model
i9020a
i9020t/i9023
You can get the model in fastboot mode at the top if you're unsure of which you own.
Extract the ZIP contents and grab hold of boot.img. Flash this boot.img using fastboot
Example: fastboot flash boot boot.img
Once that is done, reboot to fastboot and flash CWM. Then from CWM flash superuser and whichever ROM you want.
Click to expand...
Click to collapse
Nothings working. flashed the boot then CWM still cant get into recovery. Just right back to the "google" page

I am not sure if this works on the nexus s but give it a try.
Instead of flashing the recovery try and boot it. Change the command to fastboot boot recovery .....instead of flash.

albundy2010 said:
I am not sure if this works on the nexus s but give it a try.
Instead of flashing the recovery try and boot it. Change the command to fastboot boot recovery .....instead of flash.
Click to expand...
Click to collapse
still no go.

i am having the exact same problem, my computer can see my phone, but nothing is working. anyone have any input??? it seems like i can not write to certain parts of the sd card, it says, FAILED (remote: Write Fail)
trying to run an update. see how the image says it was copied over correctly? ive also tried ereasing it as well..
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
No boot or recovery img

This post specifically helped me.
http://forum.xda-developers.com/showpost.php?p=19531979&postcount=30
just rename the file "install-recovery.sh" which is in the /etc folder. You can only access it with a root file manager (rootexplorer $4 on the market)
make sure your new file is not ending with .sh
It appears that this file keeps writing stock recovery to your phone. Once you erase it, flash CWM recovery and then flash your rom. Hope it helps.

Nice catch. Didn't even think about it getting rewritten every boot.
Sent from my Nexus S using xda premium

[HELP] reboot and stuck on recovery mode only

i'm new here
yesterday i tried a new ROM, ICE_DS_v_4.2 but when done to update and i reboot my htc, it only appear htc screen fisrt boot
then i restore to my old ROM..
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
after done restore
and reboot again it just the same, stuck in htc screen
and when htc stuck on boot screen, i plug the usb..
try "adb devices" maybe still work..
but cant go tu SU
i remove the battery, turn on again, and now always go to recovery mode..
or you can see my attachments..
please, need some advice..
and sorry, if my english still bad

You don't know the difference between fastboot and adb.
Fastboot is accessible when the phone is in FASTBOOT mode in bootloader.
ADB is accessible when the phone is in recovery/ROM and booted past the kernel.
HTCDev-unlocked?
Search "fastboot flash boot.img".
May the search be with you (C).

Jack_R1 said:
You don't know the difference between fastboot and adb.
Fastboot is accessible when the phone is in FASTBOOT mode in bootloader.
ADB is accessible when the phone is in recovery/ROM and booted past the kernel.
HTCDev-unlocked?
Search "fastboot flash boot.img".
May the search be with you (C).
Click to expand...
Click to collapse
i'm very new here, for android user
i think not yet unlocked, root only..
here the report about sir.. when i do "fastboot flash boot.img"
C:\android-tools>adb devices
List of devices attached
SH215TJ01816 recovery
C:\android-tools>fastboot flash boot.img
unknown partition 'boot.img'
error: cannot determine image filename for 'boot.img'
C:\android-tools>
================== thanks

Isn't this what's shown when you don't have boot img in the correct folder?

padrik said:
i'm very new here, for android user
i think not yet unlocked, root only..
here the report about sir.. when i do "fastboot flash boot.img"
C:\android-tools>adb devices
List of devices attached
SH215TJ01816 recovery
C:\android-tools>fastboot flash boot.img
unknown partition 'boot.img'
error: cannot determine image filename for 'boot.img'
C:\android-tools>
================== thanks
Click to expand...
Click to collapse
You have to unlock your device before you can install custom roms.
And the correct way to flash boot is not "fastboot flash boot.img" but "fastboot flash boot boot.img"

505dv said:
You have to unlock your device before you can install custom roms.
And the correct way to flash boot is not "fastboot flash boot.img" but "fastboot flash boot boot.img"
Click to expand...
Click to collapse
thanks bro
this is how i try..
seems not respon anything on my device, using "fastboot flash boot boot.img" command..
*see my attachment*
something wrong..?

go here and start at the beginning. Replace reaper with whatever you want to runhttp://forum.xda-developers.com/sho...T4 recovery and custom ROM on HBOOT 2.00.0002
---------- Post added at 11:35 AM ---------- Previous post was at 11:34 AM ----------
http://forum.xda-developers.com/sho...T4 recovery and custom ROM on HBOOT 2.00.0002

Jack_R1 said:
You don't know the difference between fastboot and adb.
Fastboot is accessible when the phone is in FASTBOOT mode in bootloader.
ADB is accessible when the phone is in recovery/ROM and booted past the kernel.
Click to expand...
Click to collapse
I thought it was very clear.
When you have response to "adb devices", you can only work with ADB commands.
"fastboot" isn't ADB command, it's FASTBOOT command.
It should be run when the phone responds to "fastboot devices" command.
Now please search for the rest.

padrik said:
thanks bro
this is how i try..
seems not respon anything on my device, using "fastboot flash boot boot.img" command..
*see my attachment*
something wrong..?
Click to expand...
Click to collapse
Are you in fastboot mode when trying this command? Power down your phone, then hold volume down and press power. This will get you in the fastboot menu (white screen). Now plug in your USB cable. The fastboot menu should respond, changing its title to include USB.

jugg1es said:
go here and start at the beginning. Replace reaper with whatever you want to runhttp://forum.xda-developers.com/sho...T4 recovery and custom ROM on HBOOT 2.00.0002
---------- Post added at 11:35 AM ---------- Previous post was at 11:34 AM ----------
http://forum.xda-developers.com/sho...T4 recovery and custom ROM on HBOOT 2.00.0002
Click to expand...
Click to collapse
Jack_R1 said:
I thought it was very clear.
When you have response to "adb devices", you can only work with ADB commands.
"fastboot" isn't ADB command, it's FASTBOOT command.
It should be run when the phone responds to "fastboot devices" command.
Now please search for the rest.
Click to expand...
Click to collapse
505dv said:
Are you in fastboot mode when trying this command? Power down your phone, then hold volume down and press power. This will get you in the fastboot menu (white screen). Now plug in your USB cable. The fastboot menu should respond, changing its title to include USB.
Click to expand...
Click to collapse
thanks all, for your help.. your guide..
its already solved now, i'm using rom ICE_DS_v_4.2..
but, there's something i wanna ask again..
when my htc on standby, in a few moments, it suddenly turns itself off..
this morning already happen like that twice..
is there someone who get the same problem with me?
i havent install any application yet..
thanks

Search the damn forum dude. That same question must have been asked at least 10 times this year so far.
Sent from the darkest corners of my mind.

hi
Not able to find delet own post button. .

Htc D626 Q stuck in Recovery Mode After updating
Hi,
I have HTC D626 Q. 2days ago... when i connected WiFi, it want a ota update . I updated it but after restart it was showing No command screen ,than pressing lock button it is opening in recovery mode. Now still after opening phone it just open in recovery mode and stuck here.
Please Help me . Say me how can I fix this ????
Sorry my English is bad .
Reply me soon.

[Q] Bootloop - no recovery - no system - reset tamper flag - RMA

Hi guys,
my N5 is broken and i want to RMA ... It bootloops at the Google Logo, I can enter Fastboot, but NOT the recovery.
I managed to flash stock via fastboot and I locked the Bootloader.
After that I tried to reset the Tamper Flag with osm0sis' BootUnlocker zip ... well, ya need recovery for that. I tried to boot twrp with
Code:
fastboot boot recovery
but that returns "cannot load 'recovery': No such file or directory".
flashing the recovery works well ... but it doesn't boot into recovery, its bootlooping here to, even if you select recovery mode in fastboot.
So, any ideas how to do that now ?
thanks in advance !
EDIT
AWWW ..... after re-reading my post, I realized the command was wrong ..... its just boot ... not boot recovery ....jeeez
But anyway, even that results in a Bootloop .... so no way to access anything else but fastboot.

momsi said:
Hi guys,
my N5 is broken and i want to RMA ... It bootloops at the Google Logo, I can enter Fastboot, but NOT the recovery.
I managed to flash stock via fastboot and I locked the Bootloader.
After that I tried to reset the Tamper Flag with osm0sis' BootUnlocker zip ... well, ya need recovery for that. I tried to boot twrp with
Code:
fastboot boot recovery
but that returns "cannot load 'recovery': No such file or directory".
flashing the recovery works well ... but it doesn't boot into recovery, its bootlooping here to, even if you select recovery mode in fastboot.
So, any ideas how to do that now ?
thanks in advance !
Click to expand...
Click to collapse
it wont boot into recovery. boot into bootloader, then recovery, if no recovery, flash a recovery. btw, dont boot a recovery, flash it. if you run the script to boot it, itll only boot once. you need to fastboot flash recovery recoveryname.img
edit.. i noticed that you are booting a recovery. booting it only works for a one time use. dont boot it, flash it.
fastboot flash recovery recoveryname.img
Click to expand...
Click to collapse

fastboot boot recovery boots the phone to a recovery image on your PC.
So like fastboot flash...
fastboot boot path\to\recovery.img
Sent from my Nexus 5 using Tapatalk

I know that booting it is only one time use, I did that on purpose. But it didn't work either, see edit in OP.

momsi said:
I know that booting it is only one time use, I did that on purpose. But it didn't work either, see edit in OP.
Click to expand...
Click to collapse
the boot command is wrong as well. its fastboot boot recovery recoveryname.img
and the recovery file has to be in the same folder on your desktop as fastboot.

simms22 said:
the boot command is wrong as well. its fastboot boot recovery recoveryname.img
and the recovery file has to be in the same folder on your desktop as fastboot.
Click to expand...
Click to collapse
fastboot boot doesn't need you to identify a NAND partition as you're loading it into memory.
fastboot boot recovery.img is the command if your recovery is called recovery.img
The recovery file can be in any directory.
If you haven't installed fastboot correctly, you need to open the command prompt in (or change directory TO) the directory where fastboot.exe is. The easiest way to deal with this is as you say, drop the recovery image there, but you can also just prefix the recovery.img with the path if its anywhere else
However best practice would be to install fastboot correctly by manually adding it to environment variables or using the 15 second installer (or even dropping fastboot.exe in an existing environment variable path such as c:\windows\system32) at which point you can run fastboot no matter what directory command prompt is running in.
I cover most of the above in my "adb and fastboot. What is it?" Sticky thread in my signature
Anyway, sorry OP, I think you're stuck.
Sent from my Nexus 5 using Tapatalk

rootSU said:
fastboot boot doesn't need you to identify a NAND partition as you're loading it into memory.
fastboot boot recovery.img is the command if your recovery is called recovery.img
The recovery file can be in any directory.
If you haven't installed fastboot correctly, you need to open the command prompt in (or change directory TO) the directory where fastboot.exe is. The easiest way to deal with this is as you say, drop the recovery image there, but you can also just prefix the recovery.img with the path if its anywhere else
However best practice would be to install fastboot correctly by manually adding it to environment variables or using the 15 second installer (or even dropping fastboot.exe in an existing environment variable path such as c:\windows\system32) at which point you can run fastboot no matter what directory command prompt is running in.
I cover most of the above in my "adb and fastboot. What is it?" Sticky thread in my signature
Anyway, sorry OP, I think you're stuck.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
hmm.. ive always used fastboot boot recovery recoveryname.img, and never an issue.

simms22 said:
hmm.. ive always used fastboot boot recovery recoveryname.img, and never an issue.
Click to expand...
Click to collapse
Are you sure? It *shouldn't* work and certainly doesn't for me.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

rootSU said:
Are you sure? It *shouldn't* work and certainly doesn't for me.
Click to expand...
Click to collapse
you are right

Ah ok
Sent from my Nexus 5 using Tapatalk

Try fastboot format recovery then flash it again.
Sent from my Nexus 5 using XDA Free mobile app

Atomix86 said:
Try fastboot format recovery then flash it again.
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
did that ... didn't work....

Didn't work as in the format failed, or the recovery flash failed?
Sent from my Nexus 5 using XDA Free mobile app

I didn't see it mentioned but, have you tried a different alternative recovery? I speak from experience at one point after rooting, my phone would not launch the stock recovery. I then tried to use CWM (it's what I was familiar with) and it wouldn't boot either. I then went to TWRP and it did work.
Is it maybe possible the recovery image you have is corrupted or incomplete? Possible maybe you have the wrong one you're trying to flash and boot? I once mistakenly flashed my tablet with the recovery for my phone. Fixed that issue but it drove me nuts for a few hours wondering why it wasn't working.

Didnt work as in it stuck in the same bootloop again ...
no luck with other recoverys or other ..tried several
i only can enter fastboot

[Q] Stock OPO soft bricked after turning off at night.

Okay, here's the deal... I have an OPO (not mine) that is completely stock running, I would presume 5.0.2. I'm not exactly sure which build. But I was told that she turned the phone off at night and charged it. Turned it on in the morning and it got stuck on the cyanogen logo. No boot loops, no getting past that. Just sitting there. The device is stock, bootloader locked, no root. I also highly doubt that ADB debugging was turned on while it was working...
I'm trying to wipe it bring it back to stock, but I'm not having any success. I've gone in to Cyanogen recovery and wipe/factory reset, wipe cache, wipe media. Reboot, still stuck. When I click apply update in recovery, it gives me a bunch of errors saying so and so directory isn't found. So that leaves to me to believe that something went bad.
I just tried to fastboot oem unlock, said it finished in a few seconds. Then I tried to fastboot the factory image files and after the first one (modem), it gave me an error saying the bootloader is locked.
I'm out of ideas and the unbrick a hard bricked OPO thread said it wouldn't work, so I haven't tried it. Any advice on where to look would be much appreciated.

Anybody?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I get this when I hit Apply Update and then use storage as option.

moobieboobie said:
Anybody?
I get this when I hit Apply Update and then use storage as option.
Click to expand...
Click to collapse
Flash The whole Rom with fastboot to fix The Problem ....make a backup of your internal sdcard....

jamal2367 said:
Flash The whole Rom with fastboot to fix The Problem ....make a backup of your internal sdcard....
Click to expand...
Click to collapse
That's the problem. I can't because the bootloader is locked. When I try to unlock it, it runs the command. Then when I try to fastboot flash, it tells me the bootloader is locked. I have my own OPO that I have unlocked and rooted, so knowing how to unlock isn't an issue either.

moobieboobie said:
That's the problem. I can't because the bootloader is locked. When I try to unlock it, it runs the command. Then when I try to fastboot flash, it tells me the bootloader is locked. I have my own OPO that I have unlocked and rooted, so knowing how to unlock isn't an issue either.
Click to expand...
Click to collapse
Run CMD as Admin ...have you install the right driver for your phone and install the ADB drivers correctly? ...

jamal2367 said:
Run CMD as Admin ...have you install the right driver for your phone and install the ADB drivers correctly? ...
Click to expand...
Click to collapse
Yes, all updated drivers. Drivers are not the issue since I can execute commands while in fastboot. The issue is not having an unlocked bootloader, so I can't flash anything and it won't unlock bootloader.

moobieboobie said:
Yes, all updated drivers. Drivers are not the issue since I can execute commands while in fastboot. The issue is not having an unlocked bootloader, so I can't flash anything and it won't unlock bootloader.
Click to expand...
Click to collapse
Ps did phone was encrypt?

geowolf1000 said:
Ps did phone was encrypt?
Click to expand...
Click to collapse
No, phone was not encrypted and ColorOS unbrick didn't work. It recognizes the phone, I hit start and it does it's thing. After first green bar, it boot loops instead of flashing all the files. Ran as admin and all the drivers are good.

moobieboobie said:
No, phone was not encrypted and ColorOS unbrick didn't work. It recognizes the phone, I hit start and it does it's thing. After first green bar, it boot loops instead of flashing all the files. Ran as admin and all the drivers are good.
Click to expand...
Click to collapse
hit install from recovery
Choose file to update
Search files
Do you see your partition?
System exist?
What system do you have color or cyanogen?
Data?
Sd?

geowolf1000 said:
hit install from recovery
Choose file to update
Search files
Do you see your partition?
System exist?
What system do you have color or cyanogen?
Data?
Sd?
Click to expand...
Click to collapse
See post above with picture. It was running stock Cyanogen OS 12, not modded or anything. When I hit Apply Update and Choose from internal storage, I get the error in above picture.

moobieboobie said:
See post above with picture. It was running stock Cyanogen OS 12, not modded or anything. When I hit Apply Update and Choose from internal storage, I get the error in above picture.
Click to expand...
Click to collapse
But you have adb
Sideload full rom included recovery
From adb

geowolf1000 said:
But you have adb
Sideload full rom included recovery
From adb
Click to expand...
Click to collapse
If by sideload, you mean copy the rom to device and then load..I can not access device storage. ADB sideload rom through command line gives me the same errors you see in the above picture.

moobieboobie said:
If by sideload, you mean copy the rom to device and then load..I can not access device storage. ADB sideload rom through command line gives me the same errors you see in the above picture.
Click to expand...
Click to collapse
F**ing recovery
With adb you can navigate to system and change built.prompt and enable debugg mode
All the other method i know need root so dd (replace)recovery from adb

geowolf1000 said:
F**ing recovery
With adb you can navigate to system and change built.prompt and enable debugg mode
All the other method i know need root so dd (replace)recovery from adb
Click to expand...
Click to collapse
Can you give instructions on how to? I'm not too familiar with adb, but can follow steps.

moobieboobie said:
Can you give instructions on how to? I'm not too familiar with adb, but can follow steps.
Click to expand...
Click to collapse
Even this suggest need root.
All need root.... To system...

moobieboobie said:
Can you give instructions on how to? I'm not too familiar with adb, but can follow steps.
Click to expand...
Click to collapse
Another trick for installation is
Code:
fastboot boot <path/name of the recovery twrp img>
It will boot your phone into recovery once from the recovery image
stored in your PC temporarily
then you can flash the zip either by sideload or
Check this

geowolf1000 said:
Another trick for installation is
Code:
fastboot boot <path/name of the recovery twrp img>
It will boot your phone into recovery once from the recovery image
stored in your PC temporarily
then you can flash the zip either by sideload or
Check this
Click to expand...
Click to collapse
cannot fastboot boot recovery, tells me bootloader is locked and fails. the link requires unlocking bootloader, which is not working for me.

moobieboobie said:
cannot fastboot boot recovery, tells me bootloader is locked and fails. the link requires unlocking bootloader, which is not working for me.
Click to expand...
Click to collapse
Haz a parametre here

There is a way to flash an unlocked bootloader if you can't fastboot oem unlock.
As you already tried the color.zip method you should already have most of the needed files.
Download the attachment and unzip it into color folder replacing the files emmc_appsboot.mbn and rawprogram0_64.xml (backup the originals first).
-power off the OPO
-hold VolUp and plug into PC
-on PC open device manager, OPO should be in QDloader 9008
-keep an eye on device manager and start msm8974downloadtool from color.zip
-when in device manager the QDloader 9008 disconnects press stop in msm8974downloadtool
-OPO should now be Qualcomm Diagnostics 9006 in device manager
-download MiFlash from here http://www.androidbrick.com/ultimate-qualcomm-snapdragon-unbrick-guide-snapdragons-are-unbrickable/ and set it up like on the pictures on that website
-click refresh. now it should show you OPO on the respective COM port. click flash
-when successfull finished unplug and press and hold power for 30 seconds
-now start into fastboot with power + VolUp and there is your unlocked bootloader
-now you can flash cos with fastboot
The rawprogram0_64xml is edited so that it only writes partition table and flashes sbl1, dbi, rpm, tz, recovery and emmc_appsboot.
This worked for me when i couldn't flash with msm8974downloadtool, it always flashed modem, started with flashing system and then began from the start again.

tropenfrucht said:
There is a way to flash an unlocked bootloader if you can't fastboot oem unlock.
As you already tried the color.zip method you should already have most of the needed files.
Download the attachment and unzip it into color folder replacing the files emmc_appsboot.mbn and rawprogram0_64.xml (backup the originals first).
-power off the OPO
-hold VolUp and plug into PC
-on PC open device manager, OPO should be in QDloader 9008
-keep an eye on device manager and start msm8974downloadtool from color.zip
-when in device manager the QDloader 9008 disconnects press stop in msm8974downloadtool
-OPO should now be Qualcomm Diagnostics 9006 in device manager
-download MiFlash from here http://www.androidbrick.com/ultimate-qualcomm-snapdragon-unbrick-guide-snapdragons-are-unbrickable/ and set it up like on the pictures on that website
-click refresh. now it should show you OPO on the respective COM port. click flash
-when successfull finished unplug and press and hold power for 30 seconds
-now start into fastboot with power + VolUp and there is your unlocked bootloader
-now you can flash cos with fastboot
The rawprogram0_64xml is edited so that it only writes partition table and flashes sbl1, dbi, rpm, tz, recovery and emmc_appsboot.
This worked for me when i couldn't flash with msm8974downloadtool, it always flashed modem, started with flashing system and then began from the start again.
Click to expand...
Click to collapse
gave it a shot a few minutes ago.. As soon as 9008 dc fom device manager, i hit stop. the phone turns off or reboots (the screen goes blank)... I hear the connection, but no 9006.

[RECOVERY][UNOFFICIAL] TWRP 3.6.1 for UMIDIGI F1 and F1 Play [11/04/2022]

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
This is an UNOFFICIAL TWRP recovery for the UMIDIGI F1 and F1 Play
Builded from scratch
Whats Working :
- Decryption
- Backup / Restore
- ADB
- MTP
- OTG
- Flash System Image and Vendor Image also
Known Bugs :
- I think none
Instructions :
Using SP Flash tool
- Open flash_tool.exe from sp flash tool folder ( you can download it from here)
- Choose MT6771_Android_scatter.txt from UMIDIGI Stock Firmware
- Tap on Recovery and Choose TWRP-3.6.1-XX.img
- Click on Download and Reboot your Phone and plug your usb cable and press in Volume up button
-Wait to finish and enjoy
Using Fastboot ( you need Fastboot to do that)
- Power off
- Press on Power+Volume up button to boot up to Fastboot
- Execute "fastboot flash recovery TWRP-3.6.1-XX.img"
- Wait to Finish And Execute "fastboot reboot recovery"
- Enjoy
Using Another Recovery
- Copy TWRP-3.6.1-XX.imgto SD Card
- Press Install and Choose TWRP-3.6.1-XX.img and Choose Recovery
- Wait to Finish And Reboot to Recovery
- Enjoy
Downloads :
F1 : https://www.mediafire.com/file/91k98oii8ab7j1l/TWRP_3.6.1-F1.img/file
F1 Play : https://www.mediafire.com/file/dn8mzk8bpulvqig/TWRP_3.6.1-F1_Play.img/file
Device Tree : https://github.com/shadowofleaf96/android_device_umidgi_f1/tree/TWRP9.0
Credits :
- PeterCxy
- UMIDIGI
if you consider Donating
Thanks​

@Shadow Of Leaf, Thanks for your work.
I tried to flash the .img file today using fastboot command and for some reasons my F1 reboots to system, not recovery.
The fastboot flash command completed OK for both Sending and Writing but when I tried
fastboot reboot recovery
the phone reboots to the system.
I also tried
fastboot boot TWRP-3.5.2-F1.img
but get the same result.
Any idea what went wrong and how to fix it? TIA.

nnSlick said:
@Shadow Of Leaf, Thanks for your work.
I tried to flash the .img file today using fastboot command and for some reasons my F1 reboots to system, not recovery.
The fastboot flash command completed OK for both Sending and Writing but when I tried
fastboot reboot recovery
the phone reboots to the system.
I also tried
fastboot boot TWRP-3.5.2-F1.img
but get the same result.
Any idea what went wrong and how to fix it? TIA.
Click to expand...
Click to collapse
it is not fastboot flash boot
it is fastboot flash recovery TWRP-3.5.2-F1.img
when it finished tap fastboot reboot when phone is rebooting click on volume down until the bootlogo come out then it will go to recovery

Shadow Of Leaf said:
it is not fastboot flash boot
it is fastboot flash recovery TWRP-3.5.2-F1.img
when it finished tap fastboot reboot when phone is rebooting click on volume down until the bootlogo come out then it will go to recovery
Click to expand...
Click to collapse
@Shadow Of Leaf
Thanks for the prompt response, appreciate it.
I was not clear in my previous post, what I meant was I tried 2 ways
1. flash using fastboot flash command, and
2. boot directly using fastboot boot command
and both times I could not get TWRP to run.
Here is the output of the first method:
When I click on Vol- while the device was rebooting, I saw the boot logo andn then a screen with Chinese menus on the left top of the screen. Weird!
May be the file was not written properly? I tried to redownload the file twice but same thing happens.

nnSlick said:
@Shadow Of Leaf
Thanks for the prompt response, appreciate it.
I was not clear in my previous post, what I meant was I tried 2 ways
1. flash using fastboot flash command, and
2. boot directly using fastboot boot command
and both times I could not get TWRP to run.
Here is the output of the first method:
View attachment 5380507
When I click on Vol- while the device was rebooting, I saw the boot logo andn then a screen with Chinese menus on the left top of the screen. Weird!
May be the file was not written properly? I tried to redownload the file twice but same thing happens.
Click to expand...
Click to collapse
did you unlock your bootloader ???
if yes when flash try the power and volume down combination to go recovery
if not try this
Unlock the bootloader (will result in a factory data reset and a warning message on the boot screen) YOU LOSE YOUR WARRANTY BY DOING THIS!!!
a) Enable Developer options
b) Enable OEM unlock and USB debugging. (Install ADB drivers on your computer)
c) Connect your phone to USB and in a command window type adb reboot bootloader
d) Type fastboot flashing unlock
e) Confirm your decision on the phone (You can re-lock the bootloader with fastboot flashing lock)

Shadow Of Leaf said:
did you unlock your bootloader ???
if yes when flash try the power and volume down combination to go recovery
if not try this
Unlock the bootloader (will result in a factory data reset and a warning message on the boot screen) YOU LOSE YOUR WARRANTY BY DOING THIS!!!
a) Enable Developer options
b) Enable OEM unlock and USB debugging. (Install ADB drivers on your computer)
c) Connect your phone to USB and in a command window type adb reboot bootloader
d) Type fastboot flashing unlock
e) Confirm your decision on the phone (You can re-lock the bootloader with fastboot flashing lock)
Click to expand...
Click to collapse
I did unlock the bootloader, and every time the phone reboot I see a warning that the device is unsafe.
It appears that flashing went OK, as reported by the 'fastboot flast recovery...' command. But when I try to go to recovery with Power+VolDown combination the phone just could not run TWRP!
I am not sure if it is related but after power off, when I try to reboot with Power+Vol Down (or Up) combination the boot logo appears then disappears (looping?) and I do not see a boot menu (as shown in a YouTube video). When I reboot from fastboot it seems to go to some boot program with a Chinese menu.

nnSlick said:
I did unlock the bootloader, and every time the phone reboot I see a warning that the device is unsafe.
It appears that flashing went OK, as reported by the 'fastboot flast recovery...' command. But when I try to go to recovery with Power+VolDown combination the phone just could not run TWRP!
I am not sure if it is related but after power off, when I try to reboot with Power+Vol Down (or Up) combination the boot logo appears then disappears (looping?) and I do not see a boot menu (as shown in a YouTube video). When I reboot from fastboot it seems to go to some boot program with a Chinese menu.
Click to expand...
Click to collapse
ok another solution
try to reboot your phone to the system and enable adb (android debug shell) and type adb reboot recovery
it will reboot to recovery

Shadow Of Leaf said:
ok another solution
try to reboot your phone to the system and enable adb (android debug shell) and type adb reboot recovery
it will reboot to recovery
Click to expand...
Click to collapse
@Shadow Of Leaf
Appreciate you prompt help!
Not sure what happened but I retried one more time and guess what it works this time . Thank you so much!
I notice that it takes long time to show the menu and it looks like TWRP tries to decrypt data, even though I already did a factory reset.
Now I can root and install custom ROMs. Thanks again!

nnSlick said:
@Shadow Of Leaf
Appreciate you prompt help!
Not sure what happened but I retried one more time and guess what it works this time . Thank you so much!
I notice that it takes long time to show the menu and it looks like TWRP tries to decrypt data, even though I already did a factory reset.
Now I can root and install custom ROMs. Thanks again!
Click to expand...
Click to collapse
you welcome anytime

Hi thank you so much for your work.
But when I try to flash recovery and suddenly, when I type fastboot reboot recovery , it says something like can't get recovery partition unable, and then when I go manually into recovery I get stock one.
Of course the flashing of twrp recovery goes all well, so it's a strange issue. Just one time after the flash I successfully got twrp but lost after reboot and I didn't have internal memory mounted.
Can you help me?
Thanks

kayuz said:
Hi thank you so much for your work.
But when I try to flash recovery and suddenly, when I type fastboot reboot recovery , it says something like can't get recovery partition unable, and then when I go manually into recovery I get stock one.
Of course the flashing of twrp recovery goes all well, so it's a strange issue. Just one time after the flash I successfully got twrp but lost after reboot and I didn't have internal memory mounted.
Can you help me?
Thanks
Click to expand...
Click to collapse
yes for sure
first use this recovery https://forum.xda-developers.com/t/...icial-twrp-3-3-1-for-umidigi-f1-play.4007315/ for now
data exryption work
flash this recovery in fastboot(fastboot flash recovery 'recovery file') and type fastboot reboot
when reboot a long click on volume up button until seeing umidigi logo it will work

Shadow Of Leaf said:
yes for sure
first use this recovery https://forum.xda-developers.com/t/...icial-twrp-3-3-1-for-umidigi-f1-play.4007315/ for now
data exryption work
flash this recovery in fastboot(fastboot flash recovery 'recovery file') and type fastboot reboot
when reboot a long click on volume up button until seeing umidigi logo it will work
Click to expand...
Click to collapse
that's the error:
fastboot: usage: unknown reboot target recovery
I tried but can't access recovery, I need to plug out the cable before pressing vol up?

kayuz said:
that's the error:
fastboot: usage: unknown reboot target recovery
I tried but can't access recovery, I need to plug out the cable before pressing vol up?
Click to expand...
Click to collapse
just go to stockrom and type adb reboot recovery

I solved flashing the twrp by another person, currently on phone so can't see who was.
Anyway it appears that was an issue with decryption, because that twrp can see internal storage. Flashed all and will send feedback in appropriate thread ;-)
Shadow Of Leaf said:
just go to stockrom and type adb reboot recovery
Click to expand...
Click to collapse

TWRP 3.6.1 stable new version at last
i think it is bugless but try it out and report

Shadow Of Leaf said:
TWRP 3.6.1 stable new version at last
i think it is bugless but try it out and report
Click to expand...
Click to collapse
hello friend, could you tell me what process you did to compile a twrp for your umidigi, I wanted to make one for my umidigi a9 pro 2021, it has the same processor as your device.

Isaac™ said:
hello friend, could you tell me what process you did to compile a twrp for your umidigi, I wanted to make one for my umidigi a9 pro 2021, it has the same processor as your device.
Click to expand...
Click to collapse
you can use this guide to build twrp for your device and use this device tree thats is compatible with your device and has a newer vendor (mine is comptable with old pie vendor that will have issues with data encryption)
link of the guide : https://github.com/ADeadTrousers/twrp_device_Unihertz_Atom_LXL/blob/master/docs/HOW-TO-BUILD.md
links of device tree : https://github.com/ADeadTrousers/twrp_device_Unihertz_Atom_XL_EEA
Common device treehttps://github.com/ADeadTrousers/twrp_device_Unihertz_Atom_LXL
you have to change the common device tree and the device tree to your device