Related
After I turn on my Evo 4G, it begins the process, but sticks on the screen with the large "4G" in the center. I am rooted. I'm not sure what in the world to do. Can anyone please help? Thanks!
Use your PC to download a ROM image to restore. Install HTC sync if you don't have it (you need Sync to get the HTC USB drivers). Download and install the Android SDK from Google.
Boot into Recovery mode (pull battery, reinsert battery, hold Vol-, hold power until boots into HBoot, vol - to highlight Recovery, power to boot to recovery).
Start a command prompt window and go to the Platform-Tools folder in the SDK directory. Plug your phone, in Recovery mode, into the PC. Type "adb shell" into the PC's command prompt. If you get a $ or # prompt, you're connection is good. Type "exit."
Type "adb push [filename] /sdcard/update.zip" into the command prompt, replacing [filename] with the path to your new ROM file. This will copy your new ROM file to your SD card.
Now use the Recovery to install the new ROM. If you're using ClockWorkMod as your Recovery, the second option down is Update from SD card. Choose that, then choose "Yes - Install update.zip from the SD card" on the next menu.
This process will replace your current ROM and, if it completes successfully, should fix your problem. Although, you'll be on a non-stock ROM. Of course, there are plenty of rooted stock-ish ROMs available.
Plug
Hi, I am afraid I brick my Galaxy Nexus (Rooted)
Cause:
I think I wrongly delete some system files in Clockworkmod.
Symptoms:
1. When the mobile is turn on, only shows 'Google' logo and the 'Unlock' logo, no responds then.
2. Press Volume + and - key, I can successfully enter recovery mode.
3.Press Volume - key, I can successfully enter Download mode.
4. I do not have any Stock Rom file (or other Rom file) in the mobile memory.
Urgently need your expertise and help.
Many Thanks
(I am not an expert, so would you mind teach me step by step if you got the solution)
Thanks!!!!
So you cannot boot the phone at all past the Google splash screen? LTE or GSM?
Or does the phone boot fine, but you just can't get into ClockworkMod Recovery?
cbs2002 said:
Hi, I am afraid I brick my Galaxy Nexus (Rooted)
Cause:
I think I wrongly delete some system files in Clockworkmod.
Symptoms:
1. When the mobile is turn on, only shows 'Google' logo and the 'Unlock' logo, no responds then.
2. Press Volume + and - key, I can successfully enter recovery mode.
3.Press Volume - key, I can successfully enter Download mode.
4. I do not have any Stock Rom file (or other Rom file) in the mobile memory.
Urgently need your expertise and help.
Many Thanks
(I am not an expert, so would you mind teach me step by step if you got the solution)
Thanks!!!!
Click to expand...
Click to collapse
The key piece of information for your symptom is in this line:
1. When the mobile is turn on, only shows 'Google' logo and the 'Unlock' logo, no responds then.
The other lines do help provide background as to the other modes such as recovery and download working properly, which indicates the issue is not *serious*.
The symptom you state, where the device does not boot past the boot logo, usually means the device is not able to boot the kernel or boot past the kernel. The boot logo appears while the kernel is being loaded on the device. Generally, after the boot logo and kernel finish loading a boot animation appears which indicates the kernel has usually handed off to the Android OS to continue booting.
My approach would be to load a completely stock ROM in order to restore a working kernel and ROM to the device. I generally perform this step as a baseline to get everything back in working order.
In many instances the ROM is dependent on the kernel. Your situation requires at least a kernel to be loaded and in order to prevent any further issues, it would be best to load a ROM dependent on the kernel being loaded.
A simple way would be to grab the stock factory images from Google's site and load those back onto the device.
Another simple way would be to grab a stock ROM and flash the .zip through CWM in recovery mode.
Hope that helps!
Since you're rooted I'm going to assume you have ADB and the necessary drivers installed.
1.) Download a ROM. It doesn't have to be stock, you can choose any of the ROMs from the development section for your device. Most of the ROMs are packaged with a kernel already.
2.) Save this ROM file to the same folder where you have ADB installed.
3.) Boot your phone into CWM recovery and plug it into your computer.
4.) Use ADB to push the ROM zip file to your phone (/data/media). For example:
Code:
c:\gnex\>adb push rom.zip /data/media/rom.zip
5.) Use CWM to wipe data, cache, and davlik-cache
6.) Install zip from sdcard and flash the rom.zip.
RMarkwald said:
So you cannot boot the phone at all past the Google splash screen? LTE or GSM?
Or does the phone boot fine, but you just can't get into ClockworkMod Recovery?
Click to expand...
Click to collapse
1. I am using GSM
2. Whenever I turn on my mobile, the 'Google' and 'Unlock' logo appears and then freeze, with no more respond at all
* I definitely mess up some system files, but don't know how to restore it because my PC do not recognize my mobile.
Thanks
I am seeing more and more of these threads about "bricked" nexus's is this an issue with how new the phone is or people not following instructions properly as they are too eager to root their phones?
All else fails flash back to stock and count yourself lucky.
To silow,
Thanks for your advice, but fail
1. I put adb.exe, adbwinapi.dll and fastboot.exe (3 files) under my PC C drive (i.e. C
2. I also put a stock Rom (rename as rom.zip) under C drive (i.e. C
3. Boot phone into CWM recovery and plug it into computer.
4. Use cmd command and type c:\gnex\>adb push rom.zip /data/media/rom.zip
5. It fails , It say "Access Denied" (in Chinese, but I translate it into English here)
6. How do I use ADB (it is a ADB.exe file, When I double click it, it only flash up a few page very fast and nothing happen)
Please assist!
To Joeykrim,
I agree that
"Another simple way would be to grab a stock ROM and flash the .zip through CWM in recovery mode."
But how? (according to my symptoms)
The command I gave you was just an example. I didn't spell out the exact details because I thought that you would know how to do it considering you rooted the phone.
If you put the adb.exe and AdbWinApi.dll file in your C: drive, make sure you copy the ROM file to your C: drive too. In the follow example I'm going to use "ROM.zip" but use the name of the ROM file that you downloaded. Also I am assuming you are on Windows XP.
1.) Boot your phone into CWM recovery and then plug it in.
2.) Go to your Start Menu and choose Run. Then type in "cmd" without quotes and hit enter to open a command prompt.
3.) Enter:
Code:
cd c:\
4.) Enter the following to make sure ADB can see your phone:
Code:
adb devices
You should see something similiar to this to confirm ADB can see your device:
List of devices attached
019B756F0C018012 device
5.) Enter the following command to copy the ROM file to your phone. Remember to replace ROM.zip with whatever the name of the ROM file is:
Code:
adb push ROM.zip /data/media/ROM.zip
6.) Use CWM to wipe data, cache, and davlik-cache
7.) Install zip from sdcard and flash the rom.zip.
To Silow,
You have been very helpful, but I fail.
"You should see something similiar to this to confirm ADB can see your device:
List of devices attached"
There is NO device number shown after the phrase 'List of devices attached'
To recap:
a) Phone is already plugged in my PC, under the Clockworkmod Recovery 5.5.0.2
b) adb.exe and AdbWinApi.dll file are under C: drive directly
c) Also type cmd in 'Run', a black Dos window shown C:\windows\system32\cmd.exe
d) c:\>adb devices
List of devices attached
(But no device number show up, it cannot recognize my mobile)
Pls don't give up on me!
: )
you can't use adb from CWM, you need to enter the bootloader, then try adb or fastboot (edit: wrong!)
Sounds like your ADB USB drivers are not correctly installed. While the phone is under CWM, when you plug it in is your computer attempting to install drivers for a new device?
Download these bare ADB Interface drivers.ADB USB Drivers
Go into Device Manager on your computer and check the device list for any unknown devices or "?" devices. If you need to update those drivers by pointing them to the drivers you downloaded and extracted from that link above.
When the ADB Interface drivers are correctly installed you should see Android Phone listed under under your Device Manager when it's plugged in with CWM recovery loaded.
---------- Post added at 02:36 PM ---------- Previous post was at 02:35 PM ----------
cancerouspete said:
you can't use adb from CWM, you need to enter the bootloader, then try adb or fastboot
Click to expand...
Click to collapse
You CAN use ADB with CWM. That's one of the reasons why CWM is so awesome.
silow said:
You CAN use ADB with CWM. That's one of the reasons why CWM is so awesome.
Click to expand...
Click to collapse
edit: i did appear to have one missing driver, my mistake. it was listed in device manager as "unknown - full"
its funny cause i never had to use adb from cwm before, never noticed
cbs2002 said:
d) c:\>adb devices
List of devices attached
(But no device number show up, it cannot recognize my mobile)
Click to expand...
Click to collapse
This symptom generally occurs from not having loaded the drivers for the hardware. As with the majority of hardware devices when being connected to a Windows machine, the drivers need to be loaded. Sometimes these are automatically loaded and other times they have to be manual loaded.
As an alternative and for future reference, the android-sdk package contains general USB drives which usually work for Google Nexus devices.
Generally, as this providers a *cleaner* install, best practice as recommended by Google is to download the whole android-sdk .zip and then from the installer download/install the pieces needed, such as platform-tools (containing adb) and USB drivers as opposed to extracting out the adb.exe and .dll file and installing manually.
cancerouspete said:
you can't use adb from CWM, you need to enter the bootloader, then try adb or fastboot
Click to expand...
Click to collapse
silow said:
You CAN use ADB with CWM. That's one of the reasons why CWM is so awesome.
Click to expand...
Click to collapse
Agreed. To add greater clarification so there is no confusion: adb can't be used from the bootloader.
The /sbin/adbd daemon on the device is only loaded while in normal android boot mode or in recovery mode as called by the init.rc (or on some older devices, recovery.rc) file in the boot process.
Bootloader mode will only work with fastboot while it is in fastboot usb mode.
On some devices, the bootloader has a separate menu for fastboot and on other devices, the fastboot mode is directly entered when entering the bootloader.
Hope that helps clarify!
To silow (and all other helpers)
1. I fail
2. The ADB USB drivers in my PC should be fine as in Device Manager , I can see Android Phone with Android Composite ADB Interface. (No exclamation mark)
3. On the other hand, whenever I plug my mobile into PC, I can see "Unknown-Full"
4. In DOS, when I first type "adb devices" it shows
* daemon not running. starting it now on port 5037*
*daemon started successfully *
List of devices attached
(but NO device number shown!)
5. When I enter adb devices second time, it shows
List of devices attached (No device number shown)
Thank you so much , but it is Hong Kong time (my place) at 0511 am , I didn't sleep all night and I am very tired.
If you don't mind (especially big helper Silow), please give me email so that I capture screen picture and show you in detail (hope it may help)
my email is
[email protected]
I need to sleep now, I will check my email and see you guys or come back this Forum later (several hours later, as I really need some sleep right now)
Pls don't give up on me as this is an expensive mobile. I think the hardware is fine, just need to figure out a way to unbrick it.
Thanks, and see you!
What you need to do is right click on "Unknown-Full" and click on "Update Driver...". Then choose "Install from a list or specific location". Make sure "Search for the best driver in these locations." is checked and "Include this location in the search:" is check. Click on the Browse button and browse to where you extracted the driver files from the link I posted above. Click Next and this should install the correct drivers for you. Afterwards try "adb devices" again to see if ADB now reconizes your device.
To Silow,
Fail.
1. Already installed the drivers you gave me (and there is no 'Exclamation' Mark) in Device manager
2. Situation is the same , Cannot recognize my mobile (i.e. no Device No. after entering adb devices)
3. "List of devices attached" shown in DOS video but without any number.
No other method?
My mobile is really 'bricked' to death?
To Silow and all,
Something important
1. When choose 'install zip from sd card' under CWM, a list of old folder names remains
(e..g gameloft, DCIM, Pictures, etc). That means almost all old files, folders are STILL in my mobile!
2. I have already use the funcion 'Wipe data/factory reset', 'wipe cache partition', ' Wipe Dalvik Cache'
Perhaps my CWM has problem?
What happens when you update drivers for Unknown-Full?
Boot into fastboot and see if your computer recognizes the phone by checking device manager. The key here is to get your computer to see the phone either in fastboot or CWM.
Perhaps try another cable, USB port, or new computer.
The goal is to get Android Phone ADB Composite Interface to show up in device manager either in Fastboot or CWM. Without that done you cannot use Fastboot to flash nor ADB to push a zip file to the phone.
Sent from my Galaxy Nexus using XDA App
I have a rooted/unlocked Verizon GNex running CWM and Linaro 4.2.2 (http://forum.xda-developers.com/showthread.php?t=2106640)
It has a totally busted screen and digitizer, meaning i have a black screen and i don't believe any touch input is being passed to the OS. The phone still turns on, vibrates when it receives messages, and rings when a call comes in and may take a charge. I have full donate version of the GNex tookit. I have CallLog Backup and Restore Installed and SMS Back and Restore installed as well. When i installed that ROM above about 7 days ago, i did not enable USB debugging so i cannot access, backup or view any files on the phone from my PC or the Toolkit. When i try to do a nandroid the Toolkit says "Waiting for USB debugging to be enabled." Can someone please tell me how to enable USB debugging via the toolkit or some other method of retrieving all the data off the phone? Can i rescue the SMS messages as well? I have several nandroid backups, call log and SMS back up files, and many pictures and videos etc i would like to recover. Any help is greatly appreciated. Chris.
Boot up to a custom recovery, then execute this in terminal/command prompt: adb pull /data/media
Beamed from my Maguro
Mach3.2 said:
Boot up to a custom recovery, then execute this in terminal/command prompt: adb pull /data/media
Beamed from my Maguro
Click to expand...
Click to collapse
i guess i need to know the exact key strokes ( hold down volume up and power while booting, then press volume up the power then volume down 3x then power etc.... )to boot up to CWM where i can be able to run adb commands. Won't i have to get to the place in the menu where i can mount the sd card?
Also, that will pull the data from the card, but the toolkit will do a nandroid of the current ROM if i can get the USB debugging enabled, which will allow me to save the SMS messages since the last backup. I was really hoping i could run a nandroid of the current ROM and pull that to restore to a new phone.
Mach3.2 said:
Boot up to a custom recovery, then execute this in terminal/command prompt: adb pull /data/media
Beamed from my Maguro
Click to expand...
Click to collapse
I have CWM recovery installed... so if hold Volume Down and power, then what combination of buttons do i press to be able to pass adb commands to the device?
Thanks!
TurbineTester said:
I have CWM recovery installed... so if hold Volume Down and power, then what combination of buttons do i press to be able to pass adb commands to the device?
Thanks!
Click to expand...
Click to collapse
turn off the phone, press volume up + volume down + power, when it vibrate, you are in fastboot mode, then press 2 times on volume up then one time on power, wait for 10 seconds, connect your phone, open command line where adb file exist and type
Code:
adb devices
you should see the serial number, then
Code:
adb pull /sdcard/
or
Code:
adb pull /data/media/
samersh72 said:
turn off the phone, press volume up + volume down + power, when it vibrate, you are in fastboot mode, then press 2 times on volume up then one time on power, wait for 10 seconds, connect your phone, open command line where adb file exist and type
Code:
adb devices
you should see the serial number, then
Code:
adb pull /sdcard/
or
Code:
adb pull /data/media/
Click to expand...
Click to collapse
Ok, got the ADB drivers installed and tried what you said. The phone shows up in devices with a long number and then "recovery" next to the number
When i type either of the adb commands i get the following:
pull:building file list...
0 files pulled. 0 files skipped.
What about just the key strokes to get to "mount sd card" in CWM?
[UPDATE]
I was just able to get the phone to mount in windows and i can see the files and folders there. I've pulled my call log and SMS backups, titanium backups, and some other files. But one thing i cannot find is my nandroid backups from CWM. I can't seem to find them anywhere on the device.
Is there a trick to be able to see/copy them from Windows?
I looked in
clockworkmod - no back up folder just a download folder
data - only three fodlers there, none of them is media
Thanks again for the help!
I recently also encountered phone card data recovery problem after accidental formatting. In order to copy off all stored card data, I just read and searched a lot.
Finally, I just successfully restored all my card photos, pictures and documents by using some data recovery tools like Recuva, iCare Data Recovery, 4Card Recovery and PhotoRec, etc.
They all works well.
Note: Also learn a valuable lesson to back up everything important on different drives or cards in case of any data loss problem.
Disregard, issue resolved.
I followed the procedure listed below from the 'Help how root new update 8.5.1' thread page 10 from andraw40 (which worked fine btw) but when I got to step 7, Fastboot doesn't seem to be doing what it is supposed to do which is reboot my device into Fastboot. I shut my tablet down, issue the command and then plugin my device but all it does is just boot up into the OS. What am I doing wrong? The SDK is installed and ADB appears to be working. With the device plugged into my PC, I can issue the command 'adb devices' and it shows a device plugged in. Any help would be greatly appreciated!
andraw40 said:
Guys, first of all THANK YOU for posting and helping other people.
For the last several days I have tried as hell to make my Kindle Fire HD to work like an usual android tablet. It was hell! with blocking the tablet, bricking it, reinstall it, coming back to Amazon version, and all of that for many times. Why? Because of too many version of procedures, because of missing important info from different procedures, because of me doing things wrong, and of course, because of me not reading carefully the procedures. Whatever... Finally I get it. And because it is normal to give back, here I am trying to make easy the path for a next "me".
(This procedure is for Windows Vista or above. On Windows XP there will be a lot of problems with ADB.)
So, what I had: Kindle fire HD, 8.9", version 8.5.1
What I have now: Kindle Fire HD, 8.9" (same ), runing CyanogenMod 11 and all the Google Services
How did I get there:
1. install from Amazon the ES File Explorer
2. make sure you enable ADB in Security, on Kindle
3. connect Kindle on computer and make sure you have installed ADB drivers. Check this in Device Manager. If you have the yellow warning, with the tablet connected, install "Kindle_Fire_HD_ADB_Drivers"
4. download, copy on Kindle (in Downloads) and then install "www apks.org-com zhiqupk root apk" to root the tablet. You need to root it in order to give permission to write in System folder. The aplication is the one mentioned by esema1o in the begining (keymasteroot) - Thank you esema1o! It is in Malaysian and you can use Google translate on computer if you are curious about the labels. It will not help you further but it will satisfy your need to know. So: press Mulai Root - it will do something, then will get a message. Press Root, not Batal. Another "doing something" then a new message. Choose Batal. (search on youtoube for "How to Root an Android Device with Key Root Master"). Done! You have rooted the Kindle. Reboot.
5. Open ES File Explorer and in Tools put all the switches on. Actually you will need only the Root Explorer. If you have problems keeping on the Root explorer reboot, open again ES File Explorer, try again. On the same tablet I had experienced different result after restoring the tablet to original Amazon version. Some time, I let the tablet open, come back after 15-30 minutes and try again to activate Root explorer. Surprise! it worked! Other times worked from first try or at seccond try. It is about your luck! Now, after is staying on, press on Root Explorer. A window will pop-up. Choose there to allow w/r on System folder.
6. Download "KindleFireHD89Root.zip" (you can fiind it by search on this forum by name. I'm not yet allawed to post links so remove the space before here: downloadandroidrom com/file/KindleFire/8.9root/KindleFireHD89Root.zip). Extract. Navigate into "stuff" folder. Shift +right click in window, then choose "Open command window here". (Or you just run cmd and navigate to "stuff" folder.)
7. Check fastboot avability:
Type the following command into the cmd window you had opened before at 6.
fastboot -i 0x1949 getvar product
it should return:
< waiting for device>
Then connect Kindle to computer with a regular usb cable. Power down Kindle. Press power buton to start Kindle. . It *SHOULD* show a Fastboot screen and your terminal window should show something like:
product: Jem-PVT-Prod-04
Type this to reboot out of fastboot mode:
fastboot -i 0x1949 reboot
8. follow this procedure: wiki cyanogenmod org/w/Install_CM_for_jem (again, remove spaces and add points to have working link)
Note: when you get to the point "Installing CyanogenMod from recovery" you may be confuse about the fact that adb commands are not working. If so, you check not to be in the recovery boot mode. Just shut down Kindle by long pressing power button, or reboot from meniu and if not passing the booting yellow logo, shut it down again by long pressing power button, then go in the fastboot mode again (see the first part of point 7; do not execute reboot! if you did reboot try again to enter in fastboot mode). Now, in fastboot mode, you can follow the instructions to copy zip files on tablet (I used the cyanogenmode 11 and Google apps zip files). After copy them on tablet, go back to the procedure at the point 4 where you start the kindle in recovery mode again by pressing volume up etc. If you do not succeed by pressing volume up during boot, simple enter again in fastboot (you should know how to do it by now ) and from terminal window on computer (cmd window where you are in "stuff" folder) type:
fastboot -i 0x1949 oem recovery
At this point you are back in the procedure at point 6. Do or not the backup and go next. I did not encountered any problems from this point on.
That is all. Sorry for my English, and I hope that my "procedure" will help someone. Again, thank to all the good people that bother to help us!
Click to expand...
Click to collapse
My N1 suddenly reboot and then it can't start, just continuosly bootloop and can't boot into droidboot or recovery by pressing Power+ Vol-. Any help!!!
anyone help me!
same problem
We need to know more to be able to help. What did you do before updating? root? update? nothing?
syddd said:
We need to know more to be able to help. What did you do before updating? root? update? nothing?
Click to expand...
Click to collapse
I followed this instruction http://forum.xda-developers.com/showpost.php?p=60925623&postcount=44. Root has been established successfully, then installed GApps and after the tablet does not boot
Shvonder said:
I followed this instruction http://forum.xda-developers.com/showpost.php?p=60925623&postcount=44. Root has been established successfully, then installed GApps and after the tablet does not boot
Click to expand...
Click to collapse
That's it, now it not work anymore, just reboot and play bootanimation then reboot
alan_greece said:
My N1 suddenly reboot and then it can't start, just continuosly bootloop and can't boot into droidboot or recovery by pressing Power+ Vol-. Any help!!!
Click to expand...
Click to collapse
I have same problem
Help me!!! Please
help us!
For me its working flawlessly.... may be u have done something wrong. Had u turned off mpt mode ? Did u format and cleared catch before installing gapps ?
still waiting for solution...
( help me
When my one was boot loop.
I 've solved loop problems like following process.
1. Open windows device manger for check N1 is ready to use ADB.
2. Ready CMD for use ADB.
3. Connect to PC and wait until can see ADB Device on windows device manager.
4. ADB devices
5. ADB reboot bootloader
6. Select recovery with volume button.
7. If success on recovery mode. just push once power button. (can see some menu)
8. select factory reset. ( I can't remember correct menu name) or wipe cache / data?
After this okay to boot initial setup.
I can't remember well what I do before .
It's passed 2weeks.
And My one on the way from seller cause fix from another problems.
soondin said:
When my one was boot loop.
I 've solved loop problems like following process.
1. Open windows device manger for check N1 is ready to use ADB.
2. Ready CMD for use ADB.
3. Connect to PC and wait until can see ADB Device on windows device manager.
4. ADB devices
5. ADB reboot bootloader
6. Select recovery with volume button.
7. If success on recovery mode. just push once power button. (can see some menu)
8. select factory reset. ( I can't remember correct menu name) or wipe cache / data?
After this okay to boot initial setup.
I can't remember well what I do before .
It's passed 2weeks.
And My one on the way from seller cause fix from another problems.
Click to expand...
Click to collapse
but when i run adb reboot bootloader, it said my device was unauthorized
soondin said:
When my one was boot loop.
I 've solved loop problems like following process.
1. Open windows device manger for check N1 is ready to use ADB.
2. Ready CMD for use ADB.
3. Connect to PC and wait until can see ADB Device on windows device manager.
4. ADB devices
5. ADB reboot bootloader
6. Select recovery with volume button.
7. If success on recovery mode. just push once power button. (can see some menu)
8. select factory reset. ( I can't remember correct menu name) or wipe cache / data?
After this okay to boot initial setup.
I can't remember well what I do before .
It's passed 2weeks.
And My one on the way from seller cause fix from another problems.
Click to expand...
Click to collapse
i cant use ADB now, always unauthorized device....
Anyone who had a way to fix it? I tried but my N1 dont connect with the PC..
plz help us!
i can not open recovery by pressing vol- + power. I got a bootloop N1,too.
kaikool said:
i can not open recovery by pressing vol- + power. I got a bootloop N1,too.
Click to expand...
Click to collapse
Iam russian... Use the phone flash tool intel v444. connect you device via usb. reboot rebooot rebooot.... when programm detect your device. check in "custom flash" option fastboot or adb. and flash ifwi file. wait min 15.... WHEN YOU DEVICE TURN ON BOOTLOADER CANCEL FLASH (PULL USB CABBLE!!!) volume - to recovery. open recovery menu and factory reset and cache clear. update with sideload and wipe data/ reboot!
@Andreko777 thank you, ill try it. Hope it works! But i think it doesnt work because, when i plug my usb cable to my computer and run Intel flashtool, it can not regconize my device. So i cant do anything else,........
@alan_greece i have found another method in a Chinese forum, but i dont have my device here to do. you can try this.
1. Tools required:
1, Nokia N1 ROOT tools:
link: http: //pan.baidu.com/s/1c0i1KU8 Password: c7i3
2, Nokia ROM package:
link: http: //pan.baidu.com/s/1c06OrhI Password: zfg3
above package Zhongguancun Forum "installed Daitou", "expect Dawn c466469156" offer. Some pictures cut from below "expectations dawn c466469156" rescue brick tutorial (need only be able to enter the official REC tutorial) Step:
Prerequisite: There is a station has already authorized under the USB debugging mode N1 computer; N1 boot card after death, in The computer's device manager can see Android Composite ADB Interface device.
1, the N1 is turned on, connected to the computer.
2, download IntelAndroid-FBRL-05-16-2015-PTR.rar, unzip it into a directory in the root directory of the disk,
Right-click launcher.bat, choose Run as administrator.
Follow the onscreen prompts for capital ACCEPT OK. (Must be capitalized, because LINUX is case-sensitive)
viewing screen, if the device is connected, a blue-green word, if the word is red, was not connected, carefully check the above-mentioned process is correct.
3. After the device is connected, press the T1 diagram interface, Enter. N1 will restart, and N1 official BOOTLOADER screen appears, and writes in execution. Until an error message. Stop.
4, according to N1 volume keys, select the recovery, press the power button to confirm. Reboot into official REC. Then select Options apply update from adb and even computers.
5, put the package before downloading rename the file update.zip pulled platform-tools folder unzipped. Open a command indicator cd into this folder.
6, in the command prompt, type adb sideload update.zip Enter.
7, prompted reboot the N1.
kaikool said:
@Andreko777 thank you, ill try it. Hope it works! But i think it doesnt work because, when i plug my usb cable to my computer and run Intel flashtool, it can not regconize my device. So i cant do anything else,........
@alan_greece i have found another method in a Chinese forum, but i dont have my device here to do. you can try this.
1. Tools required:
1, Nokia N1 ROOT tools:
link: http: //pan.baidu.com/s/1c0i1KU8 Password: c7i3
2, Nokia ROM package:
link: http: //pan.baidu.com/s/1c06OrhI Password: zfg3
above package Zhongguancun Forum "installed Daitou", "expect Dawn c466469156" offer. Some pictures cut from below "expectations dawn c466469156" rescue brick tutorial (need only be able to enter the official REC tutorial) Step:
Prerequisite: There is a station has already authorized under the USB debugging mode N1 computer; N1 boot card after death, in The computer's device manager can see Android Composite ADB Interface device.
1, the N1 is turned on, connected to the computer.
2, download IntelAndroid-FBRL-05-16-2015-PTR.rar, unzip it into a directory in the root directory of the disk,
Right-click launcher.bat, choose Run as administrator.
Follow the onscreen prompts for capital ACCEPT OK. (Must be capitalized, because LINUX is case-sensitive)
viewing screen, if the device is connected, a blue-green word, if the word is red, was not connected, carefully check the above-mentioned process is correct.
3. After the device is connected, press the T1 diagram interface, Enter. N1 will restart, and N1 official BOOTLOADER screen appears, and writes in execution. Until an error message. Stop.
4, according to N1 volume keys, select the recovery, press the power button to confirm. Reboot into official REC. Then select Options apply update from adb and even computers.
5, put the package before downloading rename the file update.zip pulled platform-tools folder unzipped. Open a command indicator cd into this folder.
6, in the command prompt, type adb sideload update.zip Enter.
7, prompted reboot the N1.
Click to expand...
Click to collapse
Now i cant authorized my device anymore