Hi,
Following on from this thread I'm trying to get back to stock rom.
Each time I attempt to flash from (stock) recovery I get
check.partition.size=[__PROP_UNDEFINED__]
Installation aborted
I've tried CUS1 and GEN1 roms from Acer site both with and without the 1st line of the script commented out.
Any ideas?
Clumzie said:
Hi,
Following on from this thread I'm trying to get back to stock rom.
Each time I attempt to flash from (stock) recovery I get
check.partition.size=[__PROP_UNDEFINED__]
Installation aborted
I've tried CUS1 and GEN1 roms from Acer site both with and without the 1st line of the script commented out.
Any ideas?
Click to expand...
Click to collapse
OK, is there another way I can approach this as I need to get back before sending the tablet off to be fixed.
1) Can I push the ROM somehow using adb? If so, how?
2) What about installing CWM to flash the ROM and restore custom recovery? This would be my last resort as if it didn't work I'm stuck with root files & CWM!
Any help gratefully received as I need to send it back this week.
First off, I have some questions:
1. Are you unlocked?
2. Are you root? (Doesnt really matter)
3. Android 4.0 or 4.1?
4. At which point is that error showing up?
5. What about the stock beta ROMs?
6. Did you rename the ROM to update.zip and to what place did you copy it ?
http://forum.xda-developers.com/showpost.php?p=34015330&postcount=108
Somebody had the same problem. Im not sure about the solution though.
You can boot into a different recovery (since the message youre gettin' is from the stock recovery).
Search the forum for cwm. Then use fastboot boot recovery-nameoffile.img
It requires an unlocked bootloader.
1: You can, if you are able to boot into Android. If you can't, adb will not work.
To push a file to your tablet, use the following commands:
adb push update.zip /sdcard
Update.zip being the stock ROM, obviously.
2: Yes. That could work. Try to install CWM and you should be able to flash a stock ROM from this thread:
http://forum.xda-developers.com/showthread.php?t=1729692
However, you should be able to flash that ROM already. Remember you have to unlock your device. You can, however lock it again by installing a stock ROM; but I heard it will unlock itself after an OTA or flashing another stock ROM or something like that.
TomONeill said:
First off, I have some questions:
1. Are you unlocked? No
2. Are you root? (Doesnt really matter) Root files (su and busybox) but not superuser.apk due to JB OTA
3. Android 4.0 or 4.1? 4.1.2
4. At which point is that error showing up? After Finding/opening/verifying package
5. What about the stock beta ROMs? No, just the 2 official ones on the Acer site
6. Did you rename the ROM to update.zip and to what place did you copy it ? The downloaded files from ACER are a zip file with a pdf and update.zip inside. I copied update.zip to my SD card. Am I supposed to extract a particular file from it and create an archive out of that that or use the entire thing as I did?
http://forum.xda-developers.com/showpost.php?p=34015330&postcount=108
Somebody had the same problem. Im not sure about the solution though.
You can boot into a different recovery (since the message youre gettin' is from the stock recovery).
Search the forum for cwm. Then use fastboot boot recovery-nameoffile.img
It requires an unlocked bootloader.
1: You can, if you are able to boot into Android. If you can't, adb will not work.
To push a file to your tablet, use the following commands:
adb push update.zip /sdcard
Update.zip being the stock ROM, obviously.
/system/bin/sh: push: not found
2: Yes. That could work. Try to install CWM and you should be able to flash a stock ROM from this thread:
http://forum.xda-developers.com/showthread.php?t=1729692
However, you should be able to flash that ROM already. Remember you have to unlock your device. You can, however lock it again by installing a stock ROM; but I heard it will unlock itself after an OTA or flashing another stock ROM or something like that.
Click to expand...
Click to collapse
I'm a bit hesitant about installing CWM as I'm not convinced I won't encounter the same problems as I did with stock recovery.
Thanks again Tom
TomONeill said:
First off, I have some questions:
1. Are you unlocked?
2. Are you root? (Doesnt really matter)
3. Android 4.0 or 4.1?
4. At which point is that error showing up?
5. What about the stock beta ROMs?
6. Did you rename the ROM to update.zip and to what place did you copy it ?
http://forum.xda-developers.com/showpost.php?p=34015330&postcount=108
Somebody had the same problem. Im not sure about the solution though.
You can boot into a different recovery (since the message youre gettin' is from the stock recovery).
Search the forum for cwm. Then use fastboot boot recovery-nameoffile.img
It requires an unlocked bootloader.
1: You can, if you are able to boot into Android. If you can't, adb will not work.
To push a file to your tablet, use the following commands:
adb push update.zip /sdcard
Update.zip being the stock ROM, obviously.
2: Yes. That could work. Try to install CWM and you should be able to flash a stock ROM from this thread:
http://forum.xda-developers.com/showthread.php?t=1729692
However, you should be able to flash that ROM already. Remember you have to unlock your device. You can, however lock it again by installing a stock ROM; but I heard it will unlock itself after an OTA or flashing another stock ROM or something like that.
Click to expand...
Click to collapse
Hi I have question. If my phone USB can't working with PC anymore because the terminal cut out and my Gionee e3 phone stuck on boot logo or bootloop, how can I get it back to normal? Is there a flashable zip files can solve it? If there was please help me. Thanks.
Hey cryingbee,
Can't you get to the recoverymode by pressing volume down and the power button? If not, try booting into fastboot, which I think is volume up + the power button. If those combinations won't work, google for your phone name + fastboot mode. If you can reach fastboot, you can boot into a recovery by using fastboot commands or install new roms etc.
Related
I'm having trouble getting back to a regular non locked down firmware. I flashed whispercore without fully understanding that it was actually in fact changing my entire rom.
I didnt even think to try and install CWM first to create a recovery image I need help getting out of this mess. I've used the Whispercore installer to unlock fastboot because whispercore relocks your fastboot after it does its thing.
Seems as though the stock sdk tools hated me for a while there and wouldnt detect my device than I later realised it was just because the sdk downloads itself all fragmented it basically took fastboot and adb and separated the two even though fastboot requires adb to function properly. I wont even begin to speculate as to why that happened, as thats beyond the scope of my question.
I basically have gotten to the point where i have Clock work mod (CWM) installed on my droid and the fastboot oem unlocked but am currently stuck at trying to get Cyanogenmod 7 stable on here.
***UPDATE**
Ok. This situation has been resolved. If you are having trouble with leaving whisper core and you've flashed a bunch of stuff trying desperately trying to fix this issue. Recognize the nexus S is a very easy device to fix. Fastboot is your saviour and the WhisperCore installer will even be kind enough to install all the drivers required to OEM unlock fastboot and do it for you.
Anyways the solution was: Re run the whispercore installer. Let it do its automagic.
Than flash a new Clockwork Mod recovery image this thread provided some clean Clockwork Mod images for flashing with fastboot that link is also for rooting but provides a good example for how to flash a new recovery.
Than Just reboot into recovery and use it to mount your phone via the Clockwork Mod recovery console to your computer, upload your favorite flavor of rom and than unmount the device. Once unmounted go back to the main menu in Clockwork mod and "Flash zip from SD" look for your rom in my case it was update-cm-7.0.3-NS-signed.zip Latest stable at the time. let it do its job.
Basically my issue was a combination of several factors. A bad Clockwork mod and a semi corrupt installation of SDK tools and Whispercore.
Possibly a stock firmware might be required first I just know that trying to straight flash cm7 stable from cwm is not working out.
you can get adb and the 2 dll files and fastboot in the same folder and cd to that directory. fastboot oem unlock should unlock your bootloader. then you should be able to flash a recovery if you want. might also want to check out the 1 click stock thread to see if that works.
I will probably have trouble finding this thread but I will look and if i come up with anything I will certainly post my findings.
This should work. But we shall see I will update the original post if I find a full solution.
Just flash a stock full rom (for i9023 you can use the one in my signature, don't forget get to use the wipe options in cwm recovery before) and the root should be gone. Afterwards, boot into bootloader and use fastboot command "fastboot oem lock" to lock the bootloader again. Than you can do a factory reset (and delete usb storage) to fully restore stock "experience".
__________________
Nexus S running Official 2.3.4 ROM (for i9023) with XTEUV92 Trinity kernel
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1214705&highlight=one+click+stock
I'm getting an error in the zip files no matter what one I use and its "Status 7" whatever that means.
chamunks said:
***UPDATE**
Ok. This situation has been resolved. If you are having trouble with leaving whisper core and you've flashed a bunch of stuff trying desperately trying to fix this issue. Recognize the nexus S is a very easy device to fix. Fastboot is your saviour and the WhisperCore installer will even be kind enough to install all the drivers required to OEM unlock fastboot and do it for you.
Anyways the solution was: Re run the whispercore installer. Let it do its automagic.
Than flash a new Clockwork Mod recovery image this thread provided some clean Clockwork Mod images for flashing with fastboot that link is also for rooting but provides a good example for how to flash a new recovery.
Than Just reboot into recovery and use it to mount your phone via the Clockwork Mod recovery console to your computer, upload your favorite flavor of rom and than unmount the device. Once unmounted go back to the main menu in Clockwork mod and "Flash zip from SD" look for your rom in my case it was update-cm-7.0.3-NS-signed.zip Latest stable at the time. let it do its job.
Basically my issue was a combination of several factors. A bad Clockwork mod and a semi corrupt installation of SDK tools and Whispercore.
Click to expand...
Click to collapse
I am trying to follow what you did and i am completely lost... I have a nexus s g that i am trying to get whispercore off it!
The "Automagic" you talk about. Isnt that just whispercore putting it in fast boot??? If so then then how do you use the recover image?
(Method 1)
Ok so you're trying to put this really cool new custom ROM on your phone and then suddenly, your phone won't start up or go to recovery… well my friends, you have got yourself a bricked phone. The thing you worry about the entire time you're rooting, and flashing your phone, has now become reality. Well, fear no more, for I, have found a way to unbrick your device! after bricking my phone and finding different ways how to do it...
Because we are not able to swap or get the sdcard out from the phone, it makes it difficult on how to add a ROM.zip and re-install. Another issue I found is that CWM will not be able to read the sdcard if you do an adb push ROM.zip /sdcard/ROM.zip or by mounting the sdcard adb shell mount /sdcard . If you have this issue will explain later
So let's get started.
Step 1: Turning Off Your Phone and Reboot to Boot-Loader
Because you have a bricked phone, you can't just hold the power button. So if your phone is not already off then you're going to want to turn off by pressing the volume down + power button until the phone shuts off then turn on to boot-loader by pressing volume down and press for 3 seconds the power button. once in boot-loader select fastboot.
Step 2: Adb push to SD card
I assume that you have install CWM, if you don't you can download it from HERE. Once downloaded install CWM fastboot flash recovery CWM.TOUCH.5.8.3.1.img, where your done go back to boot-loader and select recovery. Once in recovery do an adb push of a ROM, in this example I used "Energy ROM" you can get the ROM from HERE. Once you have your ROM rename ROM.zip and push adb push ROM.zip /sdcard/ROM.zip, you will get a message stating the size of the the push.
If you can't do a push because you got an error message will explain later.
Step 3: Wipe The Phone
Make sure to do a Factory Reset / Wipe before installing ROM
Step 4: Reboot back to fastboot
Once you install the room you will need to make sure you have a boot.img for the ROM your using.
adb reboot bootloader
fastboot flash boot Recoveries/boot.img
YOUR DONE
If your the unlucky one's that can't do an adb push to the SD card do the following.
- Reinstall STOCK Recovery fastboot flash recovery recovery.img
- Lock OEM fastboot oem lock
- Unlock OEM fastboot flash unlocktoken Unlock/Unlock_code.bin
- Reinstall CWM Recovery fastboot flash recovery CWM.TOUCH.5.8.3.1.img
That should fix the problem on how to push back to the sdcard
If you have other methods post them below...
Sticky!!
But this won't work if you flash a wrong radio, will it? I thought that if you flashed a wrong radio, you couldn't get anything done, even not booting into bootloader, because it boots the radio first?
I'll second that this method works. Did for me and is easy to do once you take your time. Also make sure you have all the right files and you make sure to type everything word for word in ADB..
This tutorial already exists as a sticky in the Q&A section:
http://forum.xda-developers.com/showthread.php?t=1630459
Sent from my HTC VLE_U using Tapatalk 2
Nice writeup.
For every new Phone I own, the first thing I do after flashing a Custom Recovery is Making a Nandroid Backup of the stock Rom. If something goes wrong after flashing a bad rom I just restore to Stock rom.
A real life Saver for me.
snwman said:
I'll second that this method works. Did for me and is easy to do once you take your time. Also make sure you have all the right files and you make sure to type everything word for word in ADB..
Click to expand...
Click to collapse
It worked for me when I bricked my phone and had to find ways how to be able to load a ROM back to the SDcard and reflash it...
This is a combo of a tutorial cannondale wrote and one I wrote myself.
His is stickied in Q&A section, mine is in Android Dev section...
Not sure why this is here lol.
i get the error 155 when trying to install the RUU
420haxr said:
i get the error 155 when trying to install the RUU
Click to expand...
Click to collapse
Try to relock your bootloader first.
In fastboot:
fastboot oem lock
Sent from my HTC One S
Issue
Ok, still running into an issue. No errors when I push, I locked, unlocked, tried everything again. Reset everything, installed fresh CWM, tried it all over...
What's happening is that it's saying it pushed the file over, but I can't find it anywhere after it's done. This happened the first time I installed custom...I just can't remember what I did to get it to work...
Anyone has the link of stock recovery for HTC One S z560e(ville c2)?? i get error 155 when i try to install with RUU.
After i flash the cwm touch recovery I cant boot into recovery... my phone is stuck on the HTC boot logo with the red text underneath. Is it a problem with recovery or should i try install an RUU. My phone is HTC One S villec2 (S3).
I was able to install TWRP and unlocc bootloader and root. I tried installing PAC-man_23.0.0 wiped and now the tablet will not boot passed the splash screen. I can still get to recovery with no problems. I can't access any sdcards in recovery to try to flash any other roms.
Zaiaku said:
I was able to install TWRP and unlocc bootloader and root. I tried installing PAC-man_23.0.0 wiped and now the tablet will not boot passed the splash screen. I can still get to recovery with no problems. I can't access any sdcards in recovery to try to flash any other roms.
Click to expand...
Click to collapse
We need more details
What firmware were you on before you tried pacman?(it requires 4.1) if it was me id adb push the latest stock firmware from Asus (the package has a .zip inside a .zip so extract it once and use the second .zip)
There are plenty of guides for using adb push, google it
Make sure you have the right version of twrp for your bootloader, if not replace it with fastboot.
JoinTheRealms said:
We need more details
What firmware were you on before you tried pacman?(it requires 4.1) if it was me id adb push the latest stock firmware from Asus (the package has a .zip inside a .zip so extract it once and use the second .zip)
There are plenty of guides for using adb push, google it
Make sure you have the right version of twrp for your bootloader, if not replace it with fastboot.
Click to expand...
Click to collapse
That's proably what I did was get the wrong version some how. was able to flash another recovery now that I have access to sdcard I was able to reload another softare so atleast I'm good now.
So I flash the stock rom on it without thinking and now it wont let me flash a recovery to the tablet threw fastboot or goomanager and it wont update throguh asus update but its booting fine and wont take any updates at all i need help being pointed in the right direction!
I flashed the wrong bootloader i think and how do i flash the correct bootloader without a recover?
in fastboot im getting the error: cannot load 'file name' :no error weather its cm or twrp it wont load it and i dont know what to do please help
First of all it would be important to know what bootloader you are actually on. You do not want to flash a recovery that is not compatible with your bootloader!
So boot into the bootloader with Volume Down and POWER and read the tiny script. From there select the Android with Volume Down and boot back to system with Volume Up.
And then please report in detail what you are trying to do in fastboot, which commands you use etc.
Without knowing what you are doing we cannot tell you what you are doing wrong.....
First step: In fastboot command: fastboot devices - Do you see the serial number of your tab?
berndblb said:
First of all it would be important to know what bootloader you are actually on. You do not want to flash a recovery that is not compatible with your bootloader!
So boot into the bootloader with Volume Down and POWER and read the tiny script. From there select the Android with Volume Down and boot back to system with Volume Up.
And then please report in detail what you are trying to do in fastboot, which commands you use etc.
Without knowing what you are doing we cannot tell you what you are doing wrong.....
First step: In fastboot command: fastboot devices - Do you see the serial number of your tab?
Click to expand...
Click to collapse
bootloader version is us_epad-10.4.4.20-20121026
with a stock rom of 4.1.1
and trying to undo the rom cause im trying to put a stock 4.2.2 on it to get the drivers back on it from the stock rom.
in fastboot i just need to get a twrp installed and i can undo my mess
Skittleskitty said:
bootloader version is us_epad-10.4.4.20-20121026
with a stock rom of 4.1.1
and trying to undo the rom cause im trying to put a stock 4.2.2 on it to get the drivers back on it from the stock rom.
in fastboot i just need to get a twrp installed and i can undo my mess
Click to expand...
Click to collapse
So you are on an ICS bootloader with a JB rom... How the hell did you manage to do that?
You did not answer my question about fastboot. What you tried and what did not work.
But anyway, how I would proceed, just to get you back into safe territory, is to download the latest Asus firmware 10.6.1.14.10, unzip the downloaded file once and copy the resulting zip to the root of your internal SD.
Reboot, and hopefully the stock recovery will recognize the update file and flash you to JB 4.2.1 (which BTW is the latest version for our tabs - there never was, and probably never will be a 4.2.2). Flashing the stock firmware will replace the bootloader.
So from there you just have to get fastboot working, flash the latest TWRP and then the custom rom of your choice COMPATIBLE with your bootloader and recovery.
If that doesn't work we have to try something else. But try this first and report.
berndblb said:
So you are on an ICS bootloader with a JB rom... How the hell did you manage to do that?
You did not answer my question about fastboot. What you tried and what did not work.
But anyway, how I would proceed, just to get you back into safe territory, is to download the latest Asus firmware 10.6.1.14.10, unzip the downloaded file once and copy the resulting zip to the root of your internal SD.
Reboot, and hopefully the stock recovery will recognize the update file and flash you to JB 4.2.1 (which BTW is the latest version for our tabs - there never was, and probably never will be a 4.2.2). Flashing the stock firmware will replace the bootloader.
So from there you just have to get fastboot working, flash the latest TWRP and then the custom rom of your choice COMPATIBLE with your bootloader and recovery.
If that doesn't work we have to try something else. But try this first and report.
Click to expand...
Click to collapse
thank you so much that fixed it!!
ok i did all that but it removed fastboot what do i do to get it back?
Skittleskitty said:
ok i did all that but it removed fastboot what do i do to get it back?
Click to expand...
Click to collapse
Read the text in the upper left corner - current bootloaders enable fastboot in the bootloader menu automatically.
ok i got fastboot working and now it says when i got to flash the recovery it says error cannot open twrp.blob even though its the correct file.
Skittleskitty said:
ok i got fastboot working and now it says when i got to flash the recovery it says error cannot open twrp.blob even though its the correct file.
Click to expand...
Click to collapse
Then maybe it's not in your current directory.
Skittleskitty said:
ok i got fastboot working and now it says when i got to flash the recovery it says error cannot open twrp.blob even though its the correct file.
Click to expand...
Click to collapse
I think your tablet would be a lot safer if you did some reading here: http://lmgtfy.com/?q=fastboot+tutorial
berndblb said:
I think your tablet would be a lot safer if you did some reading here: http://lmgtfy.com/?q=fastboot+tutorial
Click to expand...
Click to collapse
i found that and have been reading it but fastboot still cant read the twrp.blob even though its in the directory with fastboot.
ok ive re installed fastboot and adb sdk and did the environment variable path and it still wont recognize the blob it wont recognize cwm .img files ether and what does key driver not found..booting os
Skittleskitty said:
i found that and have been reading it but fastboot still cant read the twrp.blob even though its in the directory with fastboot.
Click to expand...
Click to collapse
It has to be in your *current* directory.
_that said:
It has to be in your *current* directory.
Click to expand...
Click to collapse
thankyou it moved directorys on me that was the issue
So looks like I deleted my android files...................... yes kill me!!!
How it stands:
Im not able to load into Android. The tablet is Unlocked and able to only boot to twrp.
2 out 10 times im able to push a file trought. The other times I get a protocol failure.
I can adb push files but at this point I dont know what files to push. What rom or what do I need to push to get it back?
I also think I lost root since I got a msg from twrp that if I wanted to install something to get root back.....
Riken said:
So looks like I deleted my android files...................... yes kill me!!!
How it stands:
Im not able to load into Android. The tablet is Unlocked and able to only boot to twrp.
2 out 10 times im able to push a file trought. The other times I get a protocol failure.
I can adb push files but at this point I dont know what files to push. What rom or what do I need to push to get it back?
I also think I lost root since I got a msg from twrp that if I wanted to install something to get root back.....
Click to expand...
Click to collapse
Use fastboot to install you stock ROM again. Dont use adb push, you can install it from your computer. Then install the correct TWRP for your bootloader and get back to your favorite custom Rom
how do I use fastboot? Is there a guide to use fastboot? Im searching lol Where can I get the stock rom?
Can I use a stock rom with twrp recovery?
Also for stock rom, its says to use the right rom with my SKU version. But I cant boot to find the sku....
Riken said:
how do I use fastboot? Is there a guide to use fastboot? Im searching lol Where can I get the stock rom?
Can I use a stock rom with twrp recovery?
Also for stock rom, its says to use the right rom with my SKU version. But I cant boot to find the sku....
Click to expand...
Click to collapse
When you restart you device and go to the recovery menu, and the top left corner where it says the device is unlocked, there will be the bootloader version. You need that to install the correct TWRP and stock ROM for your device.
When you get that stock ROM, take the stock ROM, extract the *.blob file. Copy that to your fastboot folder.
Restart your tablet and go to fastboot.
Now in CMD, type:
Code:
fastboot -i 0x0B05 flash system blob.blob
It will take about ~300 seconds if you did it right.
You can find the stock ROMs in the index thread in developer forum.