Hi!
Yesterday night, I was on the lookout for emoji font for my phone. To no avail finding colored emoji icons, I ended up going to Font Changer (Root) but found nothing there either. Since I just discovered the app, I thought, why not just try something new? A new font? So I downloaded a font, made a backup of my old font and rebooted the phone. But then it was done. My phone didn't start anymore and was stuck on booting. I went over to Modaco forums, downloaded a custom recovery and then downloaded one of the many dedoxed roms there. I tried to flash it, but in avail.
-- Install /data/media
Finding update package...
Opening update package...
Verifying update package...
Installation aborted.
So I downloaded another ROM to try. Same error. I tried to download the stock firmware from ASUS. Same error. What is causing this?
Keep in mind, I have done a data/factory reset wipe! The phone was obviously rooted before the incident! I did not have a custom recovery before the incident! I have tried 4 different ROMs! I am currently on Modaco's custom recovery!
ROMs tried -
* Deodexed TW ROM (Padfone 2)
* Deodexed WWE ROM (Padfone 2)
* [Pre MCR WWE ROM (Padfone 2)
* PadFone2 Firmware: V10.4.11.13 Only for JP SKU (Android 4.1) (STOCK)
Current recovery -
* Modaco R1 Custom Recovery
try restoring with the phone plugged in to a power source.
it worked for me when i got the same message trying to update.
Uzrbital said:
Hi!
Yesterday night, I was on the lookout for emoji font for my phone. To no avail finding colored emoji icons, I ended up going to Font Changer (Root) but found nothing there either. Since I just discovered the app, I thought, why not just try something new? A new font? So I downloaded a font, made a backup of my old font and rebooted the phone. But then it was done. My phone didn't start anymore and was stuck on booting. I went over to Modaco forums, downloaded a custom recovery and then downloaded one of the many dedoxed roms there. I tried to flash it, but in avail.
-- Install /data/media
Finding update package...
Opening update package...
Verifying update package...
Installation aborted.
So I downloaded another ROM to try. Same error. I tried to download the stock firmware from ASUS. Same error. What is causing this?
Keep in mind, I have done a data/factory reset wipe! The phone was obviously rooted before the incident! I did not have a custom recovery before the incident! I have tried 4 different ROMs! I am currently on Modaco's custom recovery!
ROMs tried -
* Deodexed TW ROM (Padfone 2)
* Deodexed WWE ROM (Padfone 2)
* [Pre MCR WWE ROM (Padfone 2)
* PadFone2 Firmware: V10.4.11.13 Only for JP SKU (Android 4.1) (STOCK)
Current recovery -
* Modaco R1 Custom Recovery
Click to expand...
Click to collapse
Try some other recoveries
Lky CWM or TWRP
Sent from my A116 using Tapatalk 2
Same happened to me, but I got it up and running again!
Earlier today I bricked my Padfone 2 too by installing 3rd part font. After a reboot to apply the changes, it got to the boot logo but never any further.
I got it up and running again, :victory: and to those out there in same or similar situation, here's a tutorial on what I did:
Before we start, there's a few things you need;
1.1 Latest ADB version (I used 1.0.31)
1.2 Latest Fastboot version
1.3 CWM Recovery
1.4 Latest ASUS USB Drivers (available from ASUS Support site)
1.5 Padfone 2 Firmware (available from ASUS Support site)
*** NOTE: For ease of use, place extract and place all of the above to the same folder.
*** NOTE: Inside the Padfone 2 Firmware ZIP file, there's another ZIP file. This is the one we need! The one I used was called "WWE_A68-10.4.15.1-0-ota-user.zip"
*** NOTE: This method does not install CWM Recovery on your phone, it only boots it temporarily.
If you have all of the above, continue to step 2;
2.1 Booting your Padfone 2 into Fastboot mode
2.2 Press and hold Power + Volume up buttons
In Fastboot mode, connect your phone to your computer and launch cmd. Wait for windows to install necessary drivers if needed.
3.1 Navigate your CMD to the folder containing ADB, Fastboot and CWM Recovery (recovery.img)
3.2 In CMD type:
Code:
fastboot boot recovery.img
In the CWM Recovery on your phone, select the option titled "Install ZIP from sideload".
Use the volume keys to navigate and select by pressing the power button.
4.1 In CMD, transfer the Padfone 2 Firmware by typing
Code:
adb sideload [firmware-file-name.zip]
- Example from my case, I wrote:
Code:
adb sideload WWE_A68-10.4.15.1-0-ota-user.zip
4.2 When it is done, you'll be presented with CWM Recovery's screen again, select "Reboot system now".
4.3 CWM Recovery will present you with a warning saying: "ROM may flash stock recovery on boot. Fix?" - Select "NO".
[EDIT]
In some, if not all cases, Windows will try to install new drivers, but fail. If windows installed the drivers correctly, skip this step.
To solve this, go to device manager by entering the Start menu, right-click Computer and select “Manage”. Select the Device Manager.
You should see a failed device named A68. Right-click it and select “Update device software”
Select “Browse my computer for driver software”
Select “Let me pick from a list of device drivers on my computer”
Select “Have Disk”
Now browse and navigate to the folder you extracted your ASUS USB Drivers to and select the file named “android_winusb.inf”
Select “ASUS Android ADB Interface” and install.
Added files and a neat pdf tutorial.
[/EDIT]
All done! You should have a working Padfone 2 again!
Please note that you may need to root your phone again.
Please credit if used
/HelmerN
brickeddd
hey i just tried all these methods and while trying to boot recovery.img with CMD nothing else happens but CMD says <waiting for device>. My SD card is empty and i have no ROMs on international storage so i can't install. I am using TWRP custom recovery. I have no idea what to do anymore. Please help!
zimbou said:
hey i just tried all these methods and while trying to boot recovery.img with CMD nothing else happens but CMD says <waiting for device>. My SD card is empty and i have no ROMs on international storage so i can't install. I am using TWRP custom recovery. I have no idea what to do anymore. Please help!
Click to expand...
Click to collapse
listen : about your problem which is <waiting for device> just unplug the usb cable from your phone and plug it again but you have to do very fast so i want you to pull the usb a little bit and connect it again but do it fast after that the cmd its gonna recognize your phone %100 try it ,,,,,
Related
Hi,
After changing my phone's date into the future, my G2 Touch told me there was an update available, so I told it to go ahead and apply it. When the phone rebooted it came up with this message:
E:No signature (218 files)
E:Verification failed
Installation aborted
I have nandroid installed on the phone. At least I think that's what's installed - I haven't played with any ROM stuff since November I think, when I changed the bootloader (I think - if that's what's giving me the option to do a nandroid backup now) and installed the newest T-Mobile G2 ROM.
Should the phone be able to install the OTA update, or will I have to replace the bootloader in order to get the OTA update on there? If I do have to replace the bootloader, will that require a full wipe?
James
Completely the same problem with HTC Hero after European OTA update. It has been rooted while ago (by following instructions from this forum) and now after setting up date in the future and confirming update, phone reboot and I get "Android System recovery" screen with menu and this message bellow it:
Build: CyaanogenMod v1.4 + JF
Finding update package ...
Opening update package ...
Veryfing update package ...
E: No signature (218 files)
E: Verification failed
Installation aborted.
Click to expand...
Click to collapse
I have the same problem (I did not write down the message, so I'm not sure which "Build:" was listed) .
The update fails, the phone reboots and then works under the old build. Under "settings/about phone" there is also no info about the update. Can one force the phone to download the update a second time? Would this help?
Bye
Nick
P.S. I'm running the phone in Germany over e-plus as network provider. The updates was done over a WiFi connection. The phone is not branded - was from the free market and not from a provider.
Hey,
got the same problem. At least I could extract the official OTA-update-zip to publish it here (see attachment)
There also is a "recovery.img" in the update zip, so I guess usually the OTA update will kill custom recovery bootloaders. We could replace the "recovery.img" in the zip with a hacked one before applying the update.
However first we should fix the verification error...
P.S.: Also Germany, not branded, Vodafone Network
Does anyone know if I will lose all my data if I reflash the original recovery.img onto my phone?
As I used flashrec to flash ra-recovery.img I keept all my data. So I don't belive you will lost any of your data except of your actual recovery image.
At last, we can try to flash origianl RUU, but with this we lost all our personal data.
----
I tried it. I installed flasrec.apk using ASTRO and used this app to flash the recovery.img from here mentioned/linked OTA update zip. Afterwards I changed date again and was able to install OTA Update without errors and loosing personal data. Now I'm without nandroid because of changing recovery image. Keep cool at this procedure installing these flashes takes long time in boot process - I was really near an hard reset ...
Flashing the original recovery.img should not be a problem.
However, I don't want to lose root access, and thus I will wait for the official HTC 2.1-update (hoping someone publishes it online) and then flash it by myself..
I don't mind losing root access at this moment (the reason I rooted my phone was to get wifi tethering but never got it working with a mac).
Since I am total noob with android stuff, I would highly appreciate some step by step instructions or link where I can find what to do. Thanks guys.
Hi, I've been trying to install the recovery.img from the update but I get this message with flashrec 1.1.3:
Code:
"Flash FAILED: Could not run command."
I'm using WWE 405.66 flashed with ra-recovery img 1.6.2... and the rom is rooted.
What am I doing wrong?
I can't even install ra-recovery with flashrec now and I have installed ra-recovery 1.6.2 this morning (I was using 1.5)
And yes, I know I'm going to lose ra-recovery.
rseffner said:
As I used flashrec to flash ra-recovery.img I keept all my data. So I don't belive you will lost any of your data except of your actual recovery image.
At last, we can try to flash origianl RUU, but with this we lost all our personal data.
----
I tried it. I installed flasrec.apk using ASTRO and used this app to flash the recovery.img from here mentioned/linked OTA update zip. Afterwards I changed date again and was able to install OTA Update without errors and loosing personal data. Now I'm without nandroid because of changing recovery image. Keep cool at this procedure installing these flashes takes long time in boot process - I was really near an hard reset ...
Click to expand...
Click to collapse
What was the rom you were using when you flashed the official recovery?
alvaritolalala said:
Hi, I've been trying to install the recovery.img from the update but I get this message with flashrec 1.1.3:
Code:
"Flash FAILED: Could not run command."
I'm using WWE 405.66 flashed with ra-recovery img 1.6.2... and the rom is rooted.
What am I doing wrong?
I can't even install ra-recovery with flashrec now and I have installed ra-recovery 1.6.2 this morning (I was using 1.5)
And yes, I know I'm going to lose ra-recovery.
Click to expand...
Click to collapse
Try the following:
- Copy the recovery.img to your SD card
- Turn off the phone, turn it on with Buttons "HOME"+"ONOFF" pressed such that the ra-recovery which you already have starts
- connect to your phone by cable using "adb shell"
- Then with root access you can flash the image by typing "flash_image recovery /sdcard/recovery.img"
This should do it
jamesots said:
Hi,
After changing my phone's date into the future, my G2 Touch told me there was an update available, so I told it to go ahead and apply it. When the phone rebooted it came up with this message:
E:No signature (218 files)
E:Verification failed
Installation aborted
I have nandroid installed on the phone. At least I think that's what's installed - I haven't played with any ROM stuff since November I think, when I changed the bootloader (I think - if that's what's giving me the option to do a nandroid backup now) and installed the newest T-Mobile G2 ROM.
Should the phone be able to install the OTA update, or will I have to replace the bootloader in order to get the OTA update on there? If I do have to replace the bootloader, will that require a full wipe?
James
Click to expand...
Click to collapse
hey,
I had same problem
go to All programs--> Recovery Flasher--> Restore backup
then restart and update OTA
Greetings from Zagreb, Croatia
Hey guys.
So, for those of you, who do NOT care about root for now, here's what worked for me:
1.: Download the zip-file with the OTA Update, mentioned on the first page and extract it.
2.: Connect your Hero to your PC and copy the recovery.img from the OTA onto your sdcard. Disconnect from computer.
3.: Boot your phone into the bootloader (Home + PWR).
EDIT: Now connect the phone to the pc again!
4.: open the command prompt of your pc, navigate to your Android SDK folder. (If it is not installed, download it and make sure you've got the needed drivers. Otherwise: Download them, using the Setup.exe from Android SDK)
5.: Here are the needed commands:
Code:
adb shell
$su
mount -a
flash_image recovery /sdcard/recovery.img
6.: reboot your phone after exitting the command prompt.
7.: Factory reset, reboot again
8.: And well, wait for the update-window again and be happy, now it should work
EDIT 2:
Any questions? Just leave a reply
@Revoluzifer
OK I did exactly as you explained, but having problem with su command:
Code:
C:\sdk\tools>adb shell
adb server is out of date. killing...
* daemon started successfully *
/ # su
su
/sbin/sh: su: not found
I know I know, you're going to say my phone is not rooted at all But believe me it was and some apps that require root access are there (screenshot, wifi tether etc.).
I even tried to find su cmd with find:
Code:
C:\sdk\tools>adb shell
adb server is out of date. killing...
* daemon started successfully *
/ # su
su
/sbin/sh: su: not found
But got nothing as you can see.
Ideas?
@dinke:
Which bootloader / recovery console is installed?
Means, what do you see, after booting with Home + PWR?
Also try to input $su instead of just su.
But first tell me your "hack" if any
@Revoluzifer
Thanks for quick reply
I see Android system recovery screen, not sure if this is nandroid or what but have this text on the screen with following options:
Android system recovery <2>
Use trackball to highlight;
click to select.
[Home+Back] reboot system now
[Alt+S] apply sdcard:update.zip
[Alt+W] wipe data/factory reset
[Alt+B] nandroid v2.2 backup
[Alt+R] restore latest backup
[Alt+F] repair ext filesystems
-------------------------------
Click to expand...
Click to collapse
And bellow menu there is build ID:
Build: CyanogenMod v1.4 + JF
I don't remember exact procedure that I applied for rooting hero, but I followed instructions from this forum (I can try by searching for exact thread if that may help you).
Edit: I applied root procedure by following instructions on these two links:
http://forum.xda-developers.com/showpost.php?p=4257045
http://forum.xda-developers.com/showthread.php?t=559613
That sounds just perfect
CyanogenMod 1.4 is exactly the same recovery console i have had before.
(Btw, Hero is not officially supported by CM anymore, had a nice discussion yesterday in cyanogen IRC )
So, try to use $su instead of su, that's what I typed and it all worked just great.
But you definitely first booted into bootload and then connected the phone to your pc again?
Tell me if this worked for you, please...
Greetz,
Sven
dinke said:
Code:
C:\sdk\tools>adb shell
adb server is out of date. killing...
* daemon started successfully *
/ # su
su
/sbin/sh: su: not found
Click to expand...
Click to collapse
Forget about the "su". You are already root.
(You can see this, as there's a '#' in front)
Just do the mounting and flashing
Oh... You're right, nerdture... didn't see the #
I *think* I've tried mount no matter of missing 'su' cmd and it didn't work either but will try again as soon as I manage to find some cable to connect hero with macbook (no longer nearby windows machine but have sdk installed on mac so should be working as well)
Revoluzifer said:
But you definitely first booted into bootload and then connected the phone to your pc again?
Click to expand...
Click to collapse
Yes
Phone Details
Motorola Atrix 4G AT&T (bought around June 2011 Time frame)
System Version
4.5.91.MB860.ATT.en.US
Model Number
MB860
Android Version
2.34
Baseband Version
N_01.77.30P
Webtop Version
WT-1.2.0-110
Kernel Version
[email protected] #2
Build Number
4.5.91
I am absolutely new to this Android ROM installs on the phones. Though I decided to install this ROM I absolutely didn’t’ have any idea how to proceed. As a beginner I started doing the following in order.
Download and Keep the CM7 ROM
1. Downloaded Ba2F.zip to my laptop
2. Downloaded and Installed the Motorola USB drivers MotoHelper_2.0.53_Driver_5.2.0.EXE
3. Connect the Atrix and set the USB option on the phone to “USB Mass Storage”
4. Copy both BaTF.zip as well as the Extracted one to Phone internal storage as well as the Ext-SDcard on the phone
Download ROM Manager and Titanium Backup
1. Downloaded both from Android Market (ROM Manager Pro and Titanium Backup Free Version)
2. Both Apps won’t open because I had not ROOTED the phone
Root the Phone
1. I used “Pete's Motorola Root Tools.EXE” file to ROOT the phone
2. Followed step by step as mentioned here http://www.androidauthority.com/how-to-root-motorola-atrix-4g-35233/
Flash ClockworkMod Recovery
1. I used ROM Manager to do this as when you try to do anything in ROM manager it prompts to do this. The version of this is 5.0.2.0 ( I am not sure what is this for why we have to do this)
Unlocking the Bootloader
1. What I learned is, to unlock the bootloader, we have to first flash the phone with the SBF file
a. Installed RSDLite5.3.1.msi
b. Loaded the file 4547-fix-try2.sbf (Downloaded from http://forum.xda-developers.com/showthread.php?t=1136261)
c. Boot the phone with Power+volume UPPER key pressed till "Starting RSD protocol support" comes up
d. Connect to the Laptop and Hit Start button in RSD Lite Program
e. It Did Throw an error saying “FAIL” after showing the following message
i. Failed to boot: error 0x1000'( not word for word). There will also be a list of boot options like Fastboot, RSD, Recovery, etc. And it says Starting Fastboot Protocol
2. Then comes unlocking the phone
a. Though I had the previous error message, it still had the Fastboot Protocol loaded
b. I went to the FASTBOOT folder in command prompt of my laptop executed the following to unlock the phone which worked perfectly as I see the “Unlock” on the left hand corner when phone boots
c. fastboot oem unlock (it gave me the code) then I used the code to unlock
d. fastboot oem unlock #######
e. fastboot reboot
3. Installing the recovery IMG
a. I had downloaded the Recovery IMG file (recovery-atrix5.img) from http://forum.xda-developers.com/showthread.php?t=1204500
b. Booted the phone into Fastboot mode (turn off phone, hold power and volume down key until 'fastboot' appears then use volume up to select so it says 'starting fastboot protocol support').
c. From the CMD promnt and FASTBOOT directory I used fastboot erase recovery
d. Then I executed fastboot flash recovery recovery-atrix5.img (Note: I didn’t rename the file to recovery as suggested by some people)
e. Then gave fastboot reboot to restart.
4. Booting into Recovery mode (This is where I have the problem)
a. The phone is not booting into recovery it’s not going past the Android and yellow Triangle screen
b. I re-flashed the phone same SBF file (this time it was a success showed in the RSD Lite Program), re-installed the same IMG file after renaming to recovery.img
c. Also tried with a different IMG from the same link (recovery-blue-atrix5.img) but no luck
d. Also deleted the file install-recovery.sh from ./etc/ folder (bought the app root manager to delete the file) and then push the recovery.img, no luck
e. Some people said to TAP the bottom right corner while on that screen, did that but nothing is happening
f. Then I saw a note to press both the Volume Keys at the same time, this works but in this mode the cursor (I mean the selection) on the phone doesn’t go to the First TWO (i and iii) shown below, it allows me to select any of the last FOUR (v, vi, vii, viii).
i. Android System Recovery <3e>
ii. <EMPTY LINE >
iii. Android System Recovery utility
iv. <EMPTY LINE >
v. Reboot System now
vi. Apply update from sdcard
vii. Wipe data/factory reset
viii. Wipe cache partition
g. Using the above option I did factory reset but sill no results.
5. Current condition of the phone
a. It boots in unlock mode and I can do all the daily tasks. But I want to install the CM7 ROM that’s my requirement
PLEASE HELP HELP HELP
First of all, I applaud your effort in giving the a very comprehensive description of your issue.
Second, it seems you are having issues with installing a custom recovery because the recovery you're describing is still the stock recovery. I'll look around and see if I can find something that might help.
jhakash said:
4. Booting into Recovery mode (This is where I have the problem)
a. It boots in unlock mode and I can do all the daily tasks. But I want to install the CM7 ROM that’s my requirement
PLEASE HELP HELP HELP
Click to expand...
Click to collapse
---------- Post added at 11:31 AM ---------- Previous post was at 11:28 AM ----------
Have you tried re-installing the CWM from RomManager through RomManager? And then boot into recovery from within the app?
---------- Post added at 11:40 AM ---------- Previous post was at 11:31 AM ----------
EDIT: This might seem trivial, but is "USB Debugging" turned on?
You are the Man, I just flashed the same CWM 5.0.2.0 and i am in the recovery mode. This gave me an error when i did last time hence i didn't try again.
Thanks a bunch
Glad I can help, also, I think it's recommended to use the RomManager recovery for CM7 so good thing it worked.
jhakash said:
You are the Man, I just flashed the same CWM 5.0.2.0 and i am in the recovery mode. This gave me an error when i did last time hence i didn't try again.
Thanks a bunch
Click to expand...
Click to collapse
Oops.. started again, Can i use the recovery-atrix5.img and ROM manager flash it? if yes, then how?
I copy this file (after renaming to recovery.img) to both internal storage and SD card then what option should i choose in ROM Manager?
If you downloaded the CWM zip file for the romracer recovery and as long as RomManager's recovery is working then, yes, you can.
jhakash said:
Oops.. started again, Can i use the recovery-atrix5.img and ROM manager flash it? if yes, then how?
I copy this file (after renaming to recovery.img) to both internal storage and SD card then what option should i choose in ROM Manager?
Click to expand...
Click to collapse
jhakash said:
Oops.. started again, Can i use the recovery-atrix5.img and ROM manager flash it? if yes, then how?
I copy this file (after renaming to recovery.img) to both internal storage and SD card then what option should i choose in ROM Manager?
Click to expand...
Click to collapse
See post#2 from romracer's thread. Read the Miscellaneous part. Probably need to get rid of, or backup, install-recovery.sh.
He has mentioned he already did that. In his OP, under the steps he took look at "Booting into Recovery Mode" - 4.d, he says he removed it.
Maybe he's not doing it in the right order? Do you happen to know which should be done first as far as installing recovery and removing said file?
ghost_og said:
See post#2 from romracer's thread. Read the Miscellaneous part. Probably need to get rid of, or backup, install-recovery.sh.
Click to expand...
Click to collapse
live4nyy said:
He has mentioned he already did that. In his OP, under the steps he took look at "Booting into Recovery Mode" - 4.d, he says he removed it.
Maybe he's not doing it in the right order? Do you happen to know which should be done first as far as installing recovery and removing said file?
Click to expand...
Click to collapse
Woops, I should have read more carefully. It's best to remove the file first and then flash the recovery.img, or else the script will install the stock recovery on boot. That would make stock recovery the current one on the phone at the time of the script getting deleted.
I would double check and make sure /system/etc does not have install-recovery.sh. If it is not there, then proceed to the fastboot steps and reflash the recovery.img again. It should stick this time.
@Ghost, yes i deleted the file multiple times however i didn't find the /system/etc folder on the Internal Storage. however I found the install-recovery.sh file under /etc folder. The thing i observed that whether i flash it with a new CWM or not if i reboot the phone then it was created by itself.
@Live4nyy, Thanks for your suggestion, I could able to install CM7 now and it looks awesome good so far, but looks like i need to install Google Apps separately to access the APP market, am I right?
The only thing that happens to me is, it allowed me to go to Recovery only ONCE after i Flashed it thru ROM Manager, if i exit out of recovery without doing anything then next time tried to go to Recovery, it will struck at the same old Android screen and i had to flash it again. But Many thanks for suggesting to flash it thru ROM Manager.
Now with CM7, under ROM Manager (I guess this comes default with CM7) I see there is no version listed under "Flash Clockworkmod Recovery" and it says i must have to install it in-order to Flash and restore ROMs, do i need to do that? I can go to Recovery mode after reboot without any issues. Please Advise.
------
Jhakash
jhakash said:
@Ghost, yes i deleted the file multiple times however i didn't find the /system/etc folder on the Internal Storage. however I found the install-recovery.sh file under /etc folder. The thing i observed that whether i flash it with a new CWM or not if i reboot the phone then it was created by itself.
Click to expand...
Click to collapse
I just checked out my girlfriend's stock, locked, unrooted Atrix and she actually has install-recovery.sh in both /etc and /system/etc. Her file manager does not alphabetize anything in either folder, so I almost overlooked the second one.
If you're already on CM7, then you probably won't need to worry anymore. They have an entirely different set of start up scripts in that folder. Welcome to the community!
At this point I do not know enough to help you any further with this issue. All I knew about is the file that needs to be removed that @ghost_og has mentioned. But if you can flash it from RomManager and access CWM from there as well then I guess that's a good enough workaround for now.
Does anyone else have any idea why the stock recovery cannot be removed?
jhakash said:
@Live4nyy, Thanks for your suggestion, I could able to install CM7 now and it looks awesome good so far, but looks like i need to install Google Apps separately to access the APP market, am I right?
The only thing that happens to me is, it allowed me to go to Recovery only ONCE after i Flashed it thru ROM Manager, if i exit out of recovery without doing anything then next time tried to go to Recovery, it will struck at the same old Android screen and i had to flash it again. But Many thanks for suggesting to flash it thru ROM Manager.
Now with CM7, under ROM Manager (I guess this comes default with CM7) I see there is no version listed under "Flash Clockworkmod Recovery" and it says i must have to install it in-order to Flash and restore ROMs, do i need to do that? I can go to Recovery mode after reboot without any issues. Please Advise.
------
Jhakash
Click to expand...
Click to collapse
I am good to go now, everything seems to be functioning well after flashing CM7 ROM, no more recovery issues, and the Stock recovery is gone now.
Appreciate for all the info you guys provided, it helped a lot. Have a great day and Merry Christmas.
Regards
Jhakash
Hi.
While trying to upgrade my tablet to a later version of Android, something borked the bootloader. The tablet boots fine to a bare ICS (no gapps, but ROM MANAGER installed, though it does nothing but hang), but trying to boot into recovery mode hangs it (black screen with android robot, OEM info).
I can install apks to the tablet. I have installed ADB on my PC and it sees my tablet.
Where do I go from here ?
I have no clue
- what exact file(s) I need (my tablet is an Ainol novo8 advanced)
- where I need to put them
- what the commands are to do that
- it should be rooted (the superuser app aloows me to grant su privileges to apps)
Any help that can bring my tablet back to life would be very welcome.
Olivier
obarthelemy said:
Hi.
While trying to upgrade my tablet to a later version of Android, something borked the bootloader. The tablet boots fine to a bare ICS (no gapps, but ROM MANAGER installed, though it does nothing but hang), but trying to boot into recovery mode hangs it (black screen with android robot, OEM info).
I can install apks to the tablet. I have installed ADB on my PC and it sees my tablet.
Where do I go from here ?
I have no clue
- what exact file(s) I need (my tablet is an Ainol novo8 advanced)
- where I need to put them
- what the commands are to do that
- it should be rooted (the superuser app aloows me to grant su privileges to apps)
Any help that can bring my tablet back to life would be very welcome.
Olivier
Click to expand...
Click to collapse
If you can still use ADB your tablets bootloader is likely not messed up, it sounds like you booted the tablet into fastboot mode not recovery. To get into recovery you can enter it by holding a key combination the most common combination is holding volume up plus the power button at the same time. If that doesn't work from ADB you should be able to get into recovery by running the command:
Code:
adb reboot recovery
Also ROM manger doesn't always work right with every device so I would recommend just uninstalling ROM Manager for now. If it is booting fine into bare ICS then your tablet should be ok, if your looking for Google Apps for ICS they can be found here http://cmw.22aaf3.com/gapps/gapps-ics-20120317-signed.zip. Let me know if you still have questions .
Sent from my SCH-I535 using xda premium
Thanks a lot for your answer.
I'm sorry I didn't describe the issue well: I can no longer access the recovery mode.
I used to get to it by cold-booting the tablet holding Vol+ and Power. I used that to install ICS, gaps, powertools and 3D tools as described in http://forum.xda-developers.com/showthread.php?p=36059461#post36059461. The first package (recovery CWM) failed to installed because it was unsigned), the others installed, but in the end it seems I only got ICS: I have no gapps.
Now doing Vol+ and Power only gets me to the boot screen (a green android with OEM info, on a black background). Your "adb reboot recovery" does the same. I can only exit that screen by a hard reset.
During a normal boot, that screen flashes by for a couple of thesconds, then another, then the ICS colorful boot animation.
I have no clue how the recovery boot process works. I'm guessing it's reading a file of the internal Flash, and that file or dependencies got corrupted or partly overwritten by one of the packages I installed ? I'm not even sure if CWM recovery replaces the default recovery mode, or if it chains right after it ? I do have a supposedly-working CWM recovery .zip from the authors of the CM10 hack, as well as the "original" files listed here: http://forum.xda-developers.com/showpost.php?p=31089682&postcount=286 (official images from an out-of-the-box, unhacked tablet).
PS: the recovery mode I used to have was very rustic, only taking "update.zip" as an input, so when I did the update I had to go back and forth renaming the first package to "update.zip", applying it, renaming it "update1.zip, then on the the second package, etc, etc... It said Android System Recovery (3e), so maybe 3e was the version.
last but not least, if I could at least get the gapps onto the tablet, even w/o fixing the recovery mode, it would be very useful. I can install apks, or follow instructions to do it via adb ?
obarthelemy said:
Thanks a lot for your answer.
I'm sorry I didn't describe the issue well: I can no longer access the recovery mode.
I used to get to it by cold-booting the tablet holding Vol+ and Power. I used that to install ICS, gaps, powertools and 3D tools as described in http://forum.xda-developers.com/showthread.php?p=36059461#post36059461. The first package (recovery CWM) failed to installed because it was unsigned), the others installed, but in the end it seems I only got ICS: I have no gapps.
Now doing Vol+ and Power only gets me to the boot screen (a green android with OEM info, on a black background). Your "adb reboot recovery" does the same. I can only exit that screen by a hard reset.
During a normal boot, that screen flashes by for a couple of thesconds, then another, then the ICS colorful boot animation.
I have no clue how the recovery boot process works. I'm guessing it's reading a file of the internal Flash, and that file or dependencies got corrupted or partly overwritten by one of the packages I installed ? I'm not even sure if CWM recovery replaces the default recovery mode, or if it chains right after it ? I do have a supposedly-working CWM recovery .zip from the authors of the CM10 hack, as well as the "original" files listed here: http://forum.xda-developers.com/showpost.php?p=31089682&postcount=286 (official images from an out-of-the-box, unhacked tablet).
Click to expand...
Click to collapse
obarthelemy said:
PS: the recovery mode I used to have was very rustic, only taking "update.zip" as an input, so when I did the update I had to go back and forth renaming the first package to "update.zip", applying it, renaming it "update1.zip, then on the the second package, etc, etc... It said Android System Recovery (3e), so maybe 3e was the version.
Click to expand...
Click to collapse
obarthelemy said:
last but not least, if I could at least get the gapps onto the tablet, even w/o fixing the recovery mode, it would be very useful. I can install apks, or follow instructions to do it via adb ?
Click to expand...
Click to collapse
The recovery you are referring to is to the standard Android 3e recovery it is included in every version of Android, and will always be like that unless you install a custom recovery such as CWMR and or TWRP. As a general rule you should never install a custom ROM without having a custom recovery image installed first, essentially all the stock 3e recovery is good for is installing OTA updates and preforming a basic factory reset of your phone. You should try and fix your recovery before going any-further, you can sign the un-signed zip by using this tool. Overall, I would focus on trying to fix the recovery to prevent any further damage to your tablet and so that way you have a simple way to recover from anything that might go wrong when flashing ROMs, mods, and other zip files.
issue with the uImage linked
The uImage linked on the download pages for the CM10 and CM9 version ends in ".*"
I have no clue what the normal extension should be; replacing that *.zip doesn't work. Is the file bad, or am I just too clueless about what to do with it ?
Ok so the question is:
1- which "recovery mode" file should I install on my tablet, especially since the mod author's ones seem flaky
2- how do I do that via ADB since my tablet no longer seems to have a working "recovery mode".
I'm sorry to hassle you with those questions... I've looked around, I can't find info nor files I'm confident about ?
Hi Everyone i'm a newbie in this field so correct me if i'm wrong with some terms...
It's really frustrating to accidentally delete 'build.prop' without backing up and having only blackscreen showing up when you reboot is annoying isn't it? Well luckily i have made some fix here it is
BUT... make sure:
1.you have your drivers correctly installed
2.you installed your Android SDK and Java SDK(Note: java sdk must be the first to be installed)
3.you installed your adbfastboot
4.you can access to recovery and download mode(research on how to execute it.)
5.most helpful if you have installed PDANet on your PC(it will help you determine if your adb is runnning)
6.you have downloaded the suitable .img clockworkmod file(needed for flashing
7.you downloaded you're stock rom/custom rom (it's up to you)
6.you have internet acess(needed for researching since i can't provide the links)
7.and especially PATIENCE!
LET's BEGIN.
1.Put your phone into download mode
2.Then wait for notifications and check if an Android Device is installed
3.You installed your fast boot now you're ready to flash your .img clockworkmode file
...3.1.Open your cmd
...3.2.CD your path for the adbfastboot
...3.3.then type 'fastboot flash recovery clockworkmod.img' (without the quotes)
4.Now that you installed your CWM put the downloaded ROM into your SDcard then mount it to your device
5.Remove then re attach the battery and proceed to recovery mode(research on how to execute your phone's recovery mode)
6.Then now you're in cwm recovery mode you may now flash a stock/custom rom
(use your volume buttons to go up and down and power button to enter)
...6.1.Clear your data
...6.2.In the menu choose 'apply update from SD card' then install from SDcard
...6.3.Toggle and locate where you have place the rom
...6.4.Choose the desired rom then enter, then the package will install wait until it finishes and go again to the main selection menu
...6.5.Reboot and there you have it you have just revived your phone
Another Method is by using adb
1.Find the build.prop that you deleted for your phone
2.Push it inside of the adb ex.(adb push<file location> [space] <remote>)
this is my first post hope i helped you...
hey....
my x-bo o2 phone..
stock on boot animation although i reset and reboot it it still stock...
because i replace a new build prop came from my old phone ...after i reboot my phone ..it wont start..
heellp plz..
I think you have to flash the firmware with odin.
Replace permission
Permission change is required for work.
saidiemenor said:
hey....
my x-bo o2 phone..
stock on boot animation although i reset and reboot it it still stock...
because i replace a new build prop came from my old phone ...after i reboot my phone ..it wont start..
heellp plz..
Click to expand...
Click to collapse
You want to update your device, you have the OTA zipfile, but you don't know how to use it, you don't want to bricked your device!
That's why I've wrote this guide. I'm not the writer, just an adaptor for xda member
By downloading, flashing these files and use this guide you agree to the following:
Your warranty is now void.
We are NOT responsible for bricked devices, thermonuclear war, or you getting fired because the alarm app failed. Please do some research if you have any concerns about features included in this guide before use it! YOU are choosing to make these modifications, and if you point the finger at us for messing up your device, I will laugh at you with all of my teeth.
Support is limited. I do this as a hobby in our free time. I'll do my best to help you if you state your problem in clear English, with as much information as you can (what mods you selected, have you wiped, when exactly does the error occur, what type of phone you have, what carrier, logcat and so on. The more information you offer, easier for me to help you. If you do not ask for support in clear English and with no information what-so-ever we will ignore your issue
Click to expand...
Click to collapse
Before to flash or use fastboot lines command, you need to read quietly this guide. Download all files in one folder (it's easier to find all files in the same folder).
Prerequisite: Your Nexus 7 LTE should be running Android 4.4.2 (KOT49H) or (KVT49L -for Verizon). You will not lose your data using this method
Step 1.
Download the update zip
=> Download link for almost of users => cac1a204d3770a20fdce28f6ed3418fdd36abd5d.signed-razorg-KTU84L-from-KOT49H.cac1a204.zip - md5: 34adc31c6647de18547c405133072381
=> Download link for Verizon users => f0c2187ff1dba772cff3fa7f99f0e6bd38ecb62b.signed-razorg-KTU84L-from-KVT49L.f0c2187f.zip - md5: 663b29478d60babb2f0cbb6fc506f111
Charge your Nexus 7 to at least 60% battery level
Don't forget to enable USB debugging
Don't forget - Backup your tab’s storage,
you can choose to change the file’s name to ‘update.zip’. take care
Be sure to read the instructions and carry on...
Step 2.
Reboot your Nexus 7 LTE and hold the Vol+Down button while it's booting up.
Once you see the fastboot menu and the word Start, press Vol+Up a few times until you see Recovery and then press the Power button to enter recovery
You will see an Android with a red exclamation point.if you have stock recovery
Now press Vol+Up+Power together, and you should see the menu below:
Select the 2nd option called apply update from adb.
Step 3.
Connect your Nexus 7 LTE to your computer with your USB cable.
Make sure you have a recent version of adb that supports the sideload command (if you don't, download the latest Android SDK to ensure your adb is up-to-date).
Place the update.zip package from Google in the Android SDK/platform-tools folder on your computer, but do not unzip it. And open up a command prompt
(cmd in Windows)
(regular shell in Linux and Mac) in the same directory as the zip file.
and type
Code:
adb sideload <the name of the zip file that you've done>.zip
if you have changed the name of the update file to ‘update.zip’, then enter: adb sideload update.zip
You should see the progress bar go up to 100%, like so:
sending: 'sideload' 100%
Click to expand...
Click to collapse
At this point, the device should have started installing the update 4.4.3 OTA :victory:
Step 4.
Reboot - you're done.
Enjoy Android 4.4.3 on your Nexus 7 LTE... we just need to waiting the next release for KK4.4.4
Just in case
Reserved for me
Is this zip compatible with TWRP? I tried flashing the zip but it failed, and I did verify the md5 checksum was correct.
Hizpanick said:
Is this zip compatible with TWRP? I tried flashing the zip but it failed, and I did verify the md5 checksum was correct.
Click to expand...
Click to collapse
I've tried before to install my OTA update and the install is failed. I'm with TWRP also
That's why I'll edit my OP without this process. I have rename the zip file to update.zip
For info I have this result:
Code:
- verifying current system
"/system/bin/debuggerd" has unexpected contents
E:Error executing updater binary in zip '/sdcard/update.zip
Error flashing sip '/sdcard/update.zip
Updating partition details
So if you haven't received the OTA update for 4.4.3, use the adb sideload process.
So I tired with the adb sideload process, and still get the same failure:
"/system/bin/app_process" has unexpected contents.
E: Error executing updater binary in zip "/data/media" (looks like it cuts off at this point)
Since I have TWRP, I used adb sideload by going to Advanced ->Adb sodeload and then swiping to turn on adb sideload. My ADB version is 1.0.31, and the file did copy succesfully.
EDIT: Maybe this doesn't work for me because I'm stock rooted?
Hizpanick said:
So I tired with the adb sideload process, and still get the same failure:
"/system/bin/app_process" has unexpected contents.
E: Error executing updater binary in zip "/data/media" (looks like it cuts off at this point)
Since I have TWRP, I used adb sideload by going to Advanced ->Adb sodeload and then swiping to turn on adb sideload. My ADB version is 1.0.31, and the file did copy succesfully.
EDIT: Maybe this doesn't work for me because I'm stock rooted?
Click to expand...
Click to collapse
I haven't been able to get this to install either. Does root or custom recovery cause the installation to fail?
Sent from my Nexus 7 using Tapatalk
i am getting a status 7 error in /tmp/update.zip
help?
I don't know exactly what is the problem. I've used this process for updating my N7.
After the flash with adb sideload, I am back completely stock, unlocked, rooted but stock recovery, not twrp.
Sent from my N7 LTE from XDA Assist and use TapatalkPro
So I found out why I was getting my particular error and it was because I had Xposed framework installed. I uninstalled that and was able to flash the OTA. However, I lost root, but kept TWRP. So I flashed the updated SuperSU.zip (http://www.androidfilehost.com/?fid=23501681358555830) and I had root back. Re-installed Xposed Framework and now everything is updated and working
So you got the update to flash in twrp?
I uninstalled xposed and it still doesn't work with stock recovery and kernel. Got too much setup to redo it all
Sent from my SCH-I605 using Tapatalk
worked for me.