Related
hey guys i'm having some trouble. i just got the nexus (it's my first smartphone, ever) and i've tried to hit the ground running. here's what i've done to the phone so far.
i got all the drivers running on my win7 machine and also installed the android SDK folder onto C: as was described in this thread: http://forum.xda-developers.com/showthread.php?t=878786
i then unlocked the bootloader using the above guide as well. when I power on the phone using UP+POWER it says UNLOCKED.
I then proceeded to follow this guide: http://forum.xda-developers.com/showthread.php?t=875875
i used ADB to flash the clockwork crespo recovery. i then used fastboot to install Superuser.
at that point i had an unlocked bootloader, clockword recovery image and superuser permissions.
i then saw that the 2.3.1 update had been released. i wanted to learn how to tackle that so i started reading up. i noticed that people were using ROM Manager and Titanium. I got titanium and installed the BusyBox addon and it allowed me to do a full Batch Backup of all my programs, etc. i've got the 50MB or so backup folder on my PC now.
anyway, i then messed with Rom Manager. I installed the 3.0.0.0 ClockworkMod Recovery and everything went smoothly. now this is where my troubles begin.
when i go to Download ROM all i get is a Free Stuff area.
when i go to Check for ROM Updates it tells me my device isnt set up for OTA updates.
those are just minor issues.
this is the big and scary issue i have:
when i click on reboot to recovery, it takes me to the same screen that i go to when i power on with VOLUME UP+POWER. it doesnt take me to the recovery screen that i see in various youtube videos. instead, i'm at the main screen where it says UNLOCKED and i have 4 choices (reboot bootloader, recovery, reboot, power off). and on the very top in RED letters it says fastboot - no boot or img file. <-- this is the part that makes me nervous. If i manually power down the phone and boot to fastboot and click recovery, it just goes back to this same screen and says fastboot - no boot or img file. when i first rooted the phone, clicking recovery actually took me to a different screen where i was able to load up superuser.zip and install it.
did i accidetnally delete something that i wasnt supposed to? did installing ROM manager mess something up? i typically dont do anything until i confirm that i am supposed to. i think the problem is that i dont yet know how one thing i do on the phone affects another. i'm guessing when i used rom manager to update the CWmod it changed some folders/files? i dunno!
otherwise, the phone works fine and there are no glitches or hiccups or crashes. So if someone can please take a moment to just explain to me what i did wrong or what i failed to do i'd really, really appreciate it.
you don't have a recovery partition. Either flash one over manually using fastboot, or boot up and try to use ROM Manager to flash CWR.
when you say flash one over using fastboot, do you mean put my phone using VOLUME UP + POWER, connect usb cable, then use command line to do this:
fastboot flash recovery recovery-clockwork-crespo.img
?
kramer987 said:
when you say flash one over using fastboot, do you mean put my phone using VOLUME UP + POWER, connect usb cable, then use command line to do this:
fastboot flash recovery recovery-clockwork-crespo.img
?
Click to expand...
Click to collapse
yes, just follow the examples in http://forum.xda-developers.com/showthread.php?t=875875
kramer987 said:
when you say flash one over using fastboot, do you mean put my phone using VOLUME UP + POWER, connect usb cable, then use command line to do this:
fastboot flash recovery recovery-clockwork-crespo.img
?
Click to expand...
Click to collapse
Yes, 'cept it will be "fastboot flash recoveryrecovery-clockwork-3.0.0.0-crespo.img" without the quotes now.
But does it say that you're missing a boot.img or recovery.img?
Also, the "not set up for OTA" thing isn't for official OTAs. Some developers have made their custom ROMs capable of being updated that way.
unremarked said:
Yes, 'cept it will be "fastboot flash recoveryrecovery-clockwork-3.0.0.0-crespo.img" without the quotes now.
But does it say that you're missing a boot.img or recovery.img?
Also, the "not set up for OTA" thing isn't for official OTAs. Some developers have made their custom ROMs capable of being updated that way.
Click to expand...
Click to collapse
thank you luxferro and unremarked. i did it and it works perfectly. i am now able to access clockworkmod recovery 3.0.0.0. next step is backup my existing ROM and also to figure out how to put the OTA 2.3.1 on and restore all my data
oh and unremarked: it basically said no boot or img file and thats it after i would click on recovery or reboot to recovery trhough rom manager. it was just in red at the top. but now it takes me to the ClockworkMod Recovery
Hi
I've searched for a solution but didn't find one for my problem so...
I was trying to flash an updated kernel through Kernel Manager application and then it said it cannot complete task and asked me to reboot system.
I then entered into the recovery and flashed the kernel manually.
When rebooted system I got the message "FASTBOOT MODE - NO BOOT OR RECOVERY IMG" in red at the top of the bootloader.
So naturally I thought maybe it lost the recovery so I went and flashed CWM recovery 3.0.2.5 (had 3.0.2.4 when all this happened) through fastboot and that went OK.
I then entered the recovery to make sure the recovery flashing went OK and pressed Restart system now.
But then it started the bootloader and the same message appeared "FASTBOOT MODE - NO BOOT OR RECOVERY IMG" in red at the top of the bootloader.
I repeated that process few times and same thing.
The strange thing is when I select "REBOOT BOOTLOADER" and it boots into bootloader I see "FASTBOOT MODE" in red at the top. But when I try to reboot the phose I see the message to the top again.
How can I get out of this?
Hi guys,
I've got the same problem, although I don't know if it IS a problem.
I'm running v7.0.0-NS and I'm going to upgrade to v7.0.3 ... just searching for instructions!!!
~AndrewGoldy
since I am able to enter the recovery Im trying to restore an earlier backup. Not sure it this will do anything since my problem is in the bootloader area.
If this makes my phone to start up normally then I really dont understand this.
*** I think that I've just fixed it ***
I opened up "Rom Manager v4.2.0.2", and then selected the option to "Flash ClockworkMod Recovery"
Once it had downloaded "ClockworkMod Recovery v3.0.2.4", I selected the option to "Reboot into Recovery".
That worked.
It now says "Fastboot Mode" when I boot into the Bootloader.
Success!!!! (I think)
Well it just finished restoring the backup.
It seems it solved the problem on mine to since it passed the bootloader and the boot animation is on.
I really cant understand this.
I've done the same but the Recovery Stil nor Bootloader works. However it does say Fast boot mode now instead of no boot or recovery img. But still can't flash or back up a rom!
Correction i got it work after flashing to oldest recovery that was an option
I fixed this problem (Nexus S) by reverting to an older (3.0.2.4) CMRecovery, just go down to the last option "All ClockworkMod Recoveries" and Flash an older version (mine was not working with 5.0.2.0).
Hi! Anyoane can help me ?
I disconnected by accidently the USB cable while the phone was at the ClockWorkMod Recovery v5.0.2.0/-mounts and storage/-mount USB storage, and after that ( adb , fastboot and usb died).
I installed Stock OTA 2.3.6 I9023 for my Nexus S I9023. During the day phone closed and no longer wanted to open (even replace the battery). After more hours the phone is open , adb and usb works not for a long time after several attempts ( during this time I managed it to root and install CWM 5.0.2.0 back)
I flashed ICS Kwiboo v3 . After reboot the phone began to froze , and shortaly closed.
Because the phone will no longer open I tried in CWM all ( wipe data:fact, wipe cache, wipe dalvik, format/all ) .
Now if reboot system on CWM I have Fastboot Mode - No Boot or Recovery IMG
but if I reboot bootloader or power off when is opened is just Fastboot Mode .
Adb , fastboot and mount USB still no work. ( I have SDK 14 on windows7 installed, all the driver for Nexus S was updated).
Because the PC not recognized my phon I can't install another ROM or CWM.
( When USB cable connecting on the phone it's charge the battery only!).
Thanks for your advice!
No recovery img & fastboot devices -> nothing
Hi all,
When I try to access the recovery mode on my NS, I have the same "no boot or recovery img". I change my CWM version from last to 3.0.2.4 and another version too. Still, I can't access the recovery mode.
I installed the SDK to restore a stock recovery image I found, hoping to use fastboot (from the sdk + a standalone version I found before). But it won't recognize my phone (fastboot devices -> nothing). I installed the PdaNet for the Android 1.0 driver, and the Android 4.0 driver from the SDK. Still nothing, although "adb devices" apparently sees my phone.
I've spent my whole night on this. Without recovery I can't backup, and I can't switch rom (heard of this ICS rolling-out ? I'd like to have some flavour of it), I can't wipe or whatever.
Please can someone point me to a solution for fastboot to see the phone, or even better, to reinstall a recovery tool ?
Thanks a huge lot
S
saychand said:
Hi all,
When I try to access the recovery mode on my NS, I have the same "no boot or recovery img". I change my CWM version from last to 3.0.2.4 and another version too. Still, I can't access the recovery mode.
I installed the SDK to restore a stock recovery image I found, hoping to use fastboot (from the sdk + a standalone version I found before). But it won't recognize my phone (fastboot devices -> nothing). I installed the PdaNet for the Android 1.0 driver, and the Android 4.0 driver from the SDK. Still nothing, although "adb devices" apparently sees my phone.
I've spent my whole night on this. Without recovery I can't backup, and I can't switch rom (heard of this ICS rolling-out ? I'd like to have some flavour of it), I can't wipe or whatever.
Please can someone point me to a solution for fastboot to see the phone, or even better, to reinstall a recovery tool ?
Thanks a huge lot
S
Click to expand...
Click to collapse
I can help you but....
1. In bootloader mod ADB working ? (if not try back off battery for 10 min or more) and try again..
2. Your device is rooted ?
I was going to suggest trying to reflash the latest recovery again in CWM, but I think you guys said that hasn't worked.
Every now and then when I flash a new ROM this happens to me. I usually just flash an older version, then reflash the newest version and the Recovery works just fine.
Maybe try using a different recovery program?
it does work, many have done it already, see all the duplicated topics
Sent from my SGH-T989 using xda premium
Thank you guys for your replys.
surdu_petru said:
I can help you but....
1. In bootloader mod ADB working ? (if not try back off battery for 10 min or more) and try again..
2. Your device is rooted ?
Click to expand...
Click to collapse
1. I removed the battery for 10mn. When I come back to the bootloader "ADB devices" doesn't return a device, so it doesn't see my phone. But when switched on, it can see it.
2. Yes, it is. There is the SuperUser app, and when apps ask for root, I can allow or deny. And the lock state is 'unlocked'
akabadnews said:
I was going to suggest trying to reflash the latest recovery again in CWM, but I think you guys said that hasn't worked.
Every now and then when I flash a new ROM this happens to me. I usually just flash an older version, then reflash the newest version and the Recovery works just fine.
Maybe try using a different recovery program?
Click to expand...
Click to collapse
I tried the latest, the oldest, the versions inbetween... nothing. I have the latest version of CWM and I reflashed the last Recovery from the app.
I can't flash another ROM, because I need recovery mode for that ; and my problem is that I can't access recovery indeed... :/ I feel like I need A to do B, and B to do A.
"No boot or recovery img": doesn't it mean that I should put some file somewhere ? I hope it would be that simple.
Do you have other ideas ?
---------- Post added at 01:33 PM ---------- Previous post was at 01:24 PM ----------
AllGamer said:
it does work, many have done it already, see all the duplicated topics
Sent from my SGH-T989 using xda premium
Click to expand...
Click to collapse
I've tried several time, flashing different versions of CWM recovery. I've returned to bootloader -> recovery dozens of time and I still have the "no boot no recovery img". I'll try again.
All the threads which speak about it and mention to flash another rom -> yeah thanks, but I can't access recovery
Threads mentioning fastboot -> I tried with different drivers (including 1.0 and 4.0), but fastboot won't see/talk to my device
Do you see something else that I didn't try ?
---------- Post added at 02:16 PM ---------- Previous post was at 01:33 PM ----------
I also tried this which seems to be a good step
http://forum.xda-developers.com/showthread.php?t=1356319
Basically it says
adb shell
SU
flash_image recovery /sdcard/filename.img
But like the guy in thread, I have memory errors "mtd: read error at 0x00000000 (out of memory)" then write errors, then "failed with error: -1" and "error writing recovery"
It's ok now.
In case other it can help other people:
I tried again the PDAnet installation to get the android 1.0 drivers. (actually there is a binary called "install legacy usb drivers" which apparently worked well.)
Fastboot would detect my phone in bootloader mode.
So I could "fastboot flash recovery xxx.img" I first failed with a stock recovery, but for which I didn't know the exact reference and origins (I was stuck with the exclamation point in white triangle). As I couldn't find another stock recovery for Nexus S, I downloaded the CWM recovery from the website (not from the app), last version (5.0.2.0) and flashed it with fastboot.
It seems to work properly now, so i'm doing a rom backup, just in case for later, and I'll flash stock ICS
FYI: rom manager only caused me issues ; I don't know why Cyanogen uses it. Just use the recovery directly from recovery... Even CWM. just not Rom Manager.
Cheers and thanks to those who tried to help.
++
saychand said:
It's ok now.
In case other it can help other people:
I tried again the PDAnet installation to get the android 1.0 drivers. (actually there is a binary called "install legacy usb drivers" which apparently worked well.)
Fastboot would detect my phone in bootloader mode.
So I could "fastboot flash recovery xxx.img" I first failed with a stock recovery, but for which I didn't know the exact reference and origins (I was stuck with the exclamation point in white triangle). As I couldn't find another stock recovery for Nexus S, I downloaded the CWM recovery from the website (not from the app), last version (5.0.2.0) and flashed it with fastboot.
It seems to work properly now, so i'm doing a rom backup, just in case for later, and I'll flash stock ICS
FYI: rom manager only caused me issues ; I don't know why Cyanogen uses it. Just use the recovery directly from recovery... Even CWM. just not Rom Manager.
Cheers and thanks to those who tried to help.
++
Click to expand...
Click to collapse
THANKS! This helped A TON!
I did the PDA installation again, and for some reason this seemed to fix my inability to access recovery.
Agreed on Rom manager, I updated CWM through rom manager and I believe that's what buggered up my recovery, as I have never had trouble accessing it before I did that.
But again, a big THANKS for that suggestion!
Hi,
I unlocked my bootloader today and I just flashed the latest CWM Recovery via Fastboot.
However, when I try to enter Android Recovery I get the Android with the white triangle and exclamation point.
I saw a similar thread but did not see a resolution. Do I need to flash the Gingerbread boot.img via Fastboot?
Also, I read you have to delete a file somewhere or else the default recovery restores itself every reboot? I did not delete any such file, and when I unlocked my bootloader, it obviously wiped my data.
Any ideas how I can get into recovery and flash me a dang ROM?
Atrix_E said:
Hi,
I unlocked my bootloader today and I just flashed the latest CWM Recovery via Fastboot.
However, when I try to enter Android Recovery I get the Android with the white triangle and exclamation point.
I saw a similar thread but did not see a resolution. Do I need to flash the Gingerbread boot.img via Fastboot?
Also, I read you have to delete a file somewhere or else the default recovery restores itself every reboot? I did not delete any such file, and when I unlocked my bootloader, it obviously wiped my data.
Any ideas how I can get into recovery and flash me a dang ROM?
Click to expand...
Click to collapse
What command did you enter in Fastboot?
IUH1991 said:
What command did you enter in Fastboot?
Click to expand...
Click to collapse
I followed these steps:
Flashing CWM Recovery via Fastboot -
1.Download the latest CWM recovery from Downloads section (recovery-clockwork-5.0.2.0-olympus.img)
2.Power off phone
3.Put phone into fastboot (Power + Vol Down Button)
4.Press Volume Up button to select Fastboot
5.Connect phone via USB cable
6.Open Command Prompt from your fastboot directory
7.Type fastboot flash recovery recovery-clockwork-5.0.2.0-olympus.img
8.Type "fastboot reboot"
9.Your phone will reboot normally
Also, how screwed would I be if I don't backup my PDS? http://forum.xda-developers.com/showthread.php?t=1138220
I got it. Loving CM7
Could you share how did you make it work?
Thanks
iceinspire said:
Could you share how did you make it work?
Thanks
Click to expand...
Click to collapse
install recovery.sh is the file to delete i beleve its in /system/ect after useing like rommanager to install recovery i used romracers and flashed in recovery mode
i like that on better do a youtube search there are alot of good vids on how to do it
the ones i used were from thesmokingandroid
just type that into youtube search and he has a 3 part series on cwm and installing rom
Sent from my MB860 using xda premium
I deleted that file and its is still not work
iceinspire said:
I deleted that file and its is still not work
Click to expand...
Click to collapse
did you power off the phone
then
hold down power and volume down
when u see fastboot appear use vol
down to scroll to android recovery then
push power button to select it
NOTE; U need to be rooted and have your bootloader unlocked FIRST
Yes I am a noob, but a noob in need of help.
I recently decided to root my Acer Iconia a500 16gb WIFI version, running on stock ICS. I realised i had to unlock my bootloader to install CWM etc. So I followed a tutorial, and used blackthund3rs A500 APX Flash Utility v0.4. I used the flash package "Skrilax_CZ's bootloader V8".
So I thought all was going well, however when rebooting it, it just sits on "Skrilax_CZ's bootloader V8: Booting primary kernel image". I'm assuming its bricked, as it doesn't go beyond this point. I can get a few other options by doing the "PWR+VOL" combination and it opens boot-menu mode with the options:
-Reboot
-Fastboot Mode
-Boot Primary Kernel Image
-Boot Secondary Kernel Image
-Boot Recovery
-Set Boot secondary Kernel Image
-Set debug mode off/on
-Wipe Cache
The only option that does the slytest thing is putting it in fastboot mode. When putting it in this mode, it registers in "A500MANAGER" (when connected to my pc via USB) as the device being in fastboot mode. But I dont know what to do from there.
I've looked at multiple threads and cant find anything to fix this problem.
Please Help! Thanks!
boxyJ said:
Yes I am a noob, but a noob in need of help.
I recently decided to root my Acer Iconia a500 16gb WIFI version, running on stock ICS. I realised i had to unlock my bootloader to install CWM etc. So I followed a tutorial, and used blackthund3rs A500 APX Flash Utility v0.4. I used the flash package "Skrilax_CZ's bootloader V8".
So I thought all was going well, however when rebooting it, it just sits on "Skrilax_CZ's bootloader V8: Booting primary kernel image". I'm assuming its bricked, as it doesn't go beyond this point. I can get a few other options by doing the "PWR+VOL" combination and it opens boot-menu mode with the options:
-Reboot
-Fastboot Mode
-Boot Primary Kernel Image
-Boot Secondary Kernel Image
-Boot Recovery
-Set Boot secondary Kernel Image
-Set debug mode off/on
-Wipe Cache
The only option that does the slytest thing is putting it in fastboot mode. When putting it in this mode, it registers in "A500MANAGER" (when connected to my pc via USB) as the device being in fastboot mode. But I dont know what to do from there.
I've looked at multiple threads and cant find anything to fix this problem.
Please Help! Thanks!
Click to expand...
Click to collapse
Sounds like the A500 manager didn't do something right. Happens sometimes.
Here is what I would do. I assume you don't have the Android SDK installed. No need to, as some of the bootloader/CWM packages have the necessary files needed.
1. Boot to the bootloader, select the option "Fastboot Mode"
2. Make sure you have downloaded to PC a CWM package for ICS/JB. Usually the manual packages have the necessary files, such as the CWM image, fastboot.exe, adb, and some dll files. Unzip them to your PC. (Also helps to download a custom ICS or CM10 rom to your sd card first)
3. Open a command window in the same folder you have the files.
4. type "fastboot flash recovery xxxxxxxx.img" (xxxxxxxx is name of cwm recovery img file, do not put the " in) then hit enter.
5. After completion, immediately boot tablet into recovery. I believe holding Vol- and PWR does this. Or, Vol+ and PWR boots to the bootloader menu. Either way.
In recovery, do your wipes and or formats as per ROM installation instructions.
Install ROM
Enjoy. If you have problems locating one of those packages, give a shout back.
MD
Thanks for the fast reply,
I am a noob, so could you perhaps link me a CWM package for ics to download?
Thanks
boxyJ said:
Thanks for the fast reply,
I am a noob, so could you perhaps link me a CWM package for ics to download?
Thanks
Click to expand...
Click to collapse
No problem. I'll post a link in awhile.
MD
Files
Ok, so here are your files.
Unzip the contents of the zip file to a folder on your PC
Boot your tab to the bootloader menu, select Fastboot.
Connect tab to PC, then wait 30 seconds or so (windows has to recognize it)
Then, go to that folder. Hold "Shift" + "Right Mouse Click".
Select "Open Command Window"
Type in the following;
fastboot flash recovery recovery_thor17_403.img
and hit enter. Should transfer good.
When finished, boot tablet to recovery like I mentioned earlier. DO NOT boot to the system. Or you'll be doing this all over again.
Install ICS or CM10 rom following the instructions on the ROM post. I suggest starting out with Civato's ICS Flex****** rom first, or one of the stock rooted ones.
Should be good...... I hope.
MD
Thanks again.
I did the fastboot recovery thing. But when I go to reboot, I have to turn it on and select "Boot Recovery", when I do its stuck on the screen "Skrilax_CZ's bootloader v8: Booting recovery kernel image"
Is this whats supposed to happen or am I supposed to see a different screen?
boxyJ said:
Thanks again.
I did the fastboot recovery thing. But when I go to reboot, I have to turn it on and select "Boot Recovery", when I do its stuck on the screen "Skrilax_CZ's bootloader v8: Booting recovery kernel image"
Is this whats supposed to happen or am I supposed to see a different screen?
Click to expand...
Click to collapse
Shut down the tab. Reboot holding V- and PWR release when you see the text. Should reboot to recovery.
If not, your partitions are probably hosed.
Then it's Timmy Deans Rollback tool time. Will have to turn you over to dibs_nz for that one.
MD
Moscow Desire said:
Shut down the tab. Reboot holding V- and PWR release when you see the text. Should reboot to recovery.
Click to expand...
Click to collapse
That brings me to the screen "Skrilax_Cz's bootloader V8: Booting recovery kernel image." But it doesn't go any further?
Well crap.
Sounds like some partitions are messed.
Try this NVFlash package;
http://d-h.st/32X
It's a version 3 bootloader using NVFlash. Might work.
Put your tab in APX mode (I believe you press and hold the pinhole reset, then PWR. After 3 seconds, release PWR, 2 seconds later release pinhole. Might have to reverse it, don't remember)
Plug tab in. PC should recognize.
Unzip to a folder, open a command window, and run the batch file (type it into the command window, xxxxxxxx.bat then hit enter)
If there's an error, it should show in the command window.
Here is a link to Timmy Deans roll back package;
http://d-h.st/0x7
The issue here, is you need a UID number, which I HOPE you wrote down when you did the V8 bootloader!
MD
Well I cant manually put it into APX mode, tried a few times. Also there is no bat file in that download... as for Timmy Deans roll back package, is it a simple method taht should work? At this point I just want to get my tab working again . And yes I do have my UID number.
Ok,ok.
So this morning I tried to fix it again. And I think i managed to put it in APX mode. Also, I started up APX flash tool and all, did that. Suddenly a cmd window opened and started doing stuff. And now the tablet says in the top right corner "Acer Iconia APX mode", and a yellow glowing 'acer' title in the middle (which is different from what I've been seeing). Another cmd window opened by itself saying "Nvflash started [resume mode]. Where do i go from here??
Thanks!
So I think I've gotten a better understanding of how this all works today. I've tried multiple ways of flashing recovery imgs ect, flashing the bootloader and all that stuff. And all the times I've done this, it always stops at "Nvflash started [resume mode]" and doesn't go any further.
So I'm not really sure what else there is to do.
Please, I need guidance. (below is my last attempt, and what It said in the cmd window).
Flashing bootloader: bootloader_v8.bin ...
Nvflash started
[resume mode]
Formatting partition 4 please wait.. Command Execution failed cmd 13, error 0x12
0002
FAILED!
command failure: format partition failed (bad command)
bootloader status: unknown operation (code: 1) message: flags: 0
Nvflash started
[resume mode]
Please let us know if/how you fixed this problem! Some of us are in the same boat.
timmytutone said:
Please let us know if/how you fixed this problem! Some of us are in the same boat.
Click to expand...
Click to collapse
U guys need to run the babsector.rar file to reset yr tabs partitions and you must have yr cpuid/sbk.
The file and instructions to use it are in post 2 of the root guide in my sig.
If u get any errors you must post the output. You may have a faulty memory chip. If that's the case, a new motherboard is the only fix.
dibb
Sent from my GT-I9300 using Tapatalk 4
EDIT: Link to post2 (babsector.rar file)
http://forum.xda-developers.com/showthread.php?p=35500589
dibb_nz said:
U guys need to run the babsector.rar file to reset yr tabs partitions and you must have yr cpuid/sbk.
The file and instructions to use it are in post 2 of the root guide in my sig.
If u get any errors you must post the output. You may have a faulty memory chip. If that's the case, a new motherboard is the only fix.
dibb
Sent from my GT-I9300 using Tapatalk 4
EDIT: Link to post2 (babsector.rar file)
http://forum.xda-developers.com/showthread.php?p=35500589
Click to expand...
Click to collapse
Thank you so much for the reply. I gave up this afternoon and just flashed the ota 4.0.3 version from Acer and it seems to be running really good. The only reason I was looking to flash something new is because the update from honeycomb to ics didn't take very well and I've always been dealing with problems from it. If the flashed version is still running well I might not try a different Rom again. I'll be putting your tip in my notes in case I do. Thanks again.
dibb_nz said:
U guys need to run the babsector.rar file to reset yr tabs partitions and you must have yr cpuid/sbk.
The file and instructions to use it are in post 2 of the root guide in my sig.
If u get any errors you must post the output. You may have a faulty memory chip. If that's the case, a new motherboard is the only fix.
dibb
Sent from my GT-I9300 using Tapatalk 4
EDIT: Link to post2 (babsector.rar file)
http://forum.xda-developers.com/showthread.php?p=35500589
Click to expand...
Click to collapse
So I rooted and then flashed a Custom Recovery Image. Then I followed the instructions under the babsector portion of your post. I got to this part: Go back into apx mode and run 501 B.bat, Reboot into recovery and do the wipes, Reboot!!!
I wasn't sure what "do the wipes" referred to so I did ALL the wipes. Cache/Dalvik/Battery/ and Data(?) When I rebooted it went back to the green screen and says in yellow: "Invalid primary (LNX) image." and has the same menu as when I rebooted after 501 A.bat
Now what?
EDIT:
So I was sitting there with the green screen/yellow error and decided to boot into recovery again. I then reflashed my custom rom, and did a normal reboot. Everything is working now! My FIRST custom rom after owning android devices since the ancient Motorola i1 way back in the day. I'd still like to know if what I did was right or what happened, so I can detail it in my instructions for my next custom rom project.
timmytutone said:
So I rooted and then flashed a Custom Recovery Image. Then I followed the instructions under the babsector portion of your post. I got to this part: Go back into apx mode and run 501 B.bat, Reboot into recovery and do the wipes, Reboot!!!
I wasn't sure what "do the wipes" referred to so I did ALL the wipes. Cache/Dalvik/Battery/ and Data(?) When I rebooted it went back to the green screen and says in yellow: "Invalid primary (LNX) image." and has the same menu as when I rebooted after 501 A.bat
Now what?
EDIT:
So I was sitting there with the green screen/yellow error and decided to boot into recovery again. I then reflashed my custom rom, and did a normal reboot. Everything is working now! My FIRST custom rom after owning android devices since the ancient Motorola i1 way back in the day. I'd still like to know if what I did was right or what happened, so I can detail it in my instructions for my next custom rom project.
Click to expand...
Click to collapse
Dude I know it's been 4 years since you wrote that but I just wanted to say you really saved my life, THANK YOU!!!
About 2 months ago I tried to unlock my tablet's bootloader but I gave up after reading different articles and obviously ended up with a really bad headache. Last night I realized Android 3 is really old and I almost can't install anything on it. So basically I gave it another shot and been reading and downloading different files for almost 3 hours. Today I managed to unlock bootloader and use your short instruction (more likely a walk-thru that how you fixed your problem) and it worked!!! I owe you man... I owe you
I even took it to so many different mobile centers about 3 weeks ago but they said its files are not anywhere/we can't do it/it's too risky/it's not possible deal with it
Happy to help!
Ok, I seem to be making things worse and worse, so I've come here to beg for help.
TLDR:
my acer iconia a500 was running skrilax_CZ's bootloader V8, I screwed it up (I think) by trying to install ClockworkRecovery.
I was still able to boot into Tegraowners_JB-MR1_ROM_v11t4
I messed a BUNCH more stuff up. a bunch!
Now, I can still see the internal and external SD but when i try to use blackthund3r's tools to root/recovery/custom-mod
it gets stuck when trying to enter APX mode. "No APX devices detected"
I do have the CPUID and the SBK
Longer explanation and details:
I installed Acer's USB drivers: USB_Acer_1.06.1500_A30H_A
I rooted the device using: ICS_rooting_A10x_A5xx --> runit-win.bat
I used blackthund3r's tools: A500APXFlash.exe and A500Manager.exe
I installed a custom bootloader rom: V8-Thor_1.7.3_recovery.a500apx
I installed Tegraowners_JB-MR1_ROM_v11t4 and gapps-jb-20130301-a500-v2
I was happy as a clam for 2 days playing with my fancy tablet.
I installed Superuser App
I made a nandroid backup at least once from the v8 bootloader.
I made a batch Titanium backup
I then tried installing clockwork recovery mod, and I think that's when i screwed myself.
Suddenly the power on + down_volume switch just led to a screen that said "Skrillax_CZ's bootloader V8"
"Booting recovery kernel image" and then it would hang there forever.
I could still boot into Tegraowners_JB-MR1_ROM_v11t4 so I tried to run a restore from Titanium Backup,
it froze halfway through with the message "superuser access denied"
I rebooted, and suddenly most of the widgets/apps are gone, and the back/home/and application navigation
button that are usually on the bottom left corner are also gone!
then I did a bunch of crazy/desperate stuff with blackthund3r's tools, (something involving trebuchet?)
and I finally blacked out amidst tears and despair around 5 am this morning.
so
now, when I use A500APXFlash.exe and A500Manager.exe it tries to put the tablet into APX mode, and the
tablet goes to a blackscreen, with a white LED on the power button, but I get the error "No APX devices detected"
I also tried inserting a paper clip then turning the power on, same result.
I do have the CPUID and the SBK
Please help if you can, and please dumb down your explanations if possible, this is my first tablet and
i'm totally new to android, etc.
Thanks for your time
-Joel
couple more details, it boots to the point where you swipe to unlock it, but when i do, i get a popup that says Trebuchet has stopped,
and when i click ok, it just comes back infinitum
oh, and when i use A500 Manager.exe it says that it's connected and usb debugging is ON, but I have no way of getting into the settings
to confirm that?
I don't want to come across as lazy, I literally have 8 tabs open from xda-developers and 3 from tegraowners. I also just tried afterotav_109 but that didn't do anything.
I found
the following files in
Computer\Acer Iconia Tab A500\Internal Storage\0\.AcerRecoveryInstaller
(see attached picture)
I'm guessing I can't rename recovery.old to recovery, or something easy like that?
small update, installed android SDK and adb shell
when I launch adb shell I can see the various directories on the tablet internal and external SD. I'm in the process of scouring the forums for info about how to use the adb tool to fix my problem, am I even on the right track?
thanks for any feedback y'all can provide
-Joel
j8ner said:
Ok, I seem to be making things worse and worse, so I've come here to beg for help.
Click to expand...
Click to collapse
I'm going to reply to each part of your post, just in case someone else is having the same probs...
Longer explanation and details:
I installed Acer's USB drivers: USB_Acer_1.06.1500_A30H_A
I rooted the device using: ICS_rooting_A10x_A5xx --> runit-win.bat
I used blackthund3r's tools: A500APXFlash.exe and A500Manager.exe
I installed a custom bootloader rom: V8-Thor_1.7.3_recovery.a500apx
I installed Tegraowners_JB-MR1_ROM_v11t4 and gapps-jb-20130301-a500-v2
Click to expand...
Click to collapse
TBH installing T/O's rom you should really be asking on their forum - their roms are a little different to the ones on xda - like, you don't need the v8 unlocked bootloader you can run it on HC or ICS Bootloaders.
android adb/usb drivers?? you dont mention them are they on your PC?
I then tried installing clockwork recovery mod
Click to expand...
Click to collapse
Didnt you already have cwm 1.7.3?
How did you try to install it? and yeh this is probably where you went wrong.
You must install custom recoverys using either fastboot or an appropriate flashable zip
Suddenly the power on + down_volume switch just led to a screen that said "Skrillax_CZ's bootloader V8"
"Booting recovery kernel image" and then it would hang there forever.
Click to expand...
Click to collapse
For future reference what you should have done here is run the 1.7.3.apx with apxflash tool.
I could still boot into Tegraowners_JB-MR1_ROM_v11t4 so I tried to run a restore from Titanium Backup,
it froze halfway through with the message "superuser access denied"
I rebooted, and suddenly most of the widgets/apps are gone, and the back/home/and application navigation
button that are usually on the bottom left corner are also gone!
then I did a bunch of crazy/desperate stuff with blackthund3r's tools, (something involving trebuchet?)
and I finally blacked out amidst tears and despair around 5 am this morning.
Click to expand...
Click to collapse
Yes it gets like that sometimes dont panic its fixable!
so
now, when I use A500APXFlash.exe and A500Manager.exe it tries to put the tablet into APX mode, and the
tablet goes to a blackscreen, with a white LED on the power button, but I get the error "No APX devices detected"
I also tried inserting a paper clip then turning the power on, same result.
I do have the CPUID and the SBK
Click to expand...
Click to collapse
If thats the error it means the drivers are screwed up. Completely uninstall the acer drivers, reboot and reinstall. But w8 theres more....
Make sure you got the adb/fastboot drivers here
Please help if you can, and please dumb down your explanations if possible, this is my first tablet and
i'm totally new to android, etc.
Thanks for your time
-Joel
couple more details, it boots to the point where you swipe to unlock it, but when i do, i get a popup that says Trebuchet has stopped,
and when i click ok, it just comes back infinitum
oh, and when i use A500 Manager.exe it says that it's connected and usb debugging is ON, but I have no way of getting into the settings
to confirm that?
I don't want to come across as lazy, I literally have 8 tabs open from xda-developers and 3 from tegraowners. I also just tried afterotav_109 but that didn't do anything.
I found the following files in Computer\Acer Iconia Tab A500\Internal Storage\0\.AcerRecoveryInstaller
(see attached picture)
Click to expand...
Click to collapse
Acer recovery installer? OK so I assume you used that to try and flash a recovery? This app works best on HC Bootloader - the only way to use it with ICS is IF you already have the v8.
Also, you must make sure you run the correct recovery for whatever version of ROM you are wanting to flash. So check the OP of your chosen rom for which recovery you need. Most of the ics/jb custom roms here on xda work with cwm 1.7.3, TWRP or public recovery. BUT these wont work on HC
I'm guessing I can't rename recovery.old to recovery, or something easy like that?
Click to expand...
Click to collapse
You can use an appropriate recovery.img and flash via fastboot
-------------------------------------------------------------------------------------------
OK so lhow do we get you fixed???
You need to do a complete FORMAT (factory data reset) of your system to get it back to a state where you can use the tools.
Install the adb drivers first!
Lets see if fastboot mode is available.
As long as you see skrilax_cz v8 bootloader on your screen connect yr micro usb cable - power down and boot up holding VOLUME UP button...you should see the fastboot menu now follow the instructions here on using the fastboot commands to WIPE userdata and cache
THEN if you have the correct recovery.img you can flash this too (see that post) if not run the apxflash tool again using cwm 1,7,3.apx file.
Now, once you have run it BOOT DIRECTLY to recovery and flash your rom. (Doesnt matter which one as long as its ICS or JB...)
This is important...if you try and boot yr tabs OS, you'll get either booting primary kernel error or be stuck on the acer logo -
IF fastboot is not available then run the apxflash tool to install recovery instead then using that same post it shows you how to do a full format wipe, with cwm.
I hope this isnt too over the top for you...I've tried to explain things so you can understand a bit better - but I may have to 'dumb' things down a bit more, let me know
good luck with it
dibb
thank you so much for replying, i'll get right on this
Dibb thank you very much, as soon as I get back I'm going to go through your directions step by step.
I really appreciate your help, and I'll post an update later tonight.
in fastboot, please advise
dibb_nz said:
Acer recovery installer? OK so I assume you used that to try and flash a recovery? This app works best on HC Bootloader - the only way to use it with ICS is IF you already have the v8.
Also, you must make sure you run the correct recovery for whatever version of ROM you are wanting to flash. So check the OP of your chosen rom for which recovery you need. Most of the ics/jb custom roms here on xda work with cwm 1.7.3, TWRP or public recovery. BUT these wont work on HC
You can use an appropriate recovery.img and flash via fastboot
-------------------------------------------------------------------------------------------
OK so lhow do we get you fixed???
You need to do a complete FORMAT (factory data reset) of your system to get it back to a state where you can use the tools.
Install the adb drivers first!
Lets see if fastboot mode is available.
As long as you see skrilax_cz v8 bootloader on your screen connect yr micro usb cable - power down and boot up holding VOLUME UP button...you should see the fastboot menu now follow the instructions here on using the fastboot commands to WIPE userdata and cache
THEN if you have the correct recovery.img you can flash this too (see that post) if not run the apxflash tool again using cwm 1,7,3.apx file.
Now, once you have run it BOOT DIRECTLY to recovery and flash your rom. (Doesnt matter which one as long as its ICS or JB...)
This is important...if you try and boot yr tabs OS, you'll get either booting primary kernel error or be stuck on the acer logo -
IF fastboot is not available then run the apxflash tool to install recovery instead then using that same post it shows you how to do a full format wipe, with cwm.
I hope this isnt too over the top for you...I've tried to explain things so you can understand a bit better - but I may have to 'dumb' things down a bit more, let me know
good luck with it
dibb
Click to expand...
Click to collapse
DIBB IS TEH AWSEOMEMEMEST!!!!!!!
fastoot mode worked!
one thing that threw me off is that I had to figure out that I needed to type
Code:
fastboot.exe flash [B]recovery[/B] recovery_thor17_403.img
the guide here
doesn't specify which partition to use so I got an error message until I guesstimated I wanted the boot partition.
Anyway, once you fixed my bootloader, I restored the full system from a backup I had made on the first of the month.
thank you thank you for your awesome help!
now I can break it again and again!
made a minor edit, changed boot --> recovery in the "code" section above
j8ner said:
DIBB IS TEH AWSEOMEMEMEST!!!!!!!
fastoot mode worked!
one thing that threw me off is that I had to figure out that I needed to type
Code:
fastboot.exe flash [B]recovery[/B] recovery_thor17_403.img
the guide here
doesn't specify which partition to use so I got an error message until I guesstimated I wanted the boot partition.
Anyway, once you fixed my bootloader, I restored the full system from a backup I had made on the first of the month.
thank you thank you for your awesome help!
now I can break it again and again!
made a minor edit, changed boot --> recovery in the "code" section above
Click to expand...
Click to collapse
Glad u got it
Not sure why you had to use fastboot.exe as the command tho? but as long as it worked and you're up and running, that's the main thing!
happy flashing
dibb
Edit: have edited guide to show recovery partition - thank for picking that up
Sent from my GT-I9300 using Tapatalk 4 Beta