Database Develop

Transfert file with ADB

Hi so i flashed the google edition rom and it kept bootlooping, so i went to recovery and wiped everything but it wiped also the ROM file from the sd card now im left with nothing to flash and only recovery i think i have to transfert the file trough ADB if so can anyone give me a tutorial ? i tried adb but there is no devices listed :'( i think its debug mode it wasnt enabled.

JadeAmineHa said:
Hi so i flashed the google edition rom and it kept bootlooping, so i went to recovery and wiped everything but it wiped also the ROM file from the sd card now im left with nothing to flash and only recovery i think i have to transfert the file trough ADB if so can anyone give me a tutorial ? i tried adb but there is no devices listed :'( i think its debug mode it wasnt enabled.
Click to expand...
Click to collapse
USB debugging doesnt matter in custom recovery.
adb push <name of ROM>.zip /data/media/0/
or
adb sideload <name of ROM>.zip
you can always try googling, and come up with a few tutorials:
http://forum.xda-developers.com/showthread.php?t=2317986
http://android-revolution-hd.blogspot.com/2013/12/ow-to-use-adb-sideload.html
http://android-revolution-hd.blogspot.com/2013/12/how-to-copy-rom-zip.html
etc.

This shows device not found when i use adb devices there is nothing

JadeAmineHa said:
This shows device not found when i use adb devices there is nothing
Click to expand...
Click to collapse
Open Device Manager do you see something like:
{
"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"
}
if yes, please go to my guide and check FAQ #2.

nkk71 said:
Open Device Manager do you see something like:
if yes, please go to my guide and check FAQ #2.
Click to expand...
Click to collapse
This is what i see sync manager is installed i tried the fastboot command to get token for boatload unlock and it works but adb is not working, Plase help me i'm stuck :crying: and just to mention that im in bootloader in fastboot usb mode ??

JadeAmineHa said:
This is what i see sync manager is installed i tried the fastboot command to get token for boatload unlock and it works but adb is not working, Plase help me i'm stuck :crying:
Click to expand...
Click to collapse
like i said, just go to my guide and check FAQ #2 (in post #1), http://forum.xda-developers.com/showthread.php?t=2541082
has all the instructions, pictures, etc.

[Q] help Reverting back 2.3

I have a serious problem, I installed the B133 and now the update and has left me a window constantly open
"Sorry, Unfortunaly the process com.android.phone has stopped." and do not let me do anything
I already restored but I get the fine not to the cust, any ideas?
how the Reverting back 2.3

I got the same problem and I can't go back to 2.3,pls someone help us :/

GuyS
Try to flash 2.3 recovery and dload it..

How do I flash it?I don't understand how because of huawei that is too complicated..

You need adb tools, google how to install them and enable USB debugging. After installing put the recovery image into the adb folder and type
cd c:/[position of the adb folder]
adb devices
adb reboot bootloader
Fastboot flash recovery recovery[name of recovery].img
Fastboot reboot

The problem is that I simply can't do anything when my phone is on!I only get a message that says "unfortunately com.android.phone has stopped" so I can't go to the settings and enable the usb debug mode

Boot the phone pressing volume down and power let's you directly get into the bootloader.. So just use the two Fastboot orders

So,I'm on the bootloader..Now when I try to open fastboot on my pc,only a black tab appears and disappears after a sec,is that normal?

Gaudhier said:
So,I'm on the bootloader..Now when I try to open fastboot on my pc,only a black tab appears and disappears after a sec,is that normal?
Click to expand...
Click to collapse
downl this https://www.sendspace.com/file/uhv7n4
u need to get 2.3 recovery from somewhere I dont have it.. put it in there in folder and flash it there is command first one..
if u want u can force 2.3 ROM via adb .. with second command

I think I have a recovery from huaweiupdateextractor..
This is what I get,and it seems like fastboot doesn't recongnize my phone..
View attachment 3078581

