Database Users

Question about changing Recovery

Hi, I have a friend who currently has
Android Recovery System <2e> on his droid. Wanting to know if there's a way to change from that to Amons? Also, while using the <2e> any zip he tries to install comes up with the error E: Can't open /cache/recovery/command
If he scrolls down to Apply sdcard: update.zip he gets:
--Install from sdcard...
Finding update package...
Opening update package...
Verifying update package...
E:failed to open /sdcard/update.zip (No such file or directory)
E:signature verification fialed
Installation aborted.
This happens when trying to open .zip's such as Evil Eris 2.0 or any other zip. I have Amon's recovery and these zips work fine for me.
Any and all help is appreciated. Thanks in advance.

was anything changed within the .zip files?... because if so that will cause it. Also i know if you rename the .zip file you will also recieve the problem because they signed with that specific name. Otherwise, i suggest deleting it from you SD and downloading the .zip again and do a wipe data/dalvik and reflash. But remember to do a nand backup! Lemme know what you get....

No files/names have been changed. If I could get Amon's recovery I could mod his phone for him. I have Amon's and do not have this issue. It is prbably something I am not doing due to being unfamiliar with the recovery he has. Basicaly I think all I really need is a way to get his recovery to read Amon's and I'm good.

andrew8806 said:
was anything changed within the .zip files?... because if so that will cause it. Also i know if you rename the .zip file you will also recieve the problem because they signed with that specific name. Otherwise, i suggest deleting it from you SD and downloading the .zip again and do a wipe data/dalvik and reflash. But remember to do a nand backup! Lemme know what you get....
Click to expand...
Click to collapse
Are you certain about that, or is that unique to that specific recovery menu?
I rename my update.zip's and ROM's after they've been signed and don't run into issues.

If his phone is rooted just download rom manager from the market, open it, scroll all the way to the bottom and hit flash alternative recovery.
That should do it.

.mak said:
Are you certain about that, or is that unique to that specific recovery menu?
I rename my update.zip's and ROM's after they've been signed and don't run into issues.
Click to expand...
Click to collapse
I change the name of update.zip and it always fails to verify.

Cant flash another recovery image!!!

It used to work along time ago, this is my new refurb that i rooted a few days ago, im on the 1.5.2 recovery image and im trying to flash the new 1.6 but i dont what the crap im doing wrong. i keep getting error messages i used to be able to do this in 10 seconds. i already have the image on the root of my card can anyone help.
Plus those bastards sent me a refurb that has dead pixels that are white in the blk screen wtf sprint, thats pure whack customer service.
EDIT: problem solved, i was trying this whole time to flash another recovery inside recovery, i actually left the phone on and pushed the recovery lol no more ghanja.

see the # symbol when you enter teh shell? that means you have root already and su isn't necessary. Also try unplugging then plugging back in, the phone from the usb. The file not found error probably means that the sd card is mounted. do an ls from /sdcard to make sure

Also try "adb mount" over "mount -a".

DISABLE usb debugging.
i know, its the little things we overlook. i just did this last night and forgot to disable it.

i did and its still not working.........i dont understand, let me upload another pic. and i already tried adb mount and fastboot still no luck

i kept getting these errors what i did and found easiest with no errors is save the recovery in the sd card. download terminal emulator then in terminal emulator su then enter
then type flash_image recovery /sdcard/nameofimage.img
someone please make sure my prompts are right as i hadn't done it in awhile.

I am trying to do the exact same thing and getting the exact same errors. The file is definitely on the sd card, I am typing the name correct, and USB debugging is off.
Anyone have any other ideas or ways to update to the newest recovery image?

Maitiu said:
I am trying to do the exact same thing and getting the exact same errors. The file is definitely on the sd card, I am typing the name correct, and USB debugging is off.
Anyone have any other ideas or ways to update to the newest recovery image?
Click to expand...
Click to collapse
hahaha dude it used to work perfectly, i been trying and trying for the past couple of hours. (scratching head)

Demoyo23 said:
hahaha dude it used to work perfectly, i been trying and trying for the past couple of hours. (scratching head)
Click to expand...
Click to collapse
you try using the terminal emulator method directly on the phone? only way i can get to work and works everytime.

