Database Users

[Q] Factory image restore with NRT, stuck at "writing system"

Hi everyone,
Yesterday, I tried the 4.4 OTA on my wifi Nexus 10 (unlocked but not rooted, previously 4.3), but got an "Error!" screen, and now the device seems soft-bricked (can't boot into system, get a "No command" screen, but I can get the bootloader screen with Power + both volume keys).
After some investigation, I tried restoring a factory image using Nexus Root Toolkit v1.7.8, after recharging the device a full night. I used the "Flash Stock + Unroot" with "Soft-bricked / Bootloop" option. At first everything looked fine, but I'm now stuck at "writing system" step, for 30 min now:
{
"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"
}
The strange thing beeing, the device shows "Fastboot status - okay":
Might it be a sync status problem between NRT and the device? Is it safe to stop the operation and try to reboot my Nexus?
Thanks for your help.

Hi. I have the same problem.
How did you manage to solve this?
Regards

Hi,
Yes I did.
I was still stuck in the "writing system" test, and rebooted the device. As I feared, the system didn't boot, so retried the stock kitkat flash through NRT. The second pass got me to the same result, stuck in "writing system" with the device saying "fastboot okay".
I decided to reboot to recovery, and wiped both system and cache partition. When I reboot, I was able to see the kitkat startup screen, and then everything went fine.
Eventually, I'm not able to tell what went wrong or good with the flashing, but here are my observations and facts :
- once launched, the system initialized correctly, and I didn't encounter any problem since then
- even if the system partition appears to be flashed correctly, I was still amazed that everything works, since the user partition hasn't been written
- only the stock system has been installed. No root nor custom recovery.
As for the root cause of the initial OTA problem, I think it was caused by lack of battery power.

Is there a way to reload the factory recovery partition?

Hello guys, just wondering if there is a way to reload the factory recovery partition?
I am getting a demigod error and cannot do anything in recovery once I try to restart into it, but the phone when restarted works fine with the factory image.
I tried to load a custom rom and done screwed up
I did make a recovery backup, but I am pretty sure I screwed it as I was trying to copy recovery.img to the phone during some un-bricking troubleshooting.
Thanks

Okay guys, I know I should be doing my own research but I'm stuck.
I found this youtube video:
https://www.youtube.com/watch?v=hQVTc2m6U-I
I've downloaded all of the LG G2 D801 T-Mobile files:
http://downloads.codefi.re/autoprime/LG/LG_G2/D801BK/Stock_Firmware/20a_partitions
I am able to get ADB to recognize my device and I am able to 'send' commands via fastboot BUT my phone doesn't seem to accept them.
I've tried via command line and using SRK tool:
Here is what happens when I try to run the fastboot commands in fastboot mode (UP button + USB plugin)
{
"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"
}
Here is what I get when I try to run SRK Tool:
So as you can see from the output, the phone is detected and it seems like the files are in the process of being 'sent' but nothing actually installs.
When I was doing it in command prompt, I let it sit for a few minutes for a few commands and they just sat there at writing.
On the phone itself, this is what it states at this moment:
[500] fastboot mode started
[500]--reset--
[500]--portchange--
[500]--reset--
[500]--portchange--
[500] fastboot: processing commands
[500]fastboot: getvar: partition-type:laf
[500]fastboot: getvar:max-download-size
[500]fastboot: download:00e00000
[500]fastboot: flash:laf
That's all I get on the phone, nothing changes. It just sits there idle.
I am unsure what to do and was wondering if anybody knows how I can fix this?

So I seem to be having some kind of issue with the phone not accepting fastboot commands and/or my computer is not recognizing fastboot.
I did install the ADB/Fastboot installer. I have Java and SDK installed.
When I try to run ADB devices, it identifies the device.
When I try to run fastboot devices, all I get is:
command prompt> fastboot devices
? fastboot
That's all.

Anyone? I am having the same exact problem and have not found a fix yet.

Look at my last reply here: http://forum.xda-developers.com/lg-g2/help/g2-fastboot-mode-t3427770 it may work

Lost recovery but Rom OK?

I seemed to have lost my recovery but my phone is otherwise working.
I went from CM13 with TWRP, downloaded OS3 from the official oneplus web download as well as the "optional recovery" on the same page.
I wiped data/system/dalvik/cache and flashed the OS 3 zip.
I then flashed the stock recovery img.
Wiped again.
Rebooted to recovery from TWRP and got stuck with the oneplus logo. Completely non-responsive.
Fearing I had softbricked the phone, I started with ADB, got the Qualcom HUB listing under Device Manager and was about to start the process of updating Qualcom Drivers and running the recovery tool (having not been able to get fastboot to see the device) when a miracle happened and the phone started booting up on its own. After running setup, I rebooted, no problem.
I have since been able to use fastboot oem lock and confirmed the phone is locked (I wanted to get back to stock).
Everything is working fine EXCEPT I don't seem to have any Recovery at all. If I use the Developer Option for Advanced Recovery and boot into recovery, I get the oneplus logo. If I use Vol Down and Power I get the oneplus logo.
I think I have lost my recovery but recognise that I am out of my depth and don't want to stuff up the second chance I was given by trying to flash a recovery (I want stock receovery so I can get OTAs in the future). BTW, I read extensively before I tried this, looking at a number of different sites and followed instructions to the letter (or at least I thought so!).
Could someone who knows what to do please help to get my recovery back? It would be very much appreciated.
Edit: I managed to fix it. You have to use the Qualcomm tool and go back to OS2.2 and then update to OS3. See the link below and follow Method 1, doing everything exactly as set out.
{
"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"
}
https://forums.oneplus.net/threads/...ck-guide-for-a-hard-bricked-oneplus-2.347607/

Error while Flashing Twrp 2.8.6 recovery.

I have flashed twrp recovery on my redmi note 4g. But after flashing when I rebooted to recovery mode, The teamwin logo appeared 4 times divided on my screen. I am unable to read any option.
Please give me a solution for this. I am attaching an image of my problem. Please help 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"
}