Gaudhier said:
I think I have a recovery from huaweiupdateextractor..
This is what I get,and it seems like fastboot doesn't recongnize my phone..
View attachment 3078581
Click to expand...
Click to collapse
u need to be in bootloader.. and those your typed commands are nonsense .. type ; fastboot flash recovery recovery.img (when u copy your 2.3 extracted ..

Edit : Sorry, nonsense. Didn't saw post above

This is what i get.. View attachment 3078641
And by bootloader you mean the system recovery?Where I can do a factory reset?

Type: Fastboot flash recovery recovery.img
Then you are able to flash another firmware or to do a Factory reset

I typed it several times,but I don't understand why it always shows "cannot determine image filename for recovery.img" like on the screenshot I posted earlier,I don't understand because I moved the recovery into the ADB folder
edit:It worked when I deleted the second adb folder I had earlier..But now the thing is that it stays on "waiting for device" even if I'm in recovery mode

You wrote a couple of things, but not those four words...??!
---------- Post added at 07:40 PM ---------- Previous post was at 07:33 PM ----------
I think I mentioned the mistake. You need administrator rights for this procedure, it looks like if you run cmd as a normal user..?

l3Nni said:
You wrote a couple of things, but not those four words...??!
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"
}
This time I wrote the whole thing,but it still says "waiting for device"
And well I run it with administrator rights but it's still waiting for device :/

I added something to my last post.. Tried as admin?

l3Nni said:
I added something to my last post.. Tried as admin?
Click to expand...
Click to collapse
I'm already running it as admin

[GUIDE] How to get back the stock kernel of Nexus 5 (LMY47I)

Hi everybody,
This is my second post at XDA and as an answer to my first post (List of Lollipop 5.1 custom kernels for the Nexus 5) This post guides you how get back the stock kernel (LMY47I).
Always remember: You flash at your own risk! This post is only for the Lollipop build LMY47I!
There are two ways to get the stock kernel back, the first with a custom recovery like TWRP or CWM and the second with FASTBOOT (UNLOCKED BOOTLOADER is imortant)
1. Download the STOCK-KERNEL.ZIP in the attachments and extract it (for example with WINRAR or 7-ZIP). Then you have two files. The only one you need is the Kernel.zip file! Copy it to your phone, then switch to the custom recovery navigate to the Kernel.zip file and flash it. Now reboot the phone. The stock kernel was succesfully flashed.
2. Download the STOCK-KERNEL.ZIP in the attachments and extract it (for example with WINRAR or 7-ZIP). Then you have two files. The only one you need is the boot.img! If you haven't downloaded the Android SDK yet download it now! Switch to folder where you installed the SDK and navigate to "platform-tools". Copy the boot.img file into it. Now reboot your phone into FASTBOOT (Bootloader) with POWER Button + VOLUME DOWN and connect your phone to your PC wait until the drivers are installed if you get an error install the latest Google drivers. Open CMD navigate to "platform-tools" and type: "fastboot flash boot boot.img". Reboot your Phone and disconnect the USB-Cable. The stock kernel was succesfully flashed.

Error
Can't flash the zip, says "Unable to execute"

falcon.prj said:
Can't flash the zip, says "Unable to execute"
Click to expand...
Click to collapse
What is the name of the .zip that you tried to flash?

some custom kernels also modify/replace other files in the system partition, so is flashing just boot.img enough to return to stock kernel then?

Wakamatsu said:
What is the name of the .zip that you tried to flash?
Click to expand...
Click to collapse
Kernel.zip
And the problem was with TWRP, sorry
and thanks!