I'm working on that now, but I tried that a few days ago and got different errors, I'll post what the specific error was when I get there in a few minutes. For some reason Superuser Permissions is force closing right now.
Yeah even from the terminal emulator, I get a "not found" error.

I just updated today from RA1.5.2 to RA1.6.2. I used the Recovery Flasher to update to the newer version as that is what I had originally used to get 1.5.2 installed.
These were original instructions from theunlockr .com:
7. Save both the Recovery-RA-HEROC-v1.5.2.img and the FlashRec.apk to your computer, then copy them both to your SD card (do NOT put them inside any folders on the SD card, just put them on the SD card itself).
8. Unplug the phone from the computer once they are downloaded to the SD card.
8. Goto the Market and download Linda File Manager or any file manager program if you do not already have one.
9. Open the file manager and goto SDCard and then find the FlashRec apk file and click it. If asked tell it to use Package Installer to open it. It should automatically install the apk.
10. Open the FlashRec program and click on Backup Recovery Image and wait for it to finish.
11. Once done, click on the empty text box in the FlashRec program and type (again remember we have replaced the recovery image from the one in the video so type what is written here, NOT what is written in the video!):
/sdcard/recovery-RA-heroc-v1.5.2.img
Then click on the Flash Custom RecoveryImage button and wait for it to finish.

Just barely.

That's still not working flashrec won't back up it keeps saying failed. And it won't flash a custom img. This refurb is cursed I had no problem doing it all on my original.
-------------------------------------
Sent via the XDA Tapatalk App

Demoyo23 said:
It used to work along time ago, this is my new refurb that i rooted a few days ago, im on the 1.5.2 recovery image and im trying to flash the new 1.6 but i dont what the crap im doing wrong. i keep getting error messages i used to be able to do this in 10 seconds. i already have the image on the root of my card can anyone help.
Plus those bastards sent me a refurb that has dead pixels that are white in the blk screen wtf sprint, thats pure whack customer service..
Click to expand...
Click to collapse
Type 'adb devices' in... Whenever I see the '/' before the '#' it means that it isn't recognizing my phone.

Just do it through adb. I did mine through adb the 1st, 2nd and 3rd time. After looking at the dirwctiona, I think it might be easier and should work.
-------------------------------------
Sent via the XDA Tapatalk App

Make sure the phone is connected as charge only, once it is type
ls /sdcard
AND PASTE THE RESULTS HERE
It sounds like you don't have the sdcard mounted or if you do you may be typing the file wrong compared to what is on the sdcard.
Don't panic, this had nothing to do worth the phone being refurbished, it is only a simple file not found error that once you fun that command can easily be solved.

liquidtenmillion said:
Make sure the phone is connected as charge only, once it is type
ls /sdcard
AND PASTE THE RESULTS HERE
It sounds like you don't have the sdcard mounted or if you do you may be typing the file wrong compared to what is on the sdcard.
Don't panic, this had nothing to do worth the phone being refurbished, it is only a simple file not found error that once you fun that command can easily be solved.
Click to expand...
Click to collapse
it keeps telling me permission denied lol

Type in
"adb shell" then
"ls /sdcard"
Without the quotes exactly as I typed them one at a time and paste the results.

dirkydirk23 said:
i did and its still not working.........i dont understand, let me upload another pic. and i already tried adb mount and fastboot still no luck
Click to expand...
Click to collapse
did you try fastboot boot recovery [dir on your computer]

Do a search for adb shell recovery. It should tell you how to do it. You are going to have to mount the system before doing anything else...and also change the recovery image to something Like recovery.ing as it is easier to type and less likely to be mis-typed
-------------------------------------
Sent via the XDA Tapatalk App

Problem Rooting - Yes another one

