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.
Related
Hi Guys,
i have a very specific issue.
Its HTC hero which been upluged before finishing official upgrade to froyo.
So, where is the problem?
Hero cant boot, all the time just stay stucked on "HERO" boot animation. The problem is, that it was upgrade from stock Eclair to stock Froyo. They didn't have any root, or recovery (CWM, RA, nandroid)...
The phone can be started in hbot, fastboot, stock recovery.
HBOT->
I've found this > http://forum.xda-developers.com/showthread.php?t=575448 < but i think its need a function hero to set up setup.
So there is no way i think
Fastboot->
I've try to flash recovery with AR, CWM via
"fastboot flash recovery recovery.img"
but only get this
{
"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"
}
Stock recovery->
I've also try to flash via "apply update.zip from SD card" from this
http://www.modaco.com/topic/291942-22jan-stock-roms-radios-in-updatezip-format-for-gsm-hero/
every single file crashed "E:Verification failed!"
I'm such a big noob, but is there any way which i didn't try? Something like flash CWK recovery mode via update.zip? Every idea can help.
Thanks
Do you have your hero drivers set up on your PC?
Also, when flashing recovery.img using fastboot, please rename your clockworkmod.recovery.blablabla.img in recovery.img and then try to flash again.
as i thought so
prntscr.com/aun85 <its a link, but i'm newbie here, so i have a constraints
but its exactly the same as the file was named clockwokrmod.....img
Driver should be ok (get from android-cellphones com)
Q: how can i access the adb? In device manager a use this driver. But in cmd "adb devices" cannot find my hero. But idk if it helpfull.
Sorry for my english
When your phone is plugged in your windows PC (in hboot mode), check that the driver installed is called My HTC (in device manager), then download the latest RUU under HTC Hero support site (not the 2.1 one) and run the program, it will erase everything, but if it is successful it will install the 1.5 system to your phone, and you can start over
Sent from my GT-I9100 using xda premium
Problem was solved via hboot mode. Thx guys
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
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/
Hi all,
On Recently 7.2.1 updates, my device is failed to optimize (left it for the whole day alone)
So, i enter the recovery mode, performing the factory data reset. and when it done, reboot the device.
in this normal state, the OS is failed to enter, keep stuck at Nvidia logo forever.
Then, i enter the boot recovery kernel to
1) Wipe cache / partition
2) Wipe data / factory reset
and put the device into reboot when it done, but this appeared to be same (stuck at Nvidia logo and turn blank after a few hours)
This also put me into trouble because i cant apply the update via USB storage and ADB.
the error message is -- couldn't mount / usbdrive : Invalid argument (USB storage)
ADB device fastboot boot can't detect the device via PC
I provide the snapshot for your reference. Appreciate for your help and provide me a best solutions. Thank you
{
"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"
}
Garageflower said:
Hi all,
On Recently 7.2.1 updates, my device is failed to optimize (left it for the whole day alone)
So, i enter the recovery mode, performing the factory data reset. and when it done, reboot the device.
in this normal state, the OS is failed to enter, keep stuck at Nvidia logo forever.
Then, i enter the boot recovery kernel to
1) Wipe cache / partition
2) Wipe data / factory reset
and put the device into reboot when it done, but this appeared to be same (stuck at Nvidia logo and turn blank after a few hours)
This also put me into trouble because i cant apply the update via USB storage and ADB.
the error message is -- couldn't mount / usbdrive : Invalid argument (USB storage)
ADB device fastboot boot can't detect the device via PC
I provide the snapshot for your reference. Appreciate for your help and provide me a best solutions. Thank you
Click to expand...
Click to collapse
Fastboot and flash 7.1 developers image per Nvidia's instructions. I had the same problem and that worked for me of course this is considering your bootloader is unlocked
Hi. I am facing an issue with my oneplus 2 device, I wanted to make it boot multiple ROMs so searched on google about this and I found a thread on this website only, and in that thread, there was a recovery and zip file given to flash so I booted into TWRP recovery and flashed the zip file first and then recovery and then reboot-->recovery, after that oneplus logo with "powered by android" text came and for 5 mins nothing happened. I connected the phone to my computer and typed the fastboot command-"fastboot reboot recovery", it reboot and stuck at the same state as before, then I used-"fastboot reboot", it rebooted into the oxygen os which was installed on it. then I flashed the original TWRP recovery using its official app as my phone was rooted. After that, I again tried to flash the multirom recovery but this time I flashed the recovery first and then the zip file but the same happened. I again booted into the rom and flashed the original TWRP recovery using the app and then I got to know on the internet that I should first shutdown the phone after flashing multirom recovery and then reboot it in the recovery and then flash the zip file, so I did the same but to my bad luck this time also same happened and this time I am not able to boot into the rom also and I am only now able to use fastboot and to the very worst my bootloader has also got locked I don't know how but it was unlocked last time but when I saw in fastboot it was saying that bootloader is locked. Please help me to fix my phone I have attached the multirom recovery file and the link to the thread. Please tell me if you all want any other info I will try to provide you that.
LINK TO THE THREAD:-
[MOD][FEB-28][TESTING] MultiROM v33 for OnePlus 2
TLDR: MAKE A BACKUP. Seriously. Downloads in second post. Flash recovery, then kernel, then MultiROM. A kernel with the kexec-hardboot patch doesn't exist as of now. It is being worked upon be me Introduction This is a port...
forum.xda-developers.com
{
"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"
}