I owned and rooted a NS4G last year without an issue.
I've got a Mac now, and just got a new NS4G and tried rooting it.
I was able to unlock the bootloader via adb commands in Terminal. But when I try to flash a recovery using
Code:
~/Desktop/adb-fastboot/fastboot flash recovery.img
I get
Code:
unknown partition 'recovery.img'
error: cannot determine image filename for 'recovery.img'
I get the same error if the file is named twrp-crespo4g-2.0.0RC0.img or whatever. Either that "cannot determine..." or "unable to load".
So I can't get superuser because I don't have a recovery. In Rom Manager, it gives me an error cannot flash recovery or what not.
I'm presently stuck.
Nevermind. After some fiddling I realized I was typing in the wrong file name in the first place.
Amateurs.
Related
Hello everybody,
Before telling you about my issue, i should mention that i am a complete newbie regarding flashing kernels. This was my first try, and it didn't work out too well.
I needed to test the USB OTG/Host Functionality for a project at work, and i read that it was possible to enable it on the Nexus S by flashing a custom kernel (kernel_usbhost_build5_icsnexuss from sztupy). It's probably worth mentioning that prior to this i updated the phone to Android 4.0.3.
So i started this morning by rooting it, unlocking the bootloader and installing CWM.
At that point i realized that the recovery mode wasn't accessible : the graphics of the droid with an open belly appears for half a second, and then it gives me the black screen treatment for about a minute before rebooting.
However since there are other ways to flash kernels, i figured i could do without recovery so i didn't look more into it.
I then flashed the kernel using fastboot with this command :
Code:
C:\Program Files\Android\android-sdk\tools>fastboot flash:raw boot H:\data\Downloads\kernel_usbhost_build5_icsnexuss\kernel\zImage
creating boot image...
creating boot image - 3446784 bytes
sending 'boot' (3366 KB)...
OKAY [ 0.422s]
writing 'boot'...
OKAY [ 0.500s]
finished. total time: 0.922s
From the trace i figured that all went well, but when i reboot it stays blocked on the splash screen with the Google logo. Since then i tried flashing several other kernels, without any success. Also tried to flash an update.zip (both ICS and GB) over fastboot but i get this error :
Code:
C:\Program Files\Android\android-sdk\tools>fastboot update H:\data\Downloads\upd
ate.zip
archive does not contain 'android-info.txt'
archive does not contain 'android-product.txt'
error: update package has no android-info.txt or android-product.txt
So to sum it up i now only have access to the bootloader, without recovery mode.
Before you all jump on me, i know what i did is bad habits (i should have tested the kernel before flashing it), i did it in a hurry without checking i had all sufficient knowledge, and to be honest i would probably have been more careful if was doing it on my personal device.
Truth is now i'm really desperate because i turned my company issued phone into a brick and don't have the slightest idea what to do about it...
Is there any guru out there who knows how i could get out of this ?
Thanks a lot !
Download clockworkmod recovery and use fastboot to flash it.
Fastboot flash recovery yourfilename.img
Enter recovery and mounts and storage and mount USB storage
Transfer the kernel you want to your SD card. The one you flashes isn't a kernel I'm almost sure.
Try a different one.
Then transfer a rom to your SD card.
Factory reset/full wipe, then go to mounts and storage and format everything except your sdcard.
DO NOT FORMAT YOUR SD CARD!!!
Once that is done go to install zip from sdcard and flash the rom and then the kernel and reboot. Should be fine then. Keep me posted.
..
Election Day said:
The image you need would be this ClockworkMod img. Save it somewhere, cd to the sdk/platform-tools/ directory and then do:
Code:
fastboot flash recovery /path/to/saved/file/recovery-clockwork-5.0.2.0-crespo.img
Just drag and drop the file in your terminal, after typing the space after "recovery".
Furthermore, what nodstuff said.
Click to expand...
Click to collapse
Ha ha oops! Forgot that part!
I usually just cd to the one where I have recovery saved!
..
Thanks a lot for answering so quickly !
I'll give it a try on Monday, let you know how it goes.
Election Day said:
Yes, you can also do that, of course. In that case you'd have to provide the full path for fastboot. Or maybe you don't have to on Windows? I don't really use that operating system to be honest.
In that case it would be something like:
Code:
C:\Program Files\Android\android-sdk\tools\fastboot flash recovery recovery-clockwork-5.0.2.0-crespo.img
Looking at OP's quotes that is probably the most logical way in this case, you're right.
Click to expand...
Click to collapse
No I just cd to downloads (where recovery file would be) in terminal, type: fastboot flash recovery xxxxxx img
And that's it.
I set the path to fast boot and adb in environmental variables in device manager.
Maybe that's why.
..
Just tried out your tips, worked like a charm !
However I had to wipe everything twice before it would let me update to 4.0.3, I would get this weird error :
file_getprop: failed to stat "/system/build.prop": No such file or directory
Anyway now I'm back on ICS and, following your advice, i found another kernel to flash : Matr1x. No problem with this one, now I can test USB OTG.
Thanks again, you guys rule !
So I managed to successfully soft brick my one xl with rogers after I tried the Debranding method explained by JSLEnterprises, while we wait for a CWM recovery that might help me I need some help getting my phone working. So far fastboot is useless (on a mac) when I try to fastboot update to JSLEnterprises's rogers ruu.zip I get all this
Whoops: didn't find expected signature
read_central_directory_entry failed
error: failed to access zipdata in '??K?WY-??/?>?*{??
??#/????mGFb?-=?f?qxg??|*??)???y?ftm???>?66?-#???????$???:̇+_??????????Z?~???>??fe?o?/?`?O?B??A??xa_?&???+{]?W???G
??Άֽ???0??)
??
?K???ڷ[?v-i
XrOW??7 ?l????ր?z??9'?'??R??y???-?:?????W|???>??
??????? ?_?)?VC?--???B?o???<Xa??Z8 ????_x??vo????????ԟ6p???
c{~?~??j???Js?a???0????????`??
??>?[.씄C쿨덻
?',`?~??o??ѱ3?x??P?6v?
?:???!?X?,"K???S??=x?\??M
;sO#L~?Eh?p????/??f?²}?آ?u?!??
I have also tried extracting the system.img boot_signed.img and recovery (just for kicks) and tried flashing those individually. The system.img just wouldn't flash,
sending 'system' (1048572 KB)... FAILED (remote: data length is too large)
boot and recovery send and write just fine.
I tried extracting the contents of my zip with the only program I could find that could open said zip, (all others would say it was invalid) and then rezipped it, when I try to flash that I get it telling me that no boot.img was found, thats fair cuz its named boot_signed, I open the zip, rename all the *_signed.img to just *.img and it goes fine with the exeptions that no .sig files are there and system.img is too large.
Whenever I go to my recovery and try to factory reset, I get errors at first about how it cant mount /data/data/recovery/log, but the factory reset gives me
Formatting /data
cant't mount /data
and then cant' mount all sorts of locations in the /cache
then formatting /cache
wipe complete
trying to apply and update from either internal, external or cache seems to fail and make my phone reboot
I have also tried the windows at&t ruu, every one out there the 1.52, 1.68 even 1.44 but no luck. I did JSLEnterprises trick of replacing rom.zip with the rogers.zip but I get error 155 and my phone gets stuck at a black screen with chrome htc letters until i reboot it. Is there anything else you guys could suggest that would help since I contacted the fellow who is working on a CWM port and he informed me that mounting the "sdcard" wont be possible right away.
Somebody help!
Hi All,
I'm trying to push ROM file to sdcard through adb shell, but when I typing adb shell it gives me "device not found"
However in device manager I can see that the Asus is connected with "Interface bootloader"
So I tried to flash the ROM with fastboot,but when I trying to update the ROM I'm getting following error:
archive does not contain 'android-info.txt'
archive does not contain 'android-product.txt'
error: update package has no android-info.txt or android-product.txt
I'm trying to push the ROM with adb since I wipe all my data.
Please advice.
Thanks in advance,
vadella said:
Hi All,
I'm trying to push ROM file to sdcard through adb shell, but when I typing adb shell it gives me "device not found"
However in device manager I can see that the Asus is connected with "Interface bootloader"
So I tried to flash the ROM with fastboot,but when I trying to update the ROM I'm getting following error:
archive does not contain 'android-info.txt'
archive does not contain 'android-product.txt'
error: update package has no android-info.txt or android-product.txt
I'm trying to push the ROM with adb since I wipe all my data.
Please advice.
Thanks in advance,
Click to expand...
Click to collapse
OK,I have solved the issue.By replacing ADB drivers.
Regarding the archive errors,probably these errors derives from incorrect ROM file.
Glad you got it working. I had USB issues on my computer earlier keeping me from upgrading. Stay safe over there! שלום!
Hi all
Have a problem with a boot loop.
First, my story:
I rooted the tablet and installed Rouge recovery using the "one click root" from here: http://forum.xda-developers.com/showthread.php?t=1689193
That worked and I installed CM9
What I didn't do was to make a back-up before I had installed CM9.
I want to give the tablet away to a young relative and install the original firmware on it and removing root.
I downloaded from ASUS the WW_epad-user-9.2.1.27.zip file which was the latest firmware for the device.
When I went to flash it however I got the following error
assert failed: write_raw_image("/tmp/blob", "staging")
E:Error in /sdcard/US_epad-user-9.2.1.11.zip
(status 7)
Installation aborted.
So I did the following fix found here (http://forum.xda-developers.com/showthread.php?t=1576937)
- download the img file
- rename it as blob file with a more simple name for example cwm_touch.blob
- open Terminal Emulator on your tablet, then:
$ su
# dd if=/"path to blobfile" of=/dev/block/mmcblk0p4 (REPLACE "path to blobfile" with the path to where you have saved the file).
Now here's the problem, I restarted the device and it goes into a boot loop, trying to access the recovery (Power + Volume) It goes to an android with a red triangle and nothing else. So I'm stuck, I can't recover and I can't access the device on my computer.
What do I do?
Wedge85 said:
Hi all
Have a problem with a boot loop.
First, my story:
I rooted the tablet and installed Rouge recovery using the "one click root" from here: http://forum.xda-developers.com/showthread.php?t=1689193
That worked and I installed CM9
What I didn't do was to make a back-up before I had installed CM9.
I want to give the tablet away to a young relative and install the original firmware on it and removing root.
I downloaded from ASUS the WW_epad-user-9.2.1.27.zip file which was the latest firmware for the device.
When I went to flash it however I got the following error
assert failed: write_raw_image("/tmp/blob", "staging")
E:Error in /sdcard/US_epad-user-9.2.1.11.zip
(status 7)
Installation aborted.
So I did the following fix found here (http://forum.xda-developers.com/showthread.php?t=1576937)
- download the img file
- rename it as blob file with a more simple name for example cwm_touch.blob
- open Terminal Emulator on your tablet, then:
$ su
# dd if=/"path to blobfile" of=/dev/block/mmcblk0p4 (REPLACE "path to blobfile" with the path to where you have saved the file).
Now here's the problem, I restarted the device and it goes into a boot loop, trying to access the recovery (Power + Volume) It goes to an android with a red triangle and nothing else. So I'm stuck, I can't recover and I can't access the device on my computer.
What do I do?
Click to expand...
Click to collapse
EDIT:
Well after banging my head on a wall for a few hours, I found a solution.
http://www.transformerforums.com/fo...t/31927-frederuco-s-guide-root-rom-tf101.html
This has allowed me to get back a recovery and I have installed CM9 back again.
I'm still stumped as to how to return the device back to stock..
Wedge85 said:
EDIT:
Well after banging my head on a wall for a few hours, I found a solution.
http://www.transformerforums.com/fo...t/31927-frederuco-s-guide-root-rom-tf101.html
This has allowed me to get back a recovery and I have installed CM9 back again.
I'm still stumped as to how to return the device back to stock..
Click to expand...
Click to collapse
Why not just put ARHD on it and remove/uninstall super user app...... will work a fair bit better but still have all the stock Asus bits. There wont (i suspect) be any more updates for our TF so ARHD would be just the ticket imo.
Hello everyone,
i just wantet to wipe my old OPO to give it to my son. But in the process i accidently wiped the system partition and are now without any working phone.
i tried to flash an image via recovery and via fastboot. Both without success.
I downloaded a fastboot flashable rom from here but after flashing the system.img the phone still wont boot.
tried to flash boot.img as well but i get this error:
Code:
fastboot: core/libsparse/sparse.cpp:131: int write_all_blocks(struct sparse_file *, struct output_file *): Assertion `pad >= 0' failed.
when i try to flash the regular .zip from the oneplus page i get an error: This package is for: bacon,A0001 This Device is .
I tried to flash via adb sideload and pushed the file via adb push on the phone, but same error.
any suggestions how to save my good old ONE to give it a second live in the hands of my son?
Do you have a nandroid backup yo restore? That should fix it if you have access to recovery
patlabor said:
Hello everyone,
i just wantet to wipe my old OPO to give it to my son. But in the process i accidently wiped the system partition and are now without any working phone.
i tried to flash an image via recovery and via fastboot. Both without success.
I downloaded a fastboot flashable rom from here but after flashing the system.img the phone still wont boot.
tried to flash boot.img as well but i get this error:
Code:
fastboot: core/libsparse/sparse.cpp:131: int write_all_blocks(struct sparse_file *, struct output_file *): Assertion `pad >= 0' failed.
when i try to flash the regular .zip from the oneplus page i get an error: This package is for: bacon,A0001 This Device is .
I tried to flash via adb sideload and pushed the file via adb push on the phone, but same error.
any suggestions how to save my good old ONE to give it a second live in the hands of my son?
Click to expand...
Click to collapse
I had the same problem when I tried flashing TWRP K1. Regular TWRP flashed fine.
Oh, if you're using Linux then make sure your udev rules are set up properly. On Arch I needed to install an extra package otherwise adb/fastboot was a bit janky