iamelton said:
some custom kernels also modify/replace other files in the system partition, so is flashing just boot.img enough to return to stock kernel then?
Click to expand...
Click to collapse
Nope. So this thread is kinda pointless. You need to reflash your rom after hellscore, code blue, elementalx and probably franco (not used franco since kitkat)
From hells thread -
{
"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 via tapatalk from my cataclysm'd Lollipooop Nexus 5

Not booting: Stock recovery but root

I´ve got root access on my device but i only have got the stock recovery of android 4.3. I am able to push an twrp recovery image to the tmp partition. Now my question is if i can flash the recovery by "dd if=/tmp/recovery.img of=/dev/????". Which partition is the recovery partition?
Thank you
Edit: I did cat /tmp/recovery.img >/dev/block/mmcblk0p1 and now there is a red string when i try to enter the recovery

@Simon_29
You didn't enter proper commands, Check attachment follow space and symbols.
-Place recovery.img in internal storage
-Download android emulator from playstore
-grant su access
-Type codes from attachment
-change recovery263 with current recovery name
That's it.
NOTE on't type adb shell if you're using terminal in phone.

Salman Al-Badgail said:
@Simon_29
You didn't enter proper commands, Check attachment follow space and symbols.
-Place recovery.img in internal storage
-Download android emulator from playstore
-grant su access
-Type codes from attachment
-change recovery263 with current recovery name
That's it.
NOTE on't type adb shell if you're using terminal in phone.
Click to expand...
Click to collapse
I wasnt able to boot the device... As I told i bricked the recovery. Now i tried to flash stock firmware with this tutorial https://forum.xda-developers.com/showpost.php?p=38838927&postcount=7 . I cant see the pictures so i dont know which i have to select. I tried it nevertheless but i got the error which you can see on the attached picture... Is there any other tutorial for flashing the stock firmware?

Why i am unable to see pictures on xda???

Salman Al-Badgail said:
@Simon_29
You didn't enter proper commands, Check attachment follow space and symbols.
-Place recovery.img in internal storage
-Download android emulator from playstore
-grant su access
-Type codes from attachment
-change recovery263 with current recovery name
That's it.
NOTE on't type adb shell if you're using terminal in phone.
Click to expand...
Click to collapse
Edit: Fixed it I went back to stock rom.
The clockwork mod install app for the 4x hd was causing this. I now used the twrp manager and even it said that it failed it worked for me. Thanks for your post anyway and that you could solve the error of xda

Simon_29 said:
Edit: Fixed it
Click to expand...
Click to collapse
Great to see that, I am having problem in attachments I already informed in xda tech dept hope they will fix it soon.
This was the image I tried to attached in my above post. You can edit your title as
[SOLVED] Not booting: Stock recovery but root as this might help someone who need helps and can follow instructions.
{
"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

Any hope for me?

I have nothing but bootloader. No system. No recovery. I've attached a screenshot. Do I have any hope?
{
"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"
}

You should be fine, because your device is unlocked. The only way you likely would have screwed yourself is if the OEM Unlocking toggle in Developer Options within Android was turned off.
EDIT: Using Fastboot you should be able to flash TWRP, which will give you your recovery. From there, flash a ROM and you should be good.

spastico said:
I have nothing but bootloader. No system. No recovery. I've attached a screenshot. Do I have any hope?
Click to expand...
Click to collapse
Go here DL the latest shamu factory image and follow the instructions. It will delete everything though.

Thanks guys. I'll let you know how it goes.
I'll be using a Mac.

Still struggling, but made a little progress.
I'm using a mac with terminal.
I don't know the terminal commands, but searching around the forums By doing this: ./fastboot boot twrp.img I now have twrp recovery working. But I still can't figure out how to flash.
Browsing around my nexus using twrp, it looks like I have no system partition.
Any more advice?

Woohoo!
Reading these forums, I figured out how to sideload the rom using ./adp with twrp sideload adb.
Back up and running.
All of this started while I was trying to switch from SuperSU to Magisk.
I still want to move to Magisk, but I obviously need to do some more reading.

For some reason I couldn't get the factory images to sideload. It kept saying invalid zip. So I sideloaded PureNexus.
All is good, but I just don't have a radio.
Off to do more reading.

Got a radio and posting from my Nexus.
Thanks again guys.
./fastboot flash radio radio.img

Great read, seeing the progress reported on like that. Thanks for updating.
If you ever want to move to the stock factory image, you don't sideload it. You'll need to run the flash-all.bat file (edit it and remove the -w flag to keep your data) or unpack it and use fastboot to flash each separate image (skip userdata and if you want to have TWRP installed to your device also recovery).
And if you have further issues with getting Magisk running, check out the Magisk guide.

@spastico @Didgeridoohan
To sideload a stock image on an N6, you have to use a full OTA image as compared to using fastboot flash (or the flashall.bat) with a Google factory image.
The instructions for each are well written right on the linked page from google.
@spastico, you commented that with TWRP booted, you didn't see a system partition. System is not mounted in TWRP, but you can manually mount it if you choose. As you discovered, mounting isn't necessary to flash an image.
"Good judgment comes from experience, and a lot of that comes from bad judgment." - Will Rogers

Awesome! I keep forgetting about those full OTAs. They weren't around when I used stock factory images on my Nexus...

Thanks for the additional advice.