Database Info

[Q] adb reboot recovery has stopped working

I was stuck in a boot loop only way to do a factory reset was to use adb command line ie adb reboot recovery to enter recovery menu and it work now it's back on boot loop and the command adb reboot recovery no longer work it just reboot to the boot loop i'ave tried adb shell recovery wipe data but it just brings up a flashing yellow screen adb shell wipe data then reboot results in the boot loop adb shell reboot recovery same results i have tried adb shell echo -e boot recovery\0 >/dev/block/nandf; sync then reboot all still in shell same results my device is not rooted is there another code i or codes i can try?

Need ROM N915K or Help

HI to all I try to root mu n915k but nothing work, and my phone now not started stuck in the boot.
I try to flash K195S firmware via odin, but phone not flashed, odin send error(
i cant find firmware for my N915K in internet
If you have rooted N915K please do it for me and i try to restore my phone:
can do it in terminal emaulator app.
su
dd if=/dev/block/platform/15540000.dwmmc0/by-name/BOOT of=/sdcard/boot.img
This will dump the boot partition onto their internal device storage (sdcard). The size should be 14MB.

https://www.dropbox.com/s/v34fcyu84fqw2je/n915k_boot.img?dl=0

Many thanks for you work!!
I flash boot.img But my n915k phone not started ((
I think in my phone have a wrong recovery.img aboot.img and cashe.img because i try to flash different firmware
Maybe if you have a time, please send me this partitions! Many thanks for help!
su
dd if=/dev/block/platform/15540000.dwmmc0/by-name/CACHE of=/sdcard/cache.img
su
dd if=/dev/block/platform/15540000.dwmmc0/by-name/RECOVERY of=/sdcard/recovery.img
su
dd if=/dev/block/platform/15540000.dwmmc0/by-name/ABOOT of=/sdcard/aboot.mbn

I download from sammobile the new firmware and use odin to flash it to get it back

Bricked by flashing "nexus 6" firmware

SO i was doing a factory restore from nexus rootkit - i must have forgotten and let it use the nexus 6 files -- it did a reboot after some flashing but never booted - it's dead aside from having access to the reserve boot loader, i have access to nothing else. I saw a similar post of someone flashing nexus 4 firmware on accident and he fixed it this way, but i think the command lines must be different since his command lines were using nexus 4 directories
here is the post i speak of http://forum.xda-developers.com/google-nexus-5/general/bootloader-bootloader-nexus-5-t2746343
plz help

zmpoutsas get a new one

Another victim of toolkits. If you have access to the secondary bootloader why not just use it to fastboot a factory image?

wangdaning said:
Another victim of toolkits. If you have access to the secondary bootloader why not just use it to fastboot a factory image?
Click to expand...
Click to collapse
Thanks ,, so i tried flashing stock firmware from secondary boot loader, and after flashing bootloader, CMD says rebooting into bootloader, and nothing happing, it just turns off and doesnt reboot
here is a screen shot
http://imgur.com/UjxP13l

Maybe try erasing bootloader and then flashing it.
Code:
fastboot erase bootloader
fastboot flash bootloader [bootloader.img]
This might brick (by brick I mean not loading the OS) it more, but I would try it if it was me. I am a little crazy though

Can you boot it up using power +volume down at all?
Sent from my SHIELD Tablet using Tapatalk

You could try doing the dd command (what he is using would be the same for you, he is on the N5), but then you would need a custom recovery to run the commands in the first place. Best bet is to simply flash the bootloader in fastboot. If you don't know how to do that then learn in the thread in general that tells you how to.
---------- Post added at 06:18 PM ---------- Previous post was at 06:09 PM ----------
Just realizing the OP might have meant the phone can no longer boot at all.
Keep up posted please, it might help others.

If you can somehow boot a custom recovery like TWRP from the backup bootloader, then you may be able to fix it. (I say "may" because I'm not sure if flashing the N6 files completely overwrote the partition table.)
Try and boot TWRP by downloading the N5 version of TWRP and rename it twrp.img, boot into the backup bootloader, plug into your PC and type: fastboot boot twrp.img
If that works, then type the following commands:
Code:
dd if=/dev/block/mmcblk0p11 of=/dev/block/mmcblk0p6
dd if=/dev/block/mmcblk0p10 of=/dev/block/mmcblk0p3
dd if=/dev/block/mmcblk0p9 of=/dev/block/mmcblk0p4
dd if=/dev/block/mmcblk0p8 of=/dev/block/mmcblk0p2
Then reboot.

Recovery boot loop which runs OpenRecoveryScript that then reboots device

Hello,
I'm trying to recover from a bad flash that left my tf101 in a scripted recovery boot loop. Trying to start the device results in the tablet booting to recovery and then running an OpenRecoveryScript which formats cache and wipes data w/o wiping /data/media and then reboots. This reboot cycle continues as it doesn't reboot to system but to recovery again and repeats itself. I'm unable to get into APX mode. I am able to see the device with ADB when it's in TWRP recovery (v2.8.1.1) for a short time and run commands from there before it reboots. The commands I've tried are "dd if=/sdcard/signed_twrp-2.8.1.1_tf101.zip of=/dev/block/mmcblk0p4" and "echo boot | dd of=/dev/block/mmcblk0p3 bs=1 seek=0" neither of which have helped. Does anyone know the command to clear this OpenRecoveryScript from memory and get me out of this boot loop?
Thanks!

How to backup system (critical partitions, nandroid) without custom recovery

Since we don't have a custom recovery for the 8T yet how would I go about backing up my full system so I can tryout one of the custom roms? Would you use the dd command with the semi working TWRP we have? And if so what partitions should I back up if I wanted to come back to the original system without having to redownload and reset up everything. I'm not totally illiterate and have a basic knowledge and know how to use commands in adb and fastboot. Thanks!

What I'd use is, go download the LineageOS Recovery.img from the LOS thread, boot that and use dd after turning on ADB. It works the same as the semi-broken TWRP, but you can actually see what's on the screen. The boot command is "fastboot boot recovery.img" and the dd commands are scattered around the forums.

card13 said:
What I'd use is, go download the LineageOS Recovery.img from the LOS thread, boot that and use dd after turning on ADB. It works the same as the semi-broken TWRP, but you can actually see what's on the screen. The boot command is "fastboot boot recovery.img" and the dd commands are scattered around the forums.
Click to expand...
Click to collapse
Once I do the dd's it's basically like a nandroid, just without the convenience of doing it all in one shot correct?

Basically whatever partitions I need to flash for another rom, If I wanted to go back I would just flash my originals back one by one? For ex. If I do this for lineage:
$ adb reboot bootloader
$ fastboot -w (this will wipe your data)
$ fastboot flash recovery recovery.img
$ fastboot reboot fastboot
$ fastboot erase scratch (this is safe to fail as scratch is only created upon adb remount)
$ fastboot flash boot boot.img
$ fastboot flash dtbo dtbo.img
$ fastboot flash system system.img
$ fastboot flash system_ext system_ext.img
$ fastboot flash product product.img
$ fastboot flash vbmeta vbmeta.img
$ fastboot flash vbmeta_system vbmeta_system.img
$ fastboot reboot
I would just flash my dd originals in the same order? And if I'm currently in slot "a" do i flash on slot "b" then set "b" active?