aks279 said:
I have flashed twrp recovery on my redmi note 4g. But after flashing when I rebooted to recovery mode, The teamwin logo appeared 4 times divided on my screen. I am unable to read any option.
Please give me a solution for this. I am attaching an image of my problem. Please help me.
Click to expand...
Click to collapse
Flash this.

ray.77141 said:
Flash
Unable to flash from from my mi recovery. Verification error. I think i need a signed version of this or any other method of flashing?
Click to expand...
Click to collapse

aks279 said:
ray.77141 said:
Flash
Unable to flash from from my mi recovery. Verification error. I think i need a signed version of this or any other method of flashing?
Click to expand...
Click to collapse
Flash Recovery Using Adb Tools
You need 3 things
(a) Xiaomi usb drivers [download from Here ]
(b) adb drivers (download from Here ]
(c) TWRP recovery (TWRP download from Here ]
Procedure:-
1. install xiaomi usb drivers
2. extract adb drivers anywhere in your computer
3. copy recovery.img into adb tools folder
4. boot your phone into fastboot mode by pressing volume down key and pressing power key simultaneously , and then releasing power key .
5. connect your device to your computer through data cable
6. go into adb tools folder => while pressing shift key => right click => and click open cmd here !
7. type "fastboot flash recovery recovery.img" and press enter
8. Done
Click to expand...
Click to collapse

help me

i made a mess, i can't install anything, i tried here to do repair installation for sansung a20s software, but it immediately failed, also it doesn't let me exit this screen anymore
{
"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"
}

thanks i solved by flashing the original stock firmware again

To root your device, start by flashing TWRP, which you can find here. The TWRP .tar file goes in the AP slot of Odin.
Once you have TWRP installed, you should be able to flash Magisk, which you can find here.

how installa TWRP, i have error
this trying to put... twrp-3.7.0_9-0-a20.img

I didn't notice that OEM LOCK is ON.
You must unlock your bootloader to flash custom images.

ok i haveTWPR done
but after reload sisytem ...

this is very strange, for an old phone, I don't understand, I've never had all these problems ...

i m crazy

Did you flash vbmeta as well as TWRP? This might be the right file

I have to try again ,,,, but I still haven't figured out if anyone has been successful in rooting this device ,, I sansumg told everyone to do it

then, then yesterday I reflexed the original stok, now so I first do a TWPR and THEN this file that you are providing me?

yesss done good
now I need more help, I put TPWR then The file repairs vbmeta ,, ...., but it tells me that I don't have root permissions yet

do i have to give up?

Did you get a working twrp? Try booting into recovery (twrp) and then flash Magisk-v25.2.apk. If that works, reboot into system and install Magisk-v25.2.apk as an app. Then start the app and it will tell you whether you have root. If it doesn’t work, I don’t know what to do next. You may need to have the Magisk apk on a usb drive or microSD card for it to be visible in twrp.

the problem is that I put the TWPR gives me an error
vbmeta ,, then I put your tar file (
vbmeta_disabled.tar
2 KB · Views: 1) the phone starts, but in recovery I don't see TWPR the android menu looks normal

from this menu I tried to install the magic, but the installation fails

When you install twrp from Odin, disable automatic reboot from Odin options. Once you see that the flashing is completed, reboot the phone by holding vol- and power for 7 seconds, then immediately hold vol+ and power to boot into recovery. Otherwise twrp will get overwritten with stock recovery and you have to try again.

I am thinking that by reviewing the file (vbmeta_disabled) it overwrites the TWPR that I first put ,, in the revvr mod it always starts me with the classic menu
[email protected]
but every time I install a TWPR I have to insert after the file (vbmeta_disabled) because otherwise the phone always restarts with vbmeta error in download mod

Use 7-zip and add vbmeta.img from the tar above to the twrp tar and flash that

no work,,stay that way