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

Urgent Help, time constraint - to Stock for return

I've been at this for like 8 hours going in circles. I have about 12 hours to figure this out. I am scheduled to go back to TMO to return this phone. Please help me.
While trying to revert back to stock, upon boot, at first there is a green icon, then it turns red w/ an exclamation point and just hangs there. It seems to have booted into the recovery because where it hangs, if i touch the "home" button, it disappears and shows me the cwm recovery main menu with a few errors relating to unable to mount SD. Its a very gimpy CWM with more than half of the commands/functions missing. (see pics below)
This is what I am currently getting in order....
{
"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"
}
- Boots to image 01
- Then to 02, here its trying to load/mount stuff, notice the SD icon and load bar near the bottom
- In 03 it looks like it ran into an error and hangs there
- Not sure why but I realized it boots straight into recovery. From 03, if i touch the home button I get 04. Notice all the stuff missing from cwm options
- 05 is what my HBoot / Bootloader looks like
-------------------------------
I am able to get back into HBoot / bootloader screen and can confirm that while in that mode the PC does recognize the device. But everything I flash does not work. When I run RUUs they seem to begin a process, but once that is done ( which isnt long), I would reboot but see nothing has changed. I tried to undo that stock recovery to access to NAND backups and start the process again but that Recovery doesn't have options for backups (strange?). Anyways, but can not flash another CWM successfully.
This is what I currently see when flashing a CWM now
c:\android-sdk\tools>fastboot flash recovery recovery-clockwork-touch-5.8.3.1-vi
lle.img
sending 'recovery' (6616 KB)...
OKAY [ 0.969s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 2.210s
c:\android-sdk\tools>fastboot reboot
rebooting...
I am completely out of options now. I looked at all the stickies around here and other places but can not find anything that will work. I did my best to be as thorough as I can. Please let me know if there are more info that would help. Thanks ahead of time.

This is One S development forum. Questions should be posted in questions.
Simple fix. Boot into bootloader and factory reset. Reboot once again into bootloader and format /erase sd card. Remember all this is being done from bootloader and not recovery. Reboot once again into bootloader and connect usb to phone and use fastboot to push cwm or whatever recovery you want to phone. Your sd card should now be mounted.
Not entirely sure about the return to stock, but being able to mount is a huge step in the right direction. Hope this helped
Sent from my HTC One S using xda premium

Chris Boyer said:
This is One S development forum. Questions should be posted in questions.
Simple fix. Boot into bootloader and factory reset. Reboot once again into bootloader and format /erase sd card. Remember all this is being done from bootloader and not recovery. Reboot once again into bootloader and connect usb to phone and use fastboot to push cwm or whatever recovery you want to phone. Your sd card should now be mounted.
Not entirely sure about the return to stock, but being able to mount is a huge step in the right direction. Hope this helped
Sent from my HTC One S using xda premium
Click to expand...
Click to collapse
Sorry if I posted in the wrong place. Usually when I ask a flashing related question there someone tells me it should be asked in Development.
Anyways, I tried that but nothing changed. Sucky thing is that current recovery I am using, I can't even make a backup, restore a backup, or even install a rom from there.

enzyme said:
Sorry if I posted in the wrong place. Usually when I ask a flashing related question there someone tells me it should be asked in Development.
Anyways, I tried that but nothing changed. Sucky thing is that current recovery I am using, I can't even make a backup, restore a backup, or even install a rom from there.
Click to expand...
Click to collapse
First and foremost you need a working recovery with a mounted sd card. Are you able to push anything via fastboot? I found it easiest to use a fastboot script. It dumbs it down to a couple mouse clicks. There is a utility for the one S called all in one. (sorry don't have link) maybe try that to install fresh recovery. One thing for certain, factory reset and then format card has to be done from bootloader mode and then push new recovery.
Sent from my HTC One S using xda premium

These are the steps I took that led me here.....
1. flashed ville_recovery_signed.img via Fastboot from here
2. re-locked the bootloader with in fastboot
3. ran RUU_Ville_U_TMOUS_1.53.531.16_Radio_0.16.31501S.02_10.18.31501S.08L_release_262073_signed from here that was from this thread.

http://forum.xda-developers.com/showthread.php?p=25850720
That should help, iv had that problem before and solved it from the post I just linked
Sent from my HTC One S using XDA Premium HD app

Moved To Q&A​
Do not open question threads in the development section, thats what Q&A is for.​

Chris Boyer said:
First and foremost you need a working recovery with a mounted sd card. Are you able to push anything via fastboot? I found it easiest to use a fastboot script. It dumbs it down to a couple mouse clicks. There is a utility for the one S called all in one. (sorry don't have link) maybe try that to install fresh recovery. One thing for certain, factory reset and then format card has to be done from bootloader mode and then push new recovery.
Sent from my HTC One S using xda premium
Click to expand...
Click to collapse
Yeah i have full control of Fastboot, just not always getting the desired final results. Yes I have the AIO pack and have tried to flash those recoveries w/o results. I mean from the log it looks like that did the trick but nothing changes after reboot, I can't get rid of the current Recovery.

stealthnoodle said:
http://forum.xda-developers.com/showthread.php?p=25850720
That should help, iv had that problem before and solved it from the post I just linked
Sent from my HTC One S using XDA Premium HD app
Click to expand...
Click to collapse
Steath! Now we are getting somewhere!
As I was going through the steps, I got the CWM from the AIO. That was before I had a chance to flash the 2nd time (step3), before I could get to the rest of the steps I allowed the phone to boot normal instead of HBoot, then it reverted back to the other recovery. But as of right now I did flash via AIO, cleared storage, factory defaulted, flashed via AIO again and now I am on step 5.
I am still sitting in the AIO CWM right now. The guide says to flash the UTB rom, which I am unfamiliar with and it appears like a custom rom. So what should I flash and what method should I use? Even though CWM is back I have no means to flash a ROM from there b/c my sd is empty. Should I .....
- flash one of the RUUs via fastboot?
-rename the RUU and push it to the SD via ADB and flash via CWM (like in the guide)?
(not sure if that method works with customRom only or RUUs as well.

enzyme said:
Even though CWM is back I have no means to flash a ROM from there b/c my sd is empty.
Click to expand...
Click to collapse
If you can mount your sdcard partition in recovery, you can then adb push a rom to it and flash it.
On your PC:
adb push yournewrom.zip /sdcard/
Then on your phone, in recovery:
Format system, data, cache
Flash zip from sdcard -> choose zip -> /sdcard/yournewrom.zip
Before you boot into the new rom, flash the boot.img (extract it from the zip) in fastboot.
adb reboot-bootloader
fastboot flash boot boot.img
fastboot reboot

Steath's advice led me to the guide and got me on the right track. Even with detailed instructions, I went in circles for awhile, but in the end I got it. I'm so relieved, its been a stressful 12hrs.
So now I just have one last question. Is it safe to extract boot.img & recovery.img and flash it with fastboot? This might even be a common practice who knows, I'm still very new to much of it.

enzyme said:
Is it safe to extract boot.img & recovery.img and flash it with fastboot? This might even be a common practice...
Click to expand...
Click to collapse
It is safe and common practice (and in many cases required to prevent bootloops) to extract the boot image from the rom you flash, and flash this boot image through fastboot.
Custom roms do not come with their own recovery (only their own boot.img). The only reason to extract a recovery from a RUU or OTA and flash it, is when you need to go back complete stock.
Edit: But if you want to switch to a different custom recovery, then yes, flashing it through recovery is safe and the proper way. (You just don't 'extract' it from anything.)

[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]TWRP 3.1.1-0 LG G5 H840

DO NOT FORMAT YOUR MICRO SDCARD INSIDE TWRP RECOWERY
WARNING: If you want tho use /data and internal sdcard first have to format data in stock recovery This will wipe your internal storage, and factory reset your phone!
encryption is not supported yet
To flash this img to your phone use fastboot
Code:
fastboot flash recovery twrp-x.x.x-x-h840.img
+new test build with encryption support
source code https://github.com/synescu/twrp_lg_h840
1.Unlocking the bootloader.
1.1Get the latest drivers: ( http://tool.lime.gdms.lge.com/dn/downloader.dev?fileKey=UW00120120425 )
1.2Get ADB fastboot. If you hate installing huge files for just a few commands, you have 3 options:
-MINIMAL ADB and fastboot: (https://forum.xda-developers.com/showthread.php?t=2317790 )
-15 seconds ADB Installer v1.4.3: (https://forum.xda-developers.com/showthread.php?t=2588979 )
-SDK Platform-Tools coming directly from google: (https://developer.android.com/studio/releases/platform-tools.html )
I personally went with the “15 seconds ADB Installer v1.4.3”, because it installs also a Google driver, which might, or might have not helped out in the process to follow.
1.3Follow the instructions at the official LG unlocking page ( https://developer.lge.com/resource/mobile/RetrieveBootloader.dev ), just keep in mind that after step 1.2 you have adb ready to go @ your main drive C:\adb. You go to that folder shift + right click and open a command prompt at that location, the rest is trivial.
2.Updating to the latest official stock android.
2.1Get the latest kdz from: (https://lg-firmwares.com/lg-h840-firmwares/ ). As far as I know you can go for any of those firmwares, but it is advisable to use one from your region (Europe, South America, Middle East). As mentioned above my LG G5 H840 is the newest European model, totally unbranded. So I took the 20c for Spain. This is as high as you can get at present moment.
2.2 Flash with LGUP 1.14 and UPPERCUT 1.0.0, both available at: (http://downloads.codefi.re/autoprime/LG/LG_G5 )
2.3 Reboot and do a quick setup. I recommend to have your sim card, SD card out at this moment, do not connect to wireless networks, all of this you will have plenty of time to do later, besides whatever you set at this point will be lost in the next step.
3.Get TWRP and root
3.1TWRP. As a courtesy of synescu, we have 2 versions: a regular one and such with encryption support. It took me long to realize that only the one with encryption would work on a latest H840 installed with v20c. So I guess if you have an old phone and possibly firmware 10a/b/c/d, than you can try “twrp3.1.1-0-h840.img”, otherwise go straight to “twrp_encryption-h840.img”. If you use the one without encryption support you will find no way to root the phone, because it can not see the SD card, or any USB flash attached and also if you connect the phone to a PC with MTP mode, or any other mode you won’t be able to browse both (internal and external) memories on that phone.
3.1.1Put on a SD card following files: 1) latest stable SuperSU 2.79 2) no-verity-opt-encrypt.zip from here (https://build.nethunter.com/android-tools/no-verity-opt-encrypt/no-verity-opt-encrypt-5.1.zip ) and just in case although not mandatory “twrp_encryption-h840.img”.
3.1.2Put in the C:\adb folder the “twrp_encryption-h840.img” and the stock recovery from here (https://forum.xda-developers.com/attachment.php?attachmentid=4149809&d=1494791791 ). The stock recovery is necessary in case you make a mistake and have to do a factory reset.
3.1.3Turn off the phone.
3.1.4Boot into stock recovery (holding volume down + power, at LG logo releasing power shortly and than pushing power again).
As a side note here, after I unlocked the bootloader I’ve got that annoying message on start-up that the phone is untrusted. With G4 H815 it was a small message in the upper corner, this time around it is a huge message in the middle of the screen. LG, for the love of god! After all the playing, I have now also a message screen, which I call “Options Menu”, it shows right after the nagging untrusted message. Although esthetically ugly, I have an easy way to go to recovery and fastboot in each and every regular power on, or restart. As said the Options Menu is showing up for 5 sec after the untrusted nagger. If you click the volume up, or down you get to the options (Power off, Restart, Recovery, Fastboot ), otherwise after 5 sec the phone would boot normally. I don’t know if this is the expected behavior of the phone, or did I trigger it somehow, but now I don’t have to use the combo buttons for anything.
Back from the side note. The new stock recovery is a white screen with 2 options for No and Yes. Go for YES and than YES again, after both YES the phone will be factory reset and will reboot. Do not allow it to boot though, because the userdata will be encrypted at this point and you will have to repeat the reset again. Use the combo buttons for recovery, which will bring you to the “Options Menu”, or Volume up and plug in the phone into the PC. Yet again there is hardly any time so maybe plugin in won’t be fast enough, so just keep pressed the combo buttons, also change with volume up and power, or remove the battery and start again. In any event do not let it boot until it brings you to the “Options Menu”
3.1.5In the Options Menu pick fastboot and plug the phone to the PC
3.1.6Open command prompt in adb and flash TWRP ( fastboot flash recovery twrp_encryption-h840.img ) you might be ok also to do factory reset from adb with this command (fastboot –w ), but unfortunately I forgot already if I did it, when it finally worked for me
3.1.7Disconnect from the PC and pull the battery out, or just keep the buttons combo pressed. It is possible that you see the old stock recovery (white screen YES/NO), which might have stayed somehow in memory. Do not perform further resets, just keep pressing the button combo and it will reboot eventually to the Options Menu.
3.1.8There you go 3 times volume down and power to pick recovery. Follows a reboot of the bootloader, nagging screens, but eventually it loads TWRP.
3.2Root.
3.2.1For some reason even after the factory reset, the data partition keeps an encrypted flag. So you can not write to it. Stock recovery should have reset it to non-encrypted, but it does not do it correctly, I guess. Therefore you go to Wipe, pick only the Data check box and go to change format in the bottom. Change the format to FAT and than back to EXT4
3.2.2Go to the SD card and flash no-verity-opt-encrypt.zip and SuperSu. Yes I know, that SuperSu is supposed to install also no-verity, but I like to flash both just in case.
3.2.3Do NOT wipe anything in TWRP at this point. Reboot only!!!!! Once the phone has booted in v20c you can go back to TWRP, Wipe and make all the backups you like
Thanks to @svetloslav for this complex post

Thanks a lot.
Can't wait to flash!!

YESS finally we have root on the SE thank you very much man

Hi all. When I try to flash recovery, fastboot give me that message:
target reported max download size of 536870912 bytes
sending 'recovery' (15089 KB)...
OKAY [ 0.490s]
writing 'recovery'...
FAILED (remote: image is not a boot image)
Any suggestion? Thanks
Solved: I had not extracted the .img from the .tar archive

synescu said:
For now external sd card is mounted as internal. De only way you can flash something for now When I would have more time I will try to fix this and upload the source to github. I rooted the phone and installed the supersu and no verity zip
source code https://github.com/synescu/twrp_lg_h840
Click to expand...
Click to collapse
Thanks a lot!
just a few information...
Is this build on android 6, 7 or 7.1 three?
Is encryption supported?

bob8x said:
Thanks a lot!
just a few information...
Is this build on android 6, 7 or 7.1 three?
Is encryption supported?
Click to expand...
Click to collapse
I'm booting this vith android 7.0
6.0 must boot just fine. didn't tried encryption but I'm pretty sure that doesn't work
Build compiled from Omni 6.0 sources
Sent from my LG-H840 using Tapatalk

Thank you very much for your precious time my friend. Good work

Can't flash magisk through twrp.
Can't mount data through twrp. It is greyed out. Can't select
Have you fix the ptoblem with external sd?

Wire1122 said:
Can't flash magisk through twrp.
Can't mount data through twrp. It is greyed out. Can't select
Have you fix the ptoblem with external sd?
Click to expand...
Click to collapse
Yes internal storage it's properly mounted now
Sent from my LG-H840 using Tapatalk

Anyone can confirm if encryption works?
Sent from my LG-H840 using Tapatalk

synescu said:
Anyone can confirm if encryption works?
Click to expand...
Click to collapse
I have flash it succesffully. But how can I yest if it works?

I can't backup my data partition with twrp. Whats wrong?
Sent from my LG-H840 using XDA Labs

Wire1122 said:
I can't backup my data partition with twrp. Whats wrong?
Sent from my LG-H840 using XDA Labs
Click to expand...
Click to collapse
{
"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"
}
Sent from my LG-H840 using Tapatalk

Can't backup data. :crying: unable to mount data ecc
Sent from my LG-H840 using XDA Labs

Wire1122 said:
Can't backup data. :crying: unable to mount data ecc
Sent from my LG-H840 using XDA Labs
Click to expand...
Click to collapse
In Order to use data first you have to factory reset your phone using the stock recovery
Sent from my LG-H840 using Tapatalk

How? Stock recovery? Where is it? I'm noob and rooted with supersu

My log

Wire1122 said:
My log
Click to expand...
Click to collapse
stock h840-recovery.img

I have flashed stock recovery but not have twrp anymore... What must do i do?
Sent from my LG-H840 using XDA Labs

Wire1122 said:
I have flashed stock recovery but not have twrp anymore... What must do i do?
Sent from my LG-H840 using XDA Labs
Click to expand...
Click to collapse
Why would you think that you would keep TWRP after flashing stock recovery? Also, why would you flash stock recovery after flashing TWRP and SuperSU? You either have TWRP or stock recovery, not both. Also, don't ever recommend flashing stock recovery after modifying system in any way unless you reflash whole stock system as stock. Anyways, all you need to do to get TWRP back is use the :
fastboot flash recovery TWRP.img

TWRP wont allow file transfer in USB via pc

NEED HELP
1. I wiped my system .. no system to load into
2. MIFLASH giving antirollback check error for all Fastboot roms
3. TWRP wont allow me to flash roms and there are no roms copied in the phone. getting error while copying files to the phone via TWRP
any solution ..
other than removing antirollback check in the roms .. ?

1. Is your bootlader CURRENTLY unlocked?
2. Which TWRP did you use?
3. Did you format all data using TWRP (enter yes to confirm) AND reboot TWRP before trying to copy rom to phone?
Sent from my Mi 10 Pro using Tapatalk

ted presley said:
1. Is your bootlader CURRENTLY unlocked?
2. Which TWRP did you use?
3. Did you format all data using TWRP (enter yes to confirm) AND reboot TWRP before trying to copy rom to phone?
Sent from my Mi 10 Pro using Tapatalk
Click to expand...
Click to collapse
bootload is unlocked
I figured it out loaded mi recovery wiped data and entered the system ..
I want to go to flash eu rom
do i dirty flash or do i clean flash the rom
stuck up on that part
TED can u help plz ..
I have used twrp-cmi-3.3.1-1
twrp-umi-3.3.1-2
what twrp are u using and i havent installed twrp
i am just booting TWRP
could you please tell me steps to 20.4.27

It seems you still on stock mi flash recovery, if your bootloader currently still unlocked.
You have to:
1. Go to fastboot
2. Flash TWRP again
3. Without restaring the device, reboot TWRP by using button combination: power off the device, press and hold volume down button until you see twrp screen
4. Format all data using twrp (option enter yes to confirm)
5. Reboot recovery using option reboot in TWRP recovery
6. Plug in pc to copy rom and flash.
Sent from my Mi 10 Pro using Tapatalk

ted presley said:
It seems you still on stock mi flash recovery, if your bootloader currently still unlocked.
You have to:
1. Go to fastboot
2. Flash TWRP again
3. Without restaring the device, reboot TWRP by using button combination: power off the device, press and hold volume down button until you see twrp screen
4. Format all data using twrp (option enter yes to confirm)
5. Reboot recovery using option reboot in TWRP recovery
6. Plug in pc to copy rom and flash.
Sent from my Mi 10 Pro using Tapatalk
Click to expand...
Click to collapse
twrp gives error saying
failed to mount /system_root permission denied
failed to mount /vendor permission denied
is it necessary the twrp should be installed
is it possible to just boot twrp while loading zips ..
thanks

sanish4u said:
twrp gives error saying
failed to mount /system_root permission denied
failed to mount /vendor permission denied
is it necessary the twrp should be installed
is it possible to just boot twrp while loading zips ..
thanks
Click to expand...
Click to collapse
problems just increasing now ..
the phone wont boot to twrp it will just go to fastboot
twrp wont load through volume down and power button

Seems like you lost TWRP
Reinstall twrp
Code:
Fastboot flash recovery twrp.img (use your filename)
Fastboot reboot recovery
Then when your in click the top right icon which says wipe. Here click on the right button I forget what it says I think it says wipe data. Next screen will ask you to type out the word "yes" you have to do this. You will lose all your data on the phone.
Now provided you have the drivers correctly installed you should see your phone as accessible from your computer. Paste your rom into the drive from your computer to the phone drive.
Once completed, go back to your phone you should be on the main menu click on top right it should say install. I believe you'll be in root directory you have to navigate to sdcard. Look for sdcard folder.
You should see the Rom you copied over, install it. It should take 5 to 10 minutes. Once complete reboot to system. First but will take some time maybe 5 to 10 minutes let it do it's thing.
Your done. If you want magisk, there are lots of guides here to do that as well

IronSingh said:
Seems like you lost TWRP
Reinstall twrp
Code:
Fastboot flash recovery twrp.img (use your filename)
Fastboot reboot recovery
Then when your in click the top right icon which says wipe. Here click on the right button I forget what it says I think it says wipe data. Next screen will ask you to type out the word "yes" you have to do this. You will lose all your data on the phone.
Now provided you have the drivers correctly installed you should see your phone as accessible from your computer. Paste your rom into the drive from your computer to the phone drive.
Once completed, go back to your phone you should be on the main menu click on top right it should say install. I believe you'll be in root directory you have to navigate to sdcard. Look for sdcard folder.
You should see the Rom you copied over, install it. It should take 5 to 10 minutes. Once complete reboot to system. First but will take some time maybe 5 to 10 minutes let it do it's thing.
Your done. If you want magisk, there are lots of guides here to do that as well
Click to expand...
Click to collapse
{
"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"
}
It just wont let me wipe data says permission denied image attached
and wont let me copy rom as it is connected it MTP mode

sanish4u said:
It just wont let me wipe data says permission denied image attached
and wont let me copy rom as it is connected it MTP mode
Click to expand...
Click to collapse
Mtp is ok no issues. Photo is broken can't see what you posted. Try wipe on the left button. Don't wipe system. Did you have a pin code setup for your phone to get in the phone are you entering this pin code when twrp starts? You should enter this pin/password

IronSingh said:
Mtp is ok no issues. Photo is broken can't see what you posted. Try wipe on the left button. Don't wipe system. Did you have a pin code setup for your phone to get in the phone are you entering this pin code when twrp starts? You should enter this pin/password
Click to expand...
Click to collapse
It wont boot twrp or install twrp ..
twrp wont load whatsoever now ..
my only option is only mflash tool ..
is there any Fastboot rom which wont cause anti rollback error check
If anyone finds any solution will be greatly appreciated ..
Thanks

I'm doubt that you have unlocked Bootloader, that's really a big problem here...
If your bootloader is unlocked, our mentioned steps should work fine.
Did you really unlock bootloader? And didn't locked it again accidentally while using miflash?
Sent from my Mi 10 Pro using Tapatalk

The way you describe your problem it seems you had twrp and you booted into it.
Can you tell me what happens when you run
Fastboot flash recovery twrp.img (use your filename)

IronSingh said:
The way you describe your problem it seems you had twrp and you booted into it.
Can you tell me what happens when you run
Fastboot flash recovery twrp.img (use your filename)
Click to expand...
Click to collapse
1. I have bootloader unlocked via miunlock
2. I had booted into TWRP .. it failed to wipe data many times..
3. I installed TWRP and now it does not allow me to do anything ..
4. Wont go to TWRP wont go to Mi recovery and will just go to fastboot
5. MiFlash wont flash as it has anti rollback check error tried all fastboot roms EU and CN
6. Trying to recover it via MIUI recovery loader but it wont download from servers either ..
<img src="https://i.ibb.co/KNjRdNL/twrp.jpg" alt="twrp" border="0">
https://ibb.co/KNjRdNL this was the error message while wiping data

sanish4u said:
1. I have bootloader unlocked via miunlock
2. I had booted into TWRP .. it failed to wipe data many times..
3. I installed TWRP and now it does not allow me to do anything ..
4. Wont go to TWRP wont go to Mi recovery and will just go to fastboot
5. MiFlash wont flash as it has anti rollback check error tried all fastboot roms EU and CN
6. Trying to recover it via MIUI recovery loader but it wont download from servers either ..
https://ibb.co/KNjRdNL this was the error message while wiping data
Click to expand...
Click to collapse
Try another TWRP
Sent from my Mi 10 Pro using Tapatalk

ted presley said:
Try another TWRP
https://1drv.ms/u/s!Amo9DwwPZk-vg9gNxQ-IcpcHDWTI7A
Sent from my Mi 10 Pro using Tapatalk
Click to expand...
Click to collapse
Thanks ted it did solve the problem
thanks for all the support

ted presley said:
Try another TWRP
Sent from my Mi 10 Pro using Tapatalk
Click to expand...
Click to collapse
I installed miui 12 with the twrp provided. it booted into the system.
I want to install gapps so it try to go back to twrp by using vloume down and power the phone goes to fastboot.
Volume up and power will load xiaomi recovery v3.0
Volume up and down with power will load MIUI rom recovery
What is going wrong why am i not able to load TWRP now ..

sanish4u said:
I installed miui 12 with the twrp provided. it booted into the system.
I want to install gapps so it try to go back to twrp by using vloume down and power the phone goes to fastboot.
Volume up and power will load xiaomi recovery v3.0
Volume up and down with power will load MIUI rom recovery
What is going wrong why am i not able to load TWRP now ..
Click to expand...
Click to collapse
Unless you use custom MIUI rom, stock MIUI always overwrite TWRP.
BTW, if you flash official China Dev rom, no need to flash GAPPs, just install additional play store apk (plus additional latest play service framework if needed) from apkmirror, all other necessary things installed by Xiaomi already.
Sent from my Mi 10 Pro using Tapatalk

ted presley said:
Try another TWRP
Sent from my Mi 10 Pro using Tapatalk
Click to expand...
Click to collapse
thank you brother <3