I have the espresso mytouch 3g slide. I have tried rooting this everyway but the correct one and that is why I am asking for help. I have spend hours on this and I am sure some peeps can appreciate this. I have tried on win7, win xp, and linux. All the same problem. My device won't be seen after I go into recovery. I have tried the process in Unloker, and by eugene here at ada and wess and the bible and everyplace I can. I have tried 3 different sd cards a 512 meg a 4 gig and the 8 gig that came with the phone. I have formatted them all in the phone so they were clean. I have degugging on and charge only selected. No matter where I go or what I use in the first steps all is great.
List of devices attached
my serial number
power off Now I do the Hboot by d/vol and power and I have tried this all different bu unplugging before it looks for images and then plug in back in after andall combo's. so now I vol/down and then power and I am in recovery. I have a picture of a phone with a red triangle with a ! mark in the triangle. I press u/vol and power and I am n recovery. At the top it say Anroid system recovery <2e> so I know I am in the right place. Now at this point I have looped everyway I have read and I have read a lot. If I go to my prompt it gives me,
List of attached devices < -- and that is all
Back to thescreen of my phone at the bottom I have a yellow - E:\Can't open /cache/recovery/command. If I try to push the undate zip anyway or from the terminal. it will
find
open
Verifiy the update package but then get
e:\failed to open /sdcard/update.zip (no such file or directory)
E:\signature verification failed installation aborted
All the same endings with or with PDAnet or root.zip and simpleroot. Any light that someone can share would be appreciated

Same problem
I have the same problem as you do. I look around and i coulnd find anything. I hope someone out there know.

Ok first off the loop.bat file supposed to be run prior to selecting the recovery option in hboot
Second after you see the device offline repeating stop the loop batch job then unplug the usb from your phone and plug it back in, but only if you get "device offline" repeating otherwise repeat from hboot.
Third the rooting method for the slide is called "ota spoofing" for a reason. In the root.zip package you have three files "loop.bat, ota.zip, and update.zip" the update.zip is the file that actually contains clockworkmod recovery. However you need the ota.zip file for signature verification. And the loop file for the above purpose.
The ota.zip file needs to be on the root of your sdcard but named "update". The android recovery will only ready files named update and in the .zip archive format.
Now if you have all this and your reading your device in recovery you can type in your command prompt "adb push update.zip /sdcard" BUT DO NOT HIT RETURN YET.
Once you have that pickup your device scroll to "apply sdcard:update.zip" hit power count to 2 or 3 then hit return on your keyboard to send the actual update.zip file to the devices sdcard which will then load into clockwork recovery.
Sent from my T-Mobile myTouch 3G Slide using XDA App

Armyjon88 said:
Ok first off the loop.bat file supposed to be run prior to selecting the recovery option in hboot
Second after you see the device offline repeating stop the loop batch job then unplug the usb from your phone and plug it back in, but only if you get "device offline" repeating otherwise repeat from hboot.
Third the rooting method for the slide is called "ota spoofing" for a reason. In the root.zip package you have three files "loop.bat, ota.zip, and update.zip" the update.zip is the file that actually contains clockworkmod recovery. However you need the ota.zip file for signature verification. And the loop file for the above purpose.
The ota.zip file needs to be on the root of your sdcard but named "update". The android recovery will only ready files named update and in the .zip archive format.
Now if you have all this and your reading your device in recovery you can type in your command prompt "adb push update.zip /sdcard" BUT DO NOT HIT RETURN YET.
Once you have that pickup your device scroll to "apply sdcard:update.zip" hit power count to 2 or 3 then hit return on your keyboard to send the actual update.zip file to the devices sdcard which will then load into clockwork recovery.
Sent from my T-Mobile myTouch 3G Slide using XDA App
Click to expand...
Click to collapse
Thank you. I have no idea why someone didn't say to rename the file but that must have been it since that was the only thing I did differently. 2 days of reading and swearing at my phone and I was so close. Well others Espresso users are having the same problem so hopefully this will help them as well. Many thanks

USA 1.141.07 update fix with. .img's

