I can't get the silly thing to go into recovery mode. It says "recovery key detected" "booting recovery kernel image" and won't do anything else.
It used to be rooted and had a custom rom. Then I accidentally upgraded to a 1.2 rom - I forgot I had downgraded to 1.1. SO the darned thing was sorta bricked. I finally managed, through following several different sets of instructions, to get it back to stock. The tablet now works but I want to go back to a custom rom.
I've tried NVflash - my pc doesn't see the tablet. (it does see it when it's booted normally, just not in recovery mode).
I've tried loading CWM recovery via the SD card and it doesn't work.
I've read several instructions, including the G-tab for dummies but still can't get it to go to recovery. Suggestions on what to do next would be greatly appreciated.
Lanna
lmanalo said:
I can't get the silly thing to go into recovery mode. It says "recovery key detected" "booting recovery kernel image" and won't do anything else.
Click to expand...
Click to collapse
Those messages tell me that you have a 1.2 bootloader now, but, your recovery is still 1.1-based. So now, you'll have to load a version of CWM with a 1.2-based kernel: one of CWM-3.0.2.8rev5, CWM-4.0.1.5 (1.2 bl version), or CWM-5.5.0.4Beta15.
And, you'll have to load recovery using nvflash, like this:
1. Put the gTab into APX mode (for nvflash) by first powering it off, then powering it on by pressing both the Power button and the Vol [-] key. The splash screen with the 3 birds should appear, and then the screen should go blank.
2. Run this command to determine the partition no. of the recovery (SOS) partition--usually, it is 9: Open a CMD.exe window, then change into the directory containing both the nvflash.exe and the bootloader.bin files. Then run:
Code:
C:\SOME\PATH> [B].\nvflash --bl bootloader.bin --getpartitiontable p.txt[/B]
3. Now look through the p.txt file for a partition named SOS. Assuming, now, that the partition no. is 9, load the new recovery image using nvflash:
Code:
C:\SOME\PATH> [B].\nvflash -r --download 9 [I]C:\SOME\PATH\recovery.img[/I][/B]
You can get the recovery.img file either from any of the various CWM zip files on the board, or, use one of the image files themselves. Make sure the image is for the 1.2 version of the bootloader, though.
4. After the command completes, power off the gTab, and try to boot into recovery mode as usual.
Thank you so much for your help!!
I followed your instructions and I'm still getting to the same point with the same messages. I verified that I am using an img file for 1.2 bootloader. Actually, I've tried 2 different ones.
I looked at the p.txt and there is a SOS partition and I checked the .cfg file and it lists SOS as 9. I even tried editing the cfg file and changing the name of the file called out in img9 to recovery.img (the CWM recovery image) and ran the complete NVFlash update. It rebooted into normal tablet mode just fine. I shut down and tried booting into recovery and it still doesn't get past those messages.
Is it possible that the partition is corrupt? If so, how do I go about restoring it or creating a new one? I've seen instructions for using CWM recovery but I can't get to it. Can bit be done with NVflash or another utility?
thanks again,
Lanna
lmanalo said:
I even tried editing the cfg file and changing the name of the file called out in img9 to recovery.img (the CWM recovery image) and ran the complete NVFlash update.
Click to expand...
Click to collapse
I would avoid a complete nvflash if at all possible. Otherwise, you risk turning a simple problem--like this one seems to be--into a major headache. The commands I gave are safe because they only read stuff and operate on single partitions--so they won't make your problem worse.
It rebooted into normal tablet mode just fine. I shut down and tried booting into recovery and it still doesn't get past those messages.
Click to expand...
Click to collapse
1. Which nvflash package did you use?
2. Which version of recovery did you load with the ``--download'' command I gave before?
3. Can you post the p.txt file?
4. Also post the *.img that this command produces somewhere so I can take a look at them:
Code:
C:\SOME\PATH> [B].\nvflash --bl bootloader.bin --read 4 ebt.img --read 9 rec.img --read 10 lnx.img[/B]
Is it possible that the partition is corrupt? If so, how do I go about restoring it or creating a new one? I've seen instructions for using CWM recovery but I can't get to it. Can bit be done with NVflash or another utility?
Click to expand...
Click to collapse
Since you're now on the stock ROM you can load recovery only using nvflash--see last post for the command to be used. On rooted custom ROMs you could have used other commands to reload a recovery image.
5. In the stock ROM what TapUI version is displayed in Settings?
1. Which nvflash package did you use?
nvflash 1.2
2. Which version of recovery did you load with the ``--download'' command I gave before?
cwmod v_08
3. Can you post the p.txt file?
4. Also post the *.img that this command produces somewhere so I can take a look at them:
Ive posted them on dropbox but I don't have enough posts on the forum to be able to include the links. Suggestions?
5. In the stock ROM what TapUI version is displayed in Settings?[/QUOTE]
1.2 - 4349
Thanks again,
Lanna
lmanalo said:
1. Which nvflash package did you use?
nvflash 1.2
2. Which version of recovery did you load with the ``--download'' command I gave before?
cwmod v_08
Click to expand...
Click to collapse
No need to post your files. It's as I suspected: your bootloader is 1.2, but, you're trying to run a CWM with a 1.1 kernel on it (cwmod v_08).
See post #2 above and get the correct 1.2 versions mentioned there.
IT WORKED!!!
Now, what ROM do you suggest for 1.2?
Thanks so much.
Lanna
lmanalo said:
Now, what ROM do you suggest for 1.2?
Click to expand...
Click to collapse
That's up to you really. There are a range of 1.2-based ROMs from Froyo (Android 2.2) all the way up to ICS (Android 4.0.4) to choose from. Read the recommendations other people have made on the board when similar questions have been asked.
Hello rajeevvp,
I tried using NVFLASH to unbrick my device, but I get an error message, "USB Device not found".
I updated the APX driver. I can hear a system beep when I plug in my device and then go into APX mode. I tried download.bat and also the nvflash string. Still says no USB found.
Where did I go wrong?
Thanks for any help with this. I have been pretty lucky up to the point of bricking my device.
Thanks Steve.
Please use the Q&A Forum for questions &
Read the Forum Rules Ref Posting
Thanks ✟
Moving to Q&A
same problem.
rajeevvp said:
Those messages tell me that you have a 1.2 bootloader now, but, your recovery is still 1.1-based. So now, you'll have to load a version of CWM with a 1.2-based kernel: one of CWM-3.0.2.8rev5, CWM-4.0.1.5 (1.2 bl version), or CWM-5.5.0.4Beta15.
And, you'll have to load recovery using nvflash, like this:
1. Put the gTab into APX mode (for nvflash) by first powering it off, then powering it on by pressing both the Power button and the Vol [-] key. The splash screen with the 3 birds should appear, and then the screen should go blank.
2. Run this command to determine the partition no. of the recovery (SOS) partition--usually, it is 9: Open a CMD.exe window, then change into the directory containing both the nvflash.exe and the bootloader.bin files. Then run:
Code:
C:\SOME\PATH> [B].\nvflash --bl bootloader.bin --getpartitiontable p.txt[/B]
3. Now look through the p.txt file for a partition named SOS. Assuming, now, that the partition no. is 9, load the new recovery image using nvflash:
Code:
C:\SOME\PATH> [B].\nvflash -r --download 9 [I]C:\SOME\PATH\recovery.img[/I][/B]
You can get the recovery.img file either from any of the various CWM zip files on the board, or, use one of the image files themselves. Make sure the image is for the 1.2 version of the bootloader, though.
4. After the command completes, power off the gTab, and try to boot into recovery mode as usual.
Click to expand...
Click to collapse
I have the same problem. I can boot into my custom ROM without a problem (running Smooth_Bean), however, when i try to boot into recovery mode (pressing power and vol+) my gTablet gets stuck on the "recovery key detected" "rebooting recovery kernel image" messages. I tried getting the table and got the p.txt file but its corrupted or something, I tried opening the file with different programs and different code languages but I could not for the life of me figure out which partition is the SOS located in. Thanks in advance!
rvmedina20 said:
I have the same problem. I can boot into my custom ROM without a problem (running Smooth_Bean), however, when i try to boot into recovery mode (pressing power and vol+) my gTablet gets stuck on the "recovery key detected" "rebooting recovery kernel image" messages.
Click to expand...
Click to collapse
If you can boot into a rooted ROM, then you can use the flash_image program to write to a new recovery:
1. Copy the file containing the recovery image (some filename.img) to the SD card.
2. Open a Terminal Emulator window and type these commands (only the stuff in bold):
Code:
$ [B]su[/B]
# [B]/system/bin/flash_image recovery [I]/SOME/PATH/filename[/I].img[/B]
I tried getting the table and got the p.txt file but its corrupted or something, I tried opening the file with different programs and different code languages but I could not for the life of me figure out which partition is the SOS located in.
Click to expand...
Click to collapse
The file is OK--it's just in binary format. The nvflash program you used has created a binary NAND partition table layout file instead of the usual plain text one. The SOS partition is still #9 as per that file.
Try a different nvflash program the next time.
Related
Recovery
You should have fastboot installed properly on your system to be able to flash it.
Heres a quick guide for Mac (which is really similar to Linux, search for XP guides which are available all over)
FASTBOOT
Download Fastboot from http://developer.htc.com/adp.html
Unzip and move to whatever folder you want.
I put it in /Users/MyName/Android
OPTIONAL Rename from "fastboot-mac" to "fastboot" (makes following guides made for xp and linux easier)
Now you have to append it to your .bash_profile
Easy Way
Follow instructions on http://donovan.covblogs.com/archives/027838.html to edit the bash_profile visually with textwrangler.
Your .bash_profile should look like this:
Code:
export PATH=$PATH:/Users/MyName/Android
export PATH=$PATH:/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/bin:/usr/X11/bin
remember to edit the path to wherever you put your fastboot file (some people like to put it in the tools folder in the android sdk so adb is added to the .bash_profile as well)
or
Terminal Way
Code:
export PATH="$Path:/Users/MyName/Android"
Hit enter
Now refresh your .bash_profile
Code:
~/.bash_profile
To see if you've done it right
Code:
fastboot --help
or
Code:
fastboot --h
If the help text shows in terminal in another directory other than where fastboot is then you've got it right
Code:
$fastboot --help
usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall flash boot + recovery + system
flash <partition> [ <filename> ] write a file to a flash partition
erase <partition> erase a flash partition
getvar <variable> display a bootloader variable
boot <kernel> [ <ramdisk> ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> ] create bootimage and flash it
devices list all connected devices
reboot reboot device normally
reboot-bootloader reboot device into bootloader
options:
-w erase userdata and cache
-s <serial number> specify device serial number
-p <product> specify product name
-c <cmdline> override kernel commandline
-i <vendor id> specify a custom USB vendor id
To use the fastboot command your device has to be in fastboot mode
Enter FASTBOOT_MODE
Hold power button with device off and when the Home/Menu/Back buttons light up, release power button then press and hold the camera button
Dell logo will appear shortly followed by a white screen.
Tap fastboot in the top right
Thank you mzsigler from modaco for pointing out this simple step i missed.
finally:
FLASH RECOVERY IMAGE
Download the attached file and unzip it.
Make sure terminal is in the directory where the recovery-US6601.img is.
Use
Code:
pwd
to see which directory ur in
Code:
$ fastboot -i 0x413c flash recovery recovery-US6601.img
sending 'recovery' (3280 KB)... OKAY
writing 'recovery'... OKAY
$
Now reboot your device and hold both volume keys to get into recovery mode.
To the 6 people who downloaded it first, i might of uploaded the wrong one because i forgot that before i did nandroid backup i had flashed a different recovery to get clockword mod to work. This should be the right one now which was pulled using adb shell before clockworkmod.
Dell Streak stock US 1.6 Build 6601
There are several ways to restore/flash this i'll mention 2 Fastboot and nandroid
Fastboot
Code:
fastboot -i 0x413c flash boot boot.img
fastboot -i 0x413c flash system system.img
fastboot -i 0x413c flash cache cache.img
fastboot -i 0x413c flash userdata data.img
fastboot -i 0x413c flash recovery recovery.img
Technically you don't need to worry about flashing cache.img and data.img but i performed this backup after a factory reset so your not taking any of my personal info/data
fasboot didn't work for me for so i restored with nandroid
Nandroid
+Create a folder named "Clockworkmod" on your storage card
+In that folder create a folder named "backup"
+Create a folder in "backup" named whatever you want and place boot.img, system.img, cache.img, data.img, recovery.img and nandroid.md5 in that folder.
+Flash Clockworkmod Recovery
2.5.0.1 didnt work on mine but 1.8.1.7 did :/
+Enter clockworkmod recovery
-Power on device while holding both volume keys, then select "2. Software upgrade via Update.pkd on SD Card"
Now you should be in ClockworkMod Recovery
-Scroll down to nandroid using the volume keys and press the camera button to select it
-Select Restore and choose your folder (the one you placed in the backup folder)
Now although this flashes 1.6 build 6601 it doesn't return the baseband to *****31
this is what mine now reads
Basband version
GAUSB1A110421-US
Kernel version
2.6.29-perf
OEM version
GAUSB1a111231
Build number
6601
Click to expand...
Click to collapse
Also be warned that after i returned to 1.6 i got the crazy home/menu/back lights as seen in this video I'm guessing it has something to do with the 21 baseband and 31 oem version
I think this is worthy of a sticky great work my friend keep it up
thanks for the files. wonder how to restore the 6601 baseband.
johnnobts said:
thanks for the files. wonder how to restore the 6601 baseband.
Click to expand...
Click to collapse
Yep, trying to figure that out now.. well back it up first from a device that hasn't been messed with.
I have followed both sets of instructions (fastboot and nandroid) and I keep getting stuck at the Dell logo. During nandroid restore it gives me the error "Cannot format DATADATA" then stops. Any ideas?
when i flashed the recovery my screen got stuck at a black screen after the reboot
Worked great for me. Back to the out of the box experience.
do you have flashing lights though? or did your baseband not change? Also, maybe after returning to 6601, you can apply the 31 build? Or you already tried that, didn't you, fone? No change to baseband?
http://forum.xda-developers.com/sho...date.dell.com/LatestBuild/LatestBuild_31.html
uberamd said:
I have followed both sets of instructions (fastboot and nandroid) and I keep getting stuck at the Dell logo. During nandroid restore it gives me the error "Cannot format DATADATA" then stops. Any ideas?
Click to expand...
Click to collapse
Are the other items flashing?
lbj23numb1 said:
when i flashed the recovery my screen got stuck at a black screen after the reboot
Click to expand...
Click to collapse
which method did you use to flash and can you still access the recovery but holding down both volume buttons after you power your device on?
Bohemian said:
Worked great for me. Back to the out of the box experience.
Click to expand...
Click to collapse
Does your baseband end in 21-US or 31-US and are your capacitive button lights going crazy or normal?
johnnobts said:
do you have flashing lights though? or did your baseband not change? Also, maybe after returning to 6601, you can apply the 31 build? Or you already tried that, didn't you, fone? No change to baseband?
http://forum.xda-developers.com/sho...date.dell.com/LatestBuild/LatestBuild_31.html
Click to expand...
Click to collapse
My baseband is still at 21-US although OEM version is at 31. I have a suspicion that fastboot isn't properly writing the recovery.img for me..
I tried to use that latest update and half way through i got an error "FOTA model name mismatch"
I'm currently trying to figure a way to pull the baseband so we can do a true full restore. (now i'm worried if i can get 2.2 when its released since my device is at 21-US)
Bohemian said:
Worked great for me. Back to the out of the box experience.
Click to expand...
Click to collapse
Same here. Finally no O2 logo...
johnnobts said:
do you have flashing lights though? or did your baseband not change? Also, maybe after returning to 6601, you can apply the 31 build? Or you already tried that, didn't you, fone? No change to baseband?
http://forum.xda-developers.com/sho...date.dell.com/LatestBuild/LatestBuild_31.html
Click to expand...
Click to collapse
I had flashing lights. Flashing r2-4399-streak-superboot fixed the problem.
I am still at my original baseband. 21-EU
Stock 31 update is 4917. Why would you want to downgrade from 6601?
because we are in the US and are a little concerned we may not be able to apply the 2.2 upgrade with a modified baseband. fone, i don't think the baseband change will make a difference. i am concerned about the flashing lights as of right now.
fone_fanatic said:
Are the other items flashing?
which method did you use to flash and can you still access the recovery but holding down both volume buttons after you power your device on?
Does your baseband end in 21-US or 31-US and are your capacitive button lights going crazy or normal?
My baseband is still at 21-US although OEM version is at 31. I have a suspicion that fastboot isn't properly writing the recovery.img for me..
I tried to use that latest update and half way through i got an error "FOTA model name mismatch"
I'm currently trying to figure a way to pull the baseband so we can do a true full restore. (now i'm worried if i can get 2.2 when its released since my device is at 21-US)
Click to expand...
Click to collapse
I can still get to the recovery using the buttons but when I select the second option that's when I get stuck at a black screen. I flashed the recovery through fastboot
No change in numbers and now no flashing lights. Still can not get to recovery, clockworkmod just reboots and button mode goes to standard recover and selectin option 2 goes black screen.
Model; Dell Streak
Firmware; 1.6
Baseband; GAUSB1A111231-US
Kernel; 2.6.29-perf
OEM; GAUSB1A111231
Build; 6601
I haven't been able to find any information about backing up baseband in order to do a restore.
get stuck on dell logo boot
I have followed both sets of instructions (fastboot and nandroid) and I keep getting stuck at the Dell logo. During nandroid restore it gives me the error "Cannot format DATADATA" then stops. Please help
Hi fone-fanatic
Could you explain how backing up the recovery.img to be able to flash it ?
Thanks
gomesj said:
I have followed both sets of instructions (fastboot and nandroid) and I keep getting stuck at the Dell logo. During nandroid restore it gives me the error "Cannot format DATADATA" then stops. Please help
Click to expand...
Click to collapse
I am having the exact same issue. Any advice?
I initially flashed this via fastboot and was stuck at the dell logo. i then flashed to the 02 1.6 rom and re flashed the att rom via clockwork mod nandroid. i am up and running but the lights flash like crazy and everything has "an unexpected error" and closes. cant open contacts, set up gmail, open "phone" so i cant get to the dialer. am i the only one getting all the force closes?
I would reflash mate
How can I fix this
here's your fix
Mrdroid921 said:
How can I fix this
Click to expand...
Click to collapse
Same thing happened to me. Fear not - you CAN fix this! Here's what you do:
1) Download clockwork mod recovery (cwmod_internal.zip) from the sticky thread in the Dev forum (http://forum.xda-developers.com/showthread.php?t=865245). Unzip it, and get the file called recovery.img and put it in the directory you ran nvflash from before.
2) Now go to your nvflash directory. Find the gtablet.cfg file. Edit it - under partition 9 where it says filename, change that to say recovery.img.
Now re-run nvflash - your G Tablet will get flashed with Clockwork Mod now instead of stock recovery. Once it's finished, reboot, and hold down the Vol + key while booting. You should get into Clockwork Mod Recovery now.
From here, I recommend repartitioning (use 2048 and 0 as the two options). Now try booting normally and everything should work fine.
I found that answer here: http://forum.xda-developers.com/archive/index.php/t-932157.html And it does work - perfectly.
By the way - when editing the gtablet.cfg file, be sure the finished edited product is still named exactly the same way. (Sometimes when using the standard text editor the editor will rename the file into a txt file.)
If you can't figure out the procedure above, give me your email privately and I'll send you a modified version of nvflash - all you'll have to do is run the program.
I'm trying this now - I'm stuck in the Tap n Tap logo loop.
VTDivot said:
I'm trying this now - I'm stuck in the Tap n Tap logo loop.
Click to expand...
Click to collapse
Go to my page and look at "You bricked your gtab and now you are freaking out. "
http://viewsonic-gtablet-for-dummies.webs.com/starthere.htm
The point is to wipe data before or after you nvflash. Data from your previous rom is interrupting the normal boot process of your current rom.
Just follow my procedure.
Added by edit.
If you already have CWM working, simply boot into CWM and wipe data. Then reboot system. If that doesn't work, wipe data and then nvflash. This will work for sure.
Jackpot - although I didn't DL clockwork mod, I just ran this in apx mode:
For Windows users: nvflash.exe --bl bootloader.bin --download 9 clockworkmod.img
I then repartitioned and it worked
BTW - I wasn't even close to freaking out ;-)
I love the title of that thread LOL
Ok well i pretty much have this fix set up and ready to go..but.
I am getting this error message.
1) Error: Winzip only supports IMG files that are in the ISO format. When i try to extract the recovery.img file.
Thinking that i didnt need to extract the file....i did the drop in and rename thing and i got the following error message during the NVflash. "file recovery.img not found" (or something like that. Obviously i just need some one to tell me how to extract the recovery.img in winxp (or what program to dl to do it).
I am 99% sure this will fix my current screwup partition/bootloop after an nvflash issue.
Thanks in advance (and please answer so i dont have to clutter up the page by starting a new thread asking for help).
Allen
Ok update. My screwup was that i had actually renamed the file "recover.img" and it should have just been "recovery". No extraction was necessary just my stupidity.
In the directions above it seems to indicate you rename the file as "recovery.img" but you dont. You leave the FILE AS "recovery" but and just type in "recovery.img" as the file name in step 9.
This work, and the flash completed. Then on reboot it started bootlooping again (as expected) but FINALLY..i was able to cwm and change the partitions to 2048 and 0.Whelp..now i am off to figure out what the deal is with the two different bootloaders and pick a honecomb ROM to install (went from TNT lite to vegan tab to vegan/gingerbread edition.
Any suggestions as to which honeycomb rom is the best?
Hello There Everyone, I hope someone knowledgeable from XDA would help me out a little, I have been having trouble with my prime since I tried to install a new Rom into it, to cut thing short, I am now only able to get into Fastboot on my Prime, I tried flashing TWRP or CWM but they dont show up and only shows the two icons, the fastboot and wipe data. This is really frustrating, I tried to use NVFlash but not sure how do I extract the blob files from the AndroidRoot folder in the internal sd, I have been trying for hours but none of the method works, I really need some guidance on how do I actually restore stock Roms and get it running again! I really hope anyone would help me here..Please! Thank you in Advance!
five_secondskin said:
Hello There Everyone, I hope someone knowledgeable from XDA would help me out a little, I have been having trouble with my prime since I tried to install a new Rom into it, to cut thing short, I am now only able to get into Fastboot on my Prime, I tried flashing TWRP or CWM but they dont show up and only shows the two icons, the fastboot and wipe data. This is really frustrating, I tried to use NVFlash but not sure how do I extract the blob files from the AndroidRoot folder in the internal sd, I have been trying for hours but none of the method works, I really need some guidance on how do I actually restore stock Roms and get it running again! I really hope anyone would help me here..Please! Thank you in Advance!
Click to expand...
Click to collapse
if you are able to get into fastboot mode then it should be easy to get things fixed.
-you are unlocked correct?
-download the twrp.blob appropriate for you bootloader
- fastboot (-i 0x0b05) flash boot twrp.blob
- hold power and volume down,
-press volume up,
-use adb to push a rom to your prime
-factory reset then flash the rom
marko! said:
if you are able to get into fastboot mode then it should be easy to get things fixed.
-you are unlocked correct?
-download the twrp.blob appropriate for you bootloader
- fastboot (-i 0x0b05) flash boot twrp.blob
- hold power and volume down,
-press volume up,
-use adb to push a rom to your prime
-factory reset then flash the rom
Click to expand...
Click to collapse
If he could manage to get twrp on there he wouldn't need to adb push a rom because he would be able to load a rom from an external sd instead which would be easier and faster.
five_secondskin, if you cannot get twrp to work and you did the nvflash process and have the backup files on the internal sd from when you did it then send me a pm and I will give you my google talk name and I will talk you thru it mate.
If you nvflashed and have your files backed up, and can get into APX mode this is how you solve it :
Do you have it NVFlashed with the blobs backed up? If so here's your solution :
1. Download a ROM from the Asus site and extract the blob using BlobTools (blobunpack)
2. Enter APX mode [Power + Vol-Up]
3. Run wheelie to start nvFlash mode [This is the blob.bin specific to your device generated while enabling nvFlash]
Code:
wheelie --blob blob.bin
4. Flash the bootloader
Code:
nvflash -r --download 4 blob.EBT
5. Flash the recovery image
Code:
nvflash -r --download 5 blob.SOS
6. Flash the kernel image
Code:
nvflash -r --download 6 blob.LNX
5. Flash the system image
Code:
nvflash -r --download 10 blob.APP
6. Reboot [This should reboot your device, else long-press the power button to reboot]
Code:
nvflash -r --go
Hey everyone,
This is my first time posting to the forums. I have been trying to get everything done without having to ask questions since there are so many all over the place and I can see how it can get tiring trying to help everyone when their may be an answer out there already if you look. However, I have ran into an issue that I can't seem to find much information on. I have the HTC Rezound that is S-On (apparently you need a Linux machine to get S-Off which I don't have. Using Windows 7.) and have been using fastboot to get things done. I have unlocked the bootloader and have installed the 'Amon Ra' recovery and setup Superuser and SU. As far as I know, I have to use ROM's that are S-On friendly (right?) and I chose to try out 'EclipticRez' and later 'Talon'.
As I tried to flash the ROM's through fastboot it fails with the following errors every time and I cannot continue:
archive does not contain android-info.txt
archive does not contain android-product.txt
From what I found is that it may be a bad download of the ROM. Maybe.... But it happened consecutively with two different ROM downloads.
I also read that maybe the recovery wasn't setup, which as far as I know it is. Should I use a different recovery? Everyone usually references to using CWM, which I wouldn't mind using but I couldn't figure out how to get SU access.
Can I just create the files myself? They are only txt files after all.
If anyone can help me with this I will be so grateful! I'm pretty new to this and it has definitely been a fun learning experience for me
Much thanks in advance!
Strikerz87 said:
Hey everyone,
This is my first time posting to the forums. I have been trying to get everything done without having to ask questions since there are so many all over the place and I can see how it can get tiring trying to help everyone when their may be an answer out there already if you look. However, I have ran into an issue that I can't seem to find much information on. I have the HTC Rezound that is S-On (apparently you need a Linux machine to get S-Off which I don't have. Using Windows 7.) and have been using fastboot to get things done. I have unlocked the bootloader and have installed the 'Amon Ra' recovery and setup Superuser and SU. As far as I know, I have to use ROM's that are S-On friendly (right?) and I chose to try out 'EclipticRez' and later 'Talon'.
As I tried to flash the ROM's through fastboot it fails with the following errors every time and I cannot continue:
archive does not contain android-info.txt
archive does not contain android-product.txt
From what I found is that it may be a bad download of the ROM. Maybe.... But it happened consecutively with two different ROM downloads.
I also read that maybe the recovery wasn't setup, which as far as I know it is. Should I use a different recovery? Everyone usually references to using CWM, which I wouldn't mind using but I couldn't figure out how to get SU access.
Can I just create the files myself? They are only txt files after all.
If anyone can help me with this I will be so grateful! I'm pretty new to this and it has definitely been a fun learning experience for me
Much thanks in advance!
Click to expand...
Click to collapse
1) Switch to TWRP or CWM for your recovery.
2) You install the rom zip via recovery.
3) You then need to fastboot flash the kernel from the rom zip you downloaded. You don't install the whole rom via fastboot.
To borrow from the CM11 thread.
- Place the boot.img into the platform-tools folder of the Android SDK's install directory.
- Boot to the bootloader.
- Ensure your device is connected to your computer and that your device is now in fastboot mode. This is a white screen and it says fastboot on it.
- Open a Terminal (OSX or Linux) or CMD window (Windows) and cd to the platform-tools directory of the Android SDK's install directory.
- Issue this command to flash the boot.img we placed in the platform-tools folder earlier:
Code:
fastboot flash boot boot.img
- Watch the output of the terminal, it should say something like "sent successfully".
- Finally send this command:
Code:
fastboot reboot
Since you're s-on, you'll need to do this whenever you install a new rom. Using these steps, you can install any rom you want.
Strikerz87 said:
Hey everyone,
This is my first time posting to the forums. I have been trying to get everything done without having to ask questions since there are so many all over the place and I can see how it can get tiring trying to help everyone when their may be an answer out there already if you look. However, I have ran into an issue that I can't seem to find much information on. I have the HTC Rezound that is S-On (apparently you need a Linux machine to get S-Off which I don't have. Using Windows 7.) and have been using fastboot to get things done. I have unlocked the bootloader and have installed the 'Amon Ra' recovery and setup Superuser and SU. As far as I know, I have to use ROM's that are S-On friendly (right?) and I chose to try out 'EclipticRez' and later 'Talon'.
As I tried to flash the ROM's through fastboot it fails with the following errors every time and I cannot continue:
archive does not contain android-info.txt
archive does not contain android-product.txt
From what I found is that it may be a bad download of the ROM. Maybe.... But it happened consecutively with two different ROM downloads.
I also read that maybe the recovery wasn't setup, which as far as I know it is. Should I use a different recovery? Everyone usually references to using CWM, which I wouldn't mind using but I couldn't figure out how to get SU access.
Can I just create the files myself? They are only txt files after all.
If anyone can help me with this I will be so grateful! I'm pretty new to this and it has definitely been a fun learning experience for me
Much thanks in advance!
Click to expand...
Click to collapse
also to note....you dont have to install linux to get s-off....if you follow my guide you can do it straight from a live disk rather than installing it....so it wont erase or mess up your windows partition at all
Solved!
Thank you, Mjones, I finally got it! I knew it was much easier than I was making it out to be. I was missing the kernel! Yeah, a crucial part in the process, I know
I first ran CWM and flashed the ROM over and ran the .zip through recovery (which I couldn't understand at first as I could never find it in the directory) but the installer would only go 50% and would fail... makes sense why now lol
I later flashed TWRP and backed up again after recovering from the fail. I flashed over the kernel and voila! So simple... Had to slap myself.
Thanks again! Case solved.
REV3NT3CH, that is sweet!! I have been hoping there is a way to gain s-off with Windows. I have 7 at work and 8.1 (which I can't get anything to work on) at home. I actually have to focus on work today haha so I'll look into the method and try it out tomorrow if I can. Thanks for all of the help.
mjones73 said:
1) Switch to TWRP or CWM for your recovery.
2) You install the rom zip via recovery.
3) You then need to fastboot flash the kernel from the rom zip you downloaded. You don't install the whole rom via fastboot.
To borrow from the CM11 thread.
- Place the boot.img into the platform-tools folder of the Android SDK's install directory.
- Boot to the bootloader.
- Ensure your device is connected to your computer and that your device is now in fastboot mode. This is a white screen and it says fastboot on it.
- Open a Terminal (OSX or Linux) or CMD window (Windows) and cd to the platform-tools directory of the Android SDK's install directory.
- Issue this command to flash the boot.img we placed in the platform-tools folder earlier:
Code:
fastboot flash boot boot.img
- Watch the output of the terminal, it should say something like "sent successfully".
- Finally send this command:
Code:
fastboot reboot
Since you're s-on, you'll need to do this whenever you install a new rom. Using these steps, you can install any rom you want.
Click to expand...
Click to collapse
Thank You So much, Mine case also Resolved. I was too frustated sice last 3 days cause my phone was in dead mode. At the end, fastboot flash boot boot.img Worked. ThankYOu
mjones73 said:
1) Switch to TWRP or CWM for your recovery.
2) You install the rom zip via recovery.
3) You then need to fastboot flash the kernel from the rom zip you downloaded. You don't install the whole rom via fastboot.
To borrow from the CM11 thread.
- Place the boot.img into the platform-tools folder of the Android SDK's install directory.
- Boot to the bootloader.
- Ensure your device is connected to your computer and that your device is now in fastboot mode. This is a white screen and it says fastboot on it.
- Open a Terminal (OSX or Linux) or CMD window (Windows) and cd to the platform-tools directory of the Android SDK's install directory.
- Issue this command to flash the boot.img we placed in the platform-tools folder earlier:
Code:
fastboot flash boot boot.img
- Watch the output of the terminal, it should say something like "sent successfully".
- Finally send this command:
Code:
fastboot reboot
Since you're s-on, you'll need to do this whenever you install a new rom. Using these steps, you can install any rom you want.
Click to expand...
Click to collapse
I need to be able to do it via fastboot, as my Motorola Electrify M is stuck in a bootloop and there's no way I could find to boot into recovery. I'm using ./fastboot update name_of_update.zip and it is an official OTA .zip but I still get this error. Any suggestions?
ecols33 said:
I need to be able to do it via fastboot, as my Motorola Electrify M is stuck in a bootloop and there's no way I could find to boot into recovery. I'm using ./fastboot update name_of_update.zip and it is an official OTA .zip but I still get this error. Any suggestions?
Click to expand...
Click to collapse
Sorry, don't know anything about that phone.
ecols33 said:
I need to be able to do it via fastboot, as my Motorola Electrify M is stuck in a bootloop and there's no way I could find to boot into recovery. I'm using ./fastboot update name_of_update.zip and it is an official OTA .zip but I still get this error. Any suggestions?
Click to expand...
Click to collapse
Did you try this first? (Right from Moto's site)
Perform a factory reset using external keys
1. Power off the phone, press and hold volume down button, press power button
2. Screen will come up with "Fastboot", press Vol down key to cycle through choices until you get "Android Recovery", then press Vol up key
3. Wait for the "triangle ! / Android" screen then go on to step 4
4. Press both Vol up and Vol down key simultaneously. A menu will come up
5. Tap on Vol down key until "wipe data/factory reset" is highlighted, and tap Power key. Another Confirmation screen will come. Tap on Vol down key until coming to Yes and tap Power key
6. After userdata is cleared, the "reboot system now" option will be highlighted by Default. Tap Power key
7. Phone will reboot to initial setup screen.
PLEASE HELP! I have a Huawei P8 and I tried to update to android 6.0 (GRA-L09xxxxxxxxxxxB317 or something) Went to install it and now im stuck in bootloop (a very annoying one, I can rarely get into eRecovery and eRecovery is not able to fix my problem: "Getting package info failed") so I went into fastboot&rescue mode and I did the flash thing via my PC (that Fastboot flash boot boot.img etc.) but I get this error saying: "FAILED (remote: Command not allowed)" for any image im trying to flash. My fastboot/bootloader or whatever it's called is locked my android is unrooted and stock android. I don't know how to unlock it I can't find anything anywhere.. HELP ME
not working
hariom.gupta11 said:
Thank You So much, Mine case also Resolved. I was too frustated sice last 3 days cause my phone was in dead mode. At the end, fastboot flash boot boot.img Worked. ThankYOu
Click to expand...
Click to collapse
not working on my 4c. write successful but when reboot is completed it goes to previous state.
"the user data partition can no longer be used"
zb602kl_x00tdb
L0RDZ3RO said:
PLEASE HELP! I have a Huawei P8 and I tried to update to android 6.0 (GRA-L09xxxxxxxxxxxB317 or something) Went to install it and now im stuck in bootloop (a very annoying one, I can rarely get into eRecovery and eRecovery is not able to fix my problem: "Getting package info failed") so I went into fastboot&rescue mode and I did the flash thing via my PC (that Fastboot flash boot boot.img etc.) but I get this error saying: "FAILED (remote: Command not allowed)" for any image im trying to flash. My fastboot/bootloader or whatever it's called is locked my android is unrooted and stock android. I don't know how to unlock it I can't find anything anywhere.. HELP ME
Click to expand...
Click to collapse
I have same problem on asus zenfone max pro m1 I bought it online said used and now working
can't boot into recovery.
can't boot into system.
Only EDL Mode and Fastboot Mode, but fastboot is Locked whic I cant unlock because I cannot boot into system to toggle USB Debugging and allow OEM unlocking
Qualcomm is harder to flash than MTK that can use SP FlashTool.
on this I use QFIL but keeps "sahara error". I tried searching and try moving firmware file to bin but no Luck. I'm currently trying different version of QFIL Tool.
If it FAILS my only HOPE is to use MUT-QCfire which will Require a "SmartCardReader" Which is a bit pricey and I don't even know if it will work on my device.
I am trying to repair Galaxy Tab 10.1 3G which don't want to start.
It always start to screen where you can select between recovery and download but nothing happens if I try to select.
If I keep power button long enough pressed, it starts again. (can't poweroff)
I can start in APX mode and read & write memory with nvflash.
I did full wipe with nvflash --create but after that only APX mode was available and screen was black.
nvflash --rawdevicewrite for partitions 2, 3 and 4 returned it back to previous state.
I have also tried to write recovery (cwm and original) with nvflash but no luck.
Any ideas what I can try? Or is it now bricked?
I want to understand how boot process works.
So, I flashed something "wrong" to partition 4 (bootloader):
nvflash --bl bootloader.bin --download 4 boot.img
After this reboot => screen is always blank and only APX mode is available. So: at least it is reading bootloader.
Flashing correct bootloader (backup):
nvflash --bl bootloader.bin --download 4 part-4.img
But But what it should do next, after bootloader? Run kernel from partition 9 or recovery-kernel from partition 8?
If I select download mode, is it still using bootloader or should it run something from recovery partition? Or other partition?
Doh, maybe this tab have faulty hardware but how to detect this??
narska said:
I want to understand how boot process works.
So, I flashed something "wrong" to partition 4 (bootloader):
nvflash --bl bootloader.bin --download 4 boot.img
After this reboot => screen is always blank and only APX mode is available. So: at least it is reading bootloader.
Flashing correct bootloader (backup):
nvflash --bl bootloader.bin --download 4 part-4.img
But But what it should do next, after bootloader? Run kernel from partition 9 or recovery-kernel from partition 8?
If I select download mode, is it still using bootloader or should it run something from recovery partition? Or other partition?
Doh, maybe this tab have faulty hardware but how to detect this??
Click to expand...
Click to collapse
Maybe putting "download-mode-stuff" on any but the bootloader-partition, and putting correct bootloader-stuff in it's partition might help you to get into download-mode. Anyway,... I'm not sure, if your NAND-partition-table is still correct. Try to get into download-mode first and once that's done, try flashing it back to stock with a full image.
I don't think it is fully "hard-bricked" (would APX work then?) but it is also not a "soft-brick".
The NAND, or part of it's content doesn't seem to be as it should and you mentioned working with the stuff on, or even with the partitions.
TnA.Plastic said:
Maybe putting "download-mode-stuff" on any but the bootloader-partition, and putting correct bootloader-stuff in it's partition might help you to get into download-mode. Anyway,... I'm not sure, if your NAND-partition-table is still correct. Try to get into download-mode first and once that's done, try flashing it back to stock with a full image.
I don't think it is fully "hard-bricked" (would APX work then?) but it is also not a "soft-brick".
The NAND, or part of it's content doesn't seem to be as it should and you mentioned working with the stuff on, or even with the partitions.
Click to expand...
Click to collapse
I have spent several days trying to put this in download mode.
Problem is, I have no idea where is "download-mode-stuff", is it inside of recovery partiton?
And I don't know how to setup bootloader so it will start this downloader.
Should I download bootloader source code (u-boot?) and compile it with custom settings?
Is there source & settings available for P7500 original (or custom) bootloader?
Fixed!
It was hardware issue: cleaned system board and now it works just fine!
There was some kind of liquid. soda? juice?