Crsdr37 said:
Alright Guys in the USA. I will be posting the .img files to fix your device or update your device to 1.141.07 if you have either used the chinese update fix or some other various fix that left you with a different boot image. The instructions are simple.
1. Connect your tablet to the computer via USB. Put the boot.img and the system.img on your SD Card. Also put the Update.zip then use a file explorer to move the update.zip to the root of your SD card. Which is external SD. If you use Astro. (Alternatively you can just take your SD card out and put it in your computer to put the update.zip.)
2. You need to first push the boot.img
-Open ADB type su then hit enter. (your device will prompt for superuser you must select allow) Then enter the command below.
dd if=/sdcard/boot.img of=/dev/block/mmcblk0p2 (hit Enter)
3. Then push the system.img
dd if=/sdcard/system.img of=/dev/block/mmcblk0p3
4. Force shutdown your device when those finish (as your screen may not turn on.)Then hold volume - and the power button "until the green android comes up very important do not let them go just because the device turns on" to start the update.zip. Let it finish (Your device will reboot when it completes.
5. Enjoy the fact your device is back to stock and you can now update when future updates release.
To push the files you will need adb shell. If you dont know what that is look it up, It is part of the android development kit. Second these 2 commands will push the files to their proper mount block. You must push the boot.img first then the system.img These files are for the USA update 1.141.07
http://www.megaupload.com/?d=TNDCAYC8 - System.img -MD5-2b4e2fea567ac883bb483fc96b1fdc9d
http://www.mediafire.com/?7b5llkk8bnmnd23 -Update.zip
http://www.mediafire.com/?3qahjh3twi6jc9t -Boot.img -MD5-4477d6739dd1e3b3ba1dbf94be7fe8f0
Here are 2 Mirrors To download the boot.img you will need to download both as the uploader made it a 2 part file making it easier for some countries to download. Give thanks yo ardatdat if these came in handy.
http://www.zshare.net/download/91195486183633a0/
http://www.zshare.net/download/9119547812fdf5fa/
I will check periodically on this thread if anyone has questions or needs Help. Guve a huge shout out to deckofficer54 as he is a co-worker and friend that dumped these files for me when I screwed my system up.
Click to expand...
Click to collapse
** Alright guys I am just posting this link for when you just do the update.zip because you are already on 1.104.05_COM_GEN1 and you have a different kernel then the update.zip, What will happen is when you reboot the tablet from just doing the update.zip you may have WIFI error. These files should resolve that issue. Once again they are only if you have WIFI Error on reboot. To install these you will need some type of file explorer that has rw access to the file system. I rec. Root Explorer. To install these follow these instructions.
1. Copy both modules to your SD card does not matter where.
2. With your File Explorer/Manager Copy both of these files. (Root Explorer will let you multi-select if you hit the menu button.)
3. Navigate to System/Lib/Modules.
4. **This step is very important- You must Mount your System for RW access. If you don't they will not copy. Once you have RW just hit the paste button and then reboot your device.
5. **This step is for anyone still having wifi error after reboot. (Stop being lazy lol and just do all the steps. From the top by mounting the boot.img and system.img that way your device is 100% stock there for no checksum issues.
http://forum.xda-developers.com/attachment.php?attachmentid=601473&d=1305842073 - This is the wifi modules Download Link.
Thank you thor2002ro for posting these on your kernel modules thread. Which is found here for anyone having any other issues.
http://forum.xda-developers.com/showthread.php?t=1058713
Happy Updating
​
Alright guys here is the list of supporters thus far for the unbricking and or updating of your tablet. If I missed someone let me know.
Supporters:
Euclid's Brother -Awesome tool to flash the images Making your lives easier one click at a time. If you want an easier way download these images and use this app https://market.android.com/details?id=com.interphaze.Acer_ROM_Flasher
bhageman -Donation
aerichards1977 -Donation
Sent from my PC36100 using XDA Premium App

thanks so much for this. to verify my build number is 1.141.07_COM_GEN1 is that right?

Success! This worked like a charm! I didn't have to use the recovery img I just used the update.zip.
After update:
Kernel: g9b3ce2b
Build: Acer_A500_1.141.07_COM_GEN1
Good work and thanks!
edit: Actually I guess I do have one issue right now. After the update my wifi stopped working. When I go to the wifi settings I see "Error" under Wi-Fi and the check box is grayed out so that it can't be clicked. Any help?

Had a German 1.112 build i guess, bricked it and revocered it with Acer_A500_1.122.01_EMEA_GEN5. Used boot and system image and then updated and it really works!!! Thank you very very very much!!!
EDIT1: I even not lost my settings and can set the language to German too!!
EDIT2: Root gone (as expected), used Gingerbreak (tab version) and everything works fine.

phone.ds said:
Had a German 1.112 build i guess, bricked it and revocered it with Acer_A500_1.122.01_EMEA_GEN5. Used boot and system image and then updated and it really works!!! Thank you very very very much!!!
Click to expand...
Click to collapse
Your Very Welcome. Took me some time to get all the files but this **** works like a frickin charm. I wish it wasnt such a pain in the ass but hey its fixed.

ryutsuke said:
Success! This worked like a charm! I didn't have to use the recovery img I just used the update.zip.
After update:
Kernel: g9b3ce2b
Build: Acer_A500_1.141.07_COM_GEN1
Good work and thanks!
edit: Actually I guess I do have one issue right now. After the update my wifi stopped working. When I go to the wifi settings I see "Error" under Wi-Fi and the check box is grayed out so that it can't be clicked. Any help?
Click to expand...
Click to collapse
well the only thing I can think of it either the lib modules for wifi are messed up in which case I can post a link with them or the kernel is different. I would use the 2 .img that I posted then use the update zip. That way the images replace your kernel which is always the root cause of wifi errors.

here is a link to the wifi lib modules. You need to use something like root explorer. To mount the system as rw. Then navigate to system/lib/modules and copy those two files into there with the system mounted as rw. Reboot and see if it fixes the issue!!
http://www.megaupload.com/?d=OKU671AP

futty said:
thanks so much for this. to verify my build number is 1.141.07_COM_GEN1 is that right?
Click to expand...
Click to collapse
Yes you are now stock and able to update when they release 3.1

dont we need to flash flexrom.img to be 100% stock?

The flexrom was flashed with the update zip
Sent from my A500 using XDA Premium App

confirmed working as well.

Crsdr37 said:
here is a link to the wifi lib modules. You need to use something like root explorer. To mount the system as rw. Then navigate to system/lib/modules and copy those two files into there with the system mounted as rw. Reboot and see if it fixes the issue!!
Click to expand...
Click to collapse
Am I missing something or did you maybe forget the link =P

Ah **** lol give me 1 second
http://www.megaupload.com/?d=OKU671AP
Sent from my A500 using XDA Premium App

Did those libs help at all?a like I said if they don't the only fix I I now would be to go back to the german or chinese update then flash both. Img then update.
Sent from my A500 using XDA Premium App

Image updates
Maybe some file corruption?! Loaded per the directions and on boot got error:
"Secure Boot Image LNX checksum fail"
Going back to the Chinese Rom.

You get that only when do don't do all three'. Once you reboot after pushing the 2 images. You have to hold down the volume - and the power button it will then run the update zip to complete.
Sent from my A500 using XDA Premium App

Crsdr37 said:
Yes you are now stock and able to update when they release 3.1
Click to expand...
Click to collapse
thanks so much again. you are a god i bet you helped millions by doing this

That was my intentions I came from the evo forums. Everybody there helps each other. Im just hoping people here pick it up and start helping when people have questions.
Sent from my A500 using XDA Premium App

ryutsuke said:
Success! This worked like a charm! I didn't have to use the recovery img I just used the update.zip.
After update:
Kernel: g9b3ce2b
Build: Acer_A500_1.141.07_COM_GEN1
Good work and thanks!
edit: Actually I guess I do have one issue right now. After the update my wifi stopped working. When I go to the wifi settings I see "Error" under Wi-Fi and the check box is grayed out so that it can't be clicked. Any help?
Click to expand...
Click to collapse
Did you ever get wifi working
Sent from my A500 using XDA Premium App

tomlogan1 said:
Maybe some file corruption?! Loaded per the directions and on boot got error:
"Secure Boot Image LNX checksum fail"
Going back to the Chinese Rom.
Click to expand...
Click to collapse
Were u able to get past the checksum error?
Sent from my A500 using XDA Premium App

Can't flash KRT16S (from KRT16O)

Hi everybody
When the factory images came out, I flash my N4 with the stock factory images that we used to find here : https://developers.google.com/android/nexus/images#occamkrt16s because it is now the KRT16S build
After a few days, when the KRT16S build came out, I was proposed in my phone to update it. I downloaded it, tried to flash it but nothing worked, I'm still on KRT16O and the OTA doesn't appear anymore... Then I remembered that I flashed a mod found here : http://forum.xda-developers.com/showthread.php?t=2527525 (that's a great mod btw) so I guessed that I could reflash the undo file available on the thread, flash the ota file dl mannually (I attached it in this thread) which I did through TWRP. Then I was able to see the problem, it told me that, from what I remember, Agenda.apk was missing (I think it's diary in english, not sure) then I remembered that I manually deleted some apps I never use (diary is one of them...)
So, what's next, shall I reflash the gapps to finally update my phone
Thanks for your help :laugh:

Are you using latest TWR? I did it ok
Sent from my Nokia 3210

howard bamber said:
Are you using latest TWR? I did it ok
Sent from my Nokia 3210
Click to expand...
Click to collapse
I run the 2.6.3.3 version I guess it's the latest because I flashed it a few days ago
I installed the few missing apps that i uninstalled and Calendar didn't create any error. This time it EmailGoogle.apk... I transformed it as a system application and I went to /system/app to change its name from com.google.android.apps.email or something to EmailGoogle.apk, didn't work... But I'm sure I'm on the way to achieve it :victory:
Here's the whole mesage :
Code:
Updating partition details...
Installing '/sdcard/Download/70f3bd408ca3d142509cd4bace2f2c7e3aa486c6.signed-occam-KRT16S-from-KRT16O.70f3bd40.zip'
Checking for MD5 file...
Skipping MD5 check : no MD5 dile found.
Verifying current system...
"/system/app/EmailGoogle.apk" has unexpected contents.
E:Error executing updater binary in zip '/sdcard/Download/70f3bd408ca3d142509cd4bace2f2c7e3aa486c6.signed-occam-KRT16S-from-KRT16O.70f3bd40.zip
Error flashing zip '/sdcard/Download/70f3bd408ca3d142509cd4bace2f2c7e3aa486c6.signed-occam-KRT16S-from-KRT16O.70f3bd40.zip'
Updating partition détails...
[CENTER][COLOR="Red"][SIZE="4"]Failed[/SIZE][/COLOR][/CENTER]

azertguigui said:
I run the 2.6.3.3 version I guess it's the latest because I flashed it a few days ago
I installed the few missing apps that i uninstalled and Calendar didn't create any error. This time it EmailGoogle.apk... I transformed it as a system application and I went to /system/app to change its name from com.google.android.apps.email or something to EmailGoogle.apk, didn't work... But I'm sure I'm on the way to achieve it :victory:
Here's the whole mesage :
Code:
Updating partition details...
Installing '/sdcard/Download/70f3bd408ca3d142509cd4bace2f2c7e3aa486c6.signed-occam-KRT16S-from-KRT16O.70f3bd40.zip'
Checking for MD5 file...
Skipping MD5 check : no MD5 dile found.
Verifying current system...
"/system/app/EmailGoogle.apk" has unexpected contents.
E:Error executing updater binary in zip '/sdcard/Download/70f3bd408ca3d142509cd4bace2f2c7e3aa486c6.signed-occam-KRT16S-from-KRT16O.70f3bd40.zip
Error flashing zip '/sdcard/Download/70f3bd408ca3d142509cd4bace2f2c7e3aa486c6.signed-occam-KRT16S-from-KRT16O.70f3bd40.zip'
Updating partition détails...
[CENTER][COLOR="Red"][SIZE="4"]Failed[/SIZE][/COLOR][/CENTER]
Click to expand...
Click to collapse
You can not install an apk in recovery. Use ES File Explorer to install the apk. In addition, to avoid the error, while you are in recovery, select "Mount" and uncheck the box "System" when flashing a zip file.

taodan said:
You can not install an apk in recovery. Use ES File Explorer to install the apk. In addition, to avoid the error, while you are in recovery, select "Mount" and uncheck the box "System" when flashing a zip file.
Click to expand...
Click to collapse
I did not installed it with TWRP, I did it by simply openning the apk while my phone is on, it installed the Email app...
But thanks anyway for the mount function, I'll give a try

azertguigui said:
I did not installed it with TWRP, I did it by simply openning the apk while my phone is on, it installed the Email app...
But thanks anyway for the mount function, I'll give a try
Click to expand...
Click to collapse
Simpler way to update without OTA package:
Download the factory image, and before running the flash-all script, open it with a text editor and change "fastboot -w update" to "fastboot update"

MameTozhio said:
Simpler way to update without OTA package:
Download the factory image, and before running the flash-all script, open it with a text editor and change "fastboot -w update" to "fastboot update"
Click to expand...
Click to collapse
You mean with the sdk? I don't know how to use it, when I flash something, it's with the recovery or the nexus root toolkit..
-From my Nexus 4-

UP

azertguigui said:
UP
Click to expand...
Click to collapse
**

azertguigui said:
UP
Click to expand...
Click to collapse
azertguigui said:
**
Click to expand...
Click to collapse
Not sure what you're trying to say here..
azertguigui said:
You mean with the sdk? I don't know how to use it, when I flash something, it's with the recovery or the nexus root toolkit..
-From my Nexus 4-
Click to expand...
Click to collapse
Try avoiding toolkits as they can lead to problems and leave you stuck with no idea what to do. Yes he is referring to the sdk. Only the platform-tools folder in the sdk is required so if you don't wanna bother downloading the complete file, just download the platform-tools from here and extract it to an appropriate location. Extract and move the Factory Image that you downloaded to your platform-tools directory. If you don't want your data to be erased, edit the flash-all script with a text editor and remove -w and save. Plug in your phone. Make sure you have the drivers installed. In the platform tools directory, press shift+right click> open command prompt here. Type adb devices. You will see "device <Serial Number>. If you don't, your drivers are faulty. Then type adb reboot bootloader. Once your phone has rebooted into bootloader, make sure that it is being detected by typing fastboot devices. You should see an output similar to adb devices. Now simply run the flash-all script and let it do its work. Reboot after flashing is completed.
Hope this helps!

try search any youtube on how to flash factory images to your device. I guess u'll find lots.
Sent from my Nexus 4 using XDA Premium 4 mobile app

Words of advice, learn how to use ADB instead of relying solely on toolkits. It's very simple actually.
Now there's a simple way to update which is sideload. Oh and btw to sideload, you still need ADB though (this is why learning ADB is VERY important to us, the N4 users). Here is a video tutorial on how to perform adb sideload. All the links are attached in his youtube video.

Ibrahim.Rahman said:
Not sure what you're trying to say here..
Click to expand...
Click to collapse
:laugh: I quoted my own UP post but it told me that my post should have at least 2 letters, so I taped the spacebar twice and it wrote this
Ibrahim.Rahman said:
Try avoiding toolkits as they can lead to problems and leave you stuck with no idea what to do. Yes he is referring to the sdk. Only the platform-tools folder in the sdk is required so if you don't wanna bother downloading the complete file, just download the platform-tools from here and extract it to an appropriate location. Extract and move the Factory Image that you downloaded to your platform-tools directory. If you don't want your data to be erased, edit the flash-all script with a text editor and remove -w and save. Plug in your phone. Make sure you have the drivers installed. In the platform tools directory, press shift+right click> open command prompt here. Type adb devices. You will see "device <Serial Number>. If you don't, your drivers are faulty. Then type adb reboot bootloader. Once your phone has rebooted into bootloader, make sure that it is being detected by typing fastboot devices. You should see an output similar to adb devices. Now simply run the flash-all script and let it do its work. Reboot after flashing is completed.
Hope this helps!
Click to expand...
Click to collapse
Thanks, I'll give a try
saifulh2304 said:
try search any youtube on how to flash factory images to your device. I guess u'll find lots.
Sent from my Nexus 4 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
arffrhn said:
Words of advice, learn how to use ADB instead of relying solely on toolkits. It's very simple actually.
Now there's a simple way to update which is sideload. Oh and btw to sideload, you still need ADB though (this is why learning ADB is VERY important to us, the N4 users). Here is a video tutorial on how to perform adb sideload. All the links are attached in his youtube video.
Click to expand...
Click to collapse
thanks guys, I'm gonna find tutorials on the web like the one you pointed to me

azertguigui said:
:laugh: I quoted my own UP post but it told me that my post should have at least 2 letters, so I taped the spacebar twice and it wrote this
Click to expand...
Click to collapse
Haha right!
Sent from my Nexus 4 using xda app-developers app