Related
After successfully flashing ClockWork RecoveryMod, I placed SU on the root of my SNS, powered it off, went into fastboot, but when I went into Recovery, it just went to Stock Recovery, the Exclamation Mark inside the Triangle with the Android next to it appeared, but no text or anything else is on the screen. I've let it sit for about 15 minutes, and nothing. I also can't do anything by clicking the volume buttons, or the power buttons. I've also unplugged the Phone, held the power button to try to reboot it, held volume-up and power to try to go back into fastboot, but nothing. Should I pull the battery? Why didn't it go into ClockWork RecoveryMod? Command Prompt gave me the whole " sending 'recovery' (3980 KB)... OKAY [ 0.621s]
writing 'recovery'... OKAY [ 0.511s]
finished. total time: 1.132s" thing...
What do I do? I can't just leave it sitting like this forever.
Edit: I unplugged and replugged it a few times, and it rebooted. But I've tried going back to fastboot and going into Recovery, and I get the same screen, over and over. I've even tried flashing CWRM again, and nothing. I'm using 3.0.2.4. Should I just use 3.0.0.5?
When you are in the stock recovery mode and you see the exclamation mark inside the triangle: Just hold the power button and hit volume up and you will get into stock recovery where you can perform a reboot etc.
Just try 3.0.0.5. There is something wrong with clokwork mod it you just went into stock recovery. You should be fine if you follow one of the guides on this forum.
If you still are using the stock rom. This only applies of on stock root rom because the custom rom have the edited already. You must do this. If you don't then you will have to flash clockwork ever time you reboot.
Reboot your Nexus S
Download and install Root Explorer app from Android Market
Open Root Explorer and navigate to etc directory
Tap on the gray box that says Mount R/W
Tap and hold on the file install-recovery.sh and rename this file to install-recovery.sh.old
Once renamed, download and install the app called ROM Manager from Android Market
Once installed, open ROM Manager app and choose Flash ClockworkMod Recovery option.
Hawky_ said:
When you are in the stock recovery mode and you see the exclamation mark inside the triangle: Just hold the power button and hit volume up and you will get into stock recovery where you can perform a reboot etc.
Just try 3.0.0.5. There is something wrong with clokwork mod it you just went into stock recovery. You should be fine if you follow one of the guides on this forum.
Click to expand...
Click to collapse
I tried it again with 3.0.2.5 from http://forum.xda-developers.com/showthread.php?t=988686. Did not work. Went again into Stock Recovery.
jerrycycle said:
If you still are using the stock rom. This only applies of on stock root rom because the custom rom have the edited already. You must do this. If you don't then you will have to flash clockwork ever time you reboot.
Reboot your Nexus S
Download and install Root Explorer app from Android Market
Open Root Explorer and navigate to etc directory
Tap on the gray box that says Mount R/W
Tap and hold on the file install-recovery.sh and rename this file to install-recovery.sh.old
Once renamed, download and install the app called ROM Manager from Android Market
Once installed, open ROM Manager app and choose Flash ClockworkMod Recovery option.
Click to expand...
Click to collapse
I'm a bit confused with your post.
I am still using the Stock Rom, but I don't have root access.
I've tried, after unlocking the Bootloader, going into Rom Manager and Flashing ClockWork, but it tells me first:
"You must root your phone for ROM Manager to function. Superuser was not found at "/system/bin/su" or "/system/xbin.su". (...)"
Then, when I still attempt to flash ClockworkMod, it tells me:
"An error occurred while attempting to run priviliged commands!"
I should have told the full story first.
I was once rooted, but it was through ROM Manager and flashing Clockwork from there. But then I had a few issues with my Wifi, and I decided to flash back Stock Rom. I still had an unlocked Bootloader though, so I thought that just redownloading Rom Manager and flashing CWRM and having Superuser installed would work. It didn't. So I attempted to root all over again, this time, manually.
But, I always go back to square one, it seems, when I try to get into Recovery.
What up with that?
After you flash CWM recovery, go straight into recovery from the fastboot menu. Do not reboot. Do not power off. Flash CWM and when it finishes immediately press volume down to select recovery and then press power to go in.
The Nexus S will overwrite CWM with stock recovery every time the phone boots by default. This could be what is giving you trouble.
Sent from my Nexus S using XDA App
matt2053 said:
After you flash CWM recovery, go straight into recovery from the fastboot menu. Do not reboot. Do not power off. Flash CWM and when it finishes immediately press volume down to select recovery and then press power to go in.
The Nexus S will overwrite CWM with stock recovery every time the phone boots by default. This could be what is giving you trouble.
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
Thank you so much!
That was it!
After I did that, I went straight into Recovery, flash SU, rebooted, went into ROM Manager, Flashed CWRM from there, and boom.
I don't understand why AllGamer's guide didn't already say that could happen. I'll post a comment there.
Thanks again!
EonHawk said:
Thank you so much!
That was it!
After I did that, I went straight into Recovery, flash SU, rebooted, went into ROM Manager, Flashed CWRM from there, and boom.
I don't understand why AllGamer's guide didn't already say that could happen. I'll post a comment there.
Thanks again!
Click to expand...
Click to collapse
No problem.
There is a script located in the /etc folder called install-recovery.sh. it runs every time you boot and installs stock recovery. You have two choices: always use rom manager to flash CWM every time you need to access recovery, or use root explorer to rename install-recovery.sh to install-recovery.sh.bak so that it will not run and will leave CWM installed.
Glad you got it figured out!
Sent from my Nexus S using XDA App
Or a third choice of course would be to install a custom ROM because they tend to not include that script
Sent from my Nexus S using XDA App
EonHawk said:
Thank you so much!
That was it!
After I did that, I went straight into Recovery, flash SU, rebooted, went into ROM Manager, Flashed CWRM from there, and boom.
I don't understand why AllGamer's guide didn't already say that could happen. I'll post a comment there.
Thanks again!
Click to expand...
Click to collapse
If you are talking about this guide then it does warn about this problem. I used the guide to root my nexus s and I followed all his steps, including renaming the necessary file - http://forum.xda-developers.com/showthread.php?t=895545
This is from his 2nd post - called notes:
NOTES:
It's normal to lose the recovery after the reboot, the steps to flash the CW recovery needs to be repeated every time you want to access the CW recovery.
This is due the build in protection in 2.3
As some one pointed it out on another topic, the good thing about this is that you'll never lose the stock recovery of 2.3, thus minimizing the chance of a bricked phone.
If you want to the CW recovery to remain permanently, you'll need to rename /etc/install-recovery.sh to something thing else
buachaille said:
If you are talking about this guide then it does warn about this problem. I used the guide to root my nexus s and I followed all his steps, including renaming the necessary file - http://forum.xda-developers.com/showthread.php?t=895545
This is from his 2nd post - called notes:
NOTES:
It's normal to lose the recovery after the reboot, the steps to flash the CW recovery needs to be repeated every time you want to access the CW recovery.
This is due the build in protection in 2.3
As some one pointed it out on another topic, the good thing about this is that you'll never lose the stock recovery of 2.3, thus minimizing the chance of a bricked phone.
If you want to the CW recovery to remain permanently, you'll need to rename /etc/install-recovery.sh to something thing else
Click to expand...
Click to collapse
Actually I think that guide does have two unnecessary steps that cause confusion. After flashing CWM, the guide instructs the user to power off, power on, and then to access recovery. The user should just access recovery immediately after flashing.
EDIT: I guess the problem is just that the bolded part should be added:
Then back on the SNS select Power Off (Reboot also works)
Power ON the SNS while holding volume up
buachaille said:
If you are talking about this guide then it does warn about this problem. I used the guide to root my nexus s and I followed all his steps, including renaming the necessary file - http://forum.xda-developers.com/showthread.php?t=895545
This is from his 2nd post - called notes:
NOTES:
It's normal to lose the recovery after the reboot, the steps to flash the CW recovery needs to be repeated every time you want to access the CW recovery.
This is due the build in protection in 2.3
As some one pointed it out on another topic, the good thing about this is that you'll never lose the stock recovery of 2.3, thus minimizing the chance of a bricked phone.
If you want to the CW recovery to remain permanently, you'll need to rename /etc/install-recovery.sh to something thing else
Click to expand...
Click to collapse
That's partly my fault, I never went down to the 2nd Post and saw those Notes, but what's the point of not including that already in the steps in the main Post? He could have just told to go straight from Recovery after flashing CWRM, but decided not to.
matt2053 said:
Actually I think that guide does have two unnecessary steps that cause confusion. After flashing CWM, the guide instructs the user to power off, power on, and then to access recovery. The user should just access recovery immediately after flashing.
EDIT: I guess the problem is just that the bolded part should be added:
Then back on the SNS select Power Off (Reboot also works)
Power ON the SNS while holding volume up
Click to expand...
Click to collapse
I think he should just have instructed to place the SU zip on the root of the SD card before flashing CWRM. That way, there wouldn't be a need to reboot to mount the SD to place SU, that way potentially losing the CWRM.
I was using this guide http://forum.xda-developers.com/showthread.php?t=1078019 to unlock, install CWM, and then root. Unlocking was fine, installing that version of CWM seemed okay, but when I enter command "fastboot reboot", then hold down the volume - button after 3 seconds of the Moto logo showing, then pressing the volume + key, I get only 1 option....-->Android Recovery. I press the Volume + key, get "Entering Android Recovery Mode", and below that "Reading ODM Fuse 1", then the screen switches to an android with a yellow hazard sign in his tummy.
From that screen, if I press Volume + and power, I see:
Android system recovery <3e>
Use volume keys to highlight; power button to select.
reboot system now
apply update from USB drive
wipe data/factory reset
wipe cache partition
I don't get a choice to apply something from the microSD card I have installed with the WiFi_RootTool_3.1.zip I put on the card.
Has anyone had this happen? I can't ask in the development forum. I also just got the Xoom back from a repair, and it was wiped to stock, then I did the 3.1 update when I got it back this morning. Is the fuse thing something they may have done to block rooting?
Have you tried reformat your sd card?
becu4xda said:
Have you tried reformat your sd card?
Click to expand...
Click to collapse
I'll try that. But would that stop it from going into recovery?
becu4xda said:
Have you tried reformat your sd card?
Click to expand...
Click to collapse
I reformatted my sd card, but I still can't get CWM to work and boot into recovery. Same message-
-->Android Recovery
Entering Android Recovery Mode
Reading ODM fuse: 1
And that's it....no options to load the root zip from an SD card or anything. Is there a way to push root without using the SD card? Or is that ODM fuse thing making it impossible?
becu4xda said:
Have you tried reformat your sd card?
Click to expand...
Click to collapse
Nothing at all to do with CWM.
OP: Try flashing the recovery again. To get into recovery, type adb reboot recovery, or use an app such as Quick Boot.
Edit: You can't use CWM to root, you need to do that first.
siscim23 said:
Nothing at all to do with CWM.
OP: Try flashing the recovery again. To get into recovery, type adb reboot recovery, or use an app such as Quick Boot.
Edit: You can't use CWM to root, you need to do that first.
Click to expand...
Click to collapse
I have to root first? I'm not sure how to do it....can't find any other methods of rooting 3.1....everything on Google just points me to the same method, using the SD card that won't work cuz I can't boot into recovery. Ugh.
Hey jump hour PM me.
Hey guys,
I called JumpHour and we tried to troubleshoot this over the phone. We aren't able to get into the recovery because of error "reading odm fuse: 1". The OP is using Windows 7 64 BIT and has the SDK installed properly. He updated the sources and installed them so those are up to date. We also verified that USB debugging was enabled and that the correct files were in the tools section in the SDK folder.
We ran the commands:
adb reboot bootloader
fastboot-recovery ........ (we typed it in correctly accoriding the thread)
fastboot reboot
and we get that error message.
This was all initiated while the Xoom was powered on. JumpHour stated that he had to send his Xoom back to Moto because his Xoom got messed up during the re-locking process when he unrooted a one click root and re-locked.
We then went ahead and downloaded the recovery image again and replace the one in the tools folder. We ran the commands again and we were getting the same error.
Does anyone have any idea what is going on with this process? Are we missing something? Is something broken?
Get the official images. I am assuming you have a USA 3g or wifi model.
Follow the steps to return the device to stock. But do not issue the reclock bootloader command. There is no need to relock.
From there power up the device and turn on USB debugging.
Then adb reboot into recovery. That should bring you to the stock recovery.
If all goes well from here just do what ever else you where intending to do in the first place.
You most likely can just flash the stock recovery but I would just do a full flash back to official images minus relocking bootloader.
Sent from my Xoom using Tapatalk
Then let the ota update it to 3.1 and so on.
Sent from my Xoom using Tapatalk
What's the status JumpHour? Did you get it to work. I told you it may have been due to the images. Hopefully that fixes your issue. Take care dude.
gqstatus0685 said:
What's the status JumpHour? Did you get it to work. I told you it may have been due to the images. Hopefully that fixes your issue. Take care dude.
Click to expand...
Click to collapse
Hi, thanks for the response. I'm gonna try it now. I was up REALLY late last night, and just got up a little while ago. I'll definately respond after I try it out.
Finally, I did it!
Okay, I fixed it finally. Reloaded the stock images, and it's now rooted with SD support. Yay! Only took 2 days!
Thanks for all your help guys.
Can reflashing with original images fix recovery mode mount problem?
Does any window is flashing to the original images can restore access to the sdcard IF the recovery mode in the official recovery mode (not CWM) says that you cannot mount the sdcard?
Nexus S 4g
I did the one click root month or 2 ago and gained unlock and SU permissions. My phone updated to 2.3.7, last week. I decided to load CWM today and discovered I no longer had permissions. I've tried several things and am stuck.
Nothing in ROM manager will work properly. I get message: "error occured while attempting to run priviledged commands" for fix permissions, or load other CWMR (that worked in the past I had to put an earlier one in to be able to access recovery in bootloader). If I try to backup, apply .zip, etc it just never reboots.
If I go to bootloader and go into recovery, each time it shows unlock, then the triangle with an exclamation point (so I can't backup, restore previous backup, anything)
I managed to grab SU 3.0 and force it to install over my existing 2.3.6, it did, sees my su (which is in system/bin which I've read is a problem ) as being outdated and wants to update it, fails each time.
So someone smarter than me please advise. My phone is functioning nicely without FCs or other issues, a normal boot or reboot goes fine, but I fear for the day I really need my backup. Not to mention frustrating that I seem to be locked out from making any changes now.
Thanks, Travis
sobamaflyer said:
Nexus S 4g
I did the one click root month or 2 ago and gained unlock and SU permissions. My phone updated to 2.3.7, last week. I decided to load CWM today and discovered I no longer had permissions. I've tried several things and am stuck.
Nothing in ROM manager will work properly. I get message: "error occured while attempting to run priviledged commands" for fix permissions, or load other CWMR (that worked in the past I had to put an earlier one in to be able to access recovery in bootloader). If I try to backup, apply .zip, etc it just never reboots.
If I go to bootloader and go into recovery, each time it shows unlock, then the triangle with an exclamation point (so I can't backup, restore previous backup, anything)
I managed to grab SU 3.0 and force it to install over my existing 2.3.6, it did, sees my su (which is in system/bin which I've read is a problem ) as being outdated and wants to update it, fails each time.
So someone smarter than me please advise. My phone is functioning nicely without FCs or other issues, a normal boot or reboot goes fine, but I fear for the day I really need my backup. Not to mention frustrating that I seem to be locked out from making any changes now.
Thanks, Travis
Click to expand...
Click to collapse
You're "locked out" because you don't actually have root access. The OTA update chmods /system recursively (and as a result /system/bin and /system/xbin).
The triangle with the exclamation mark is the stock recovery (applied with the OTA update).
I'm not entirely sure what you've tried as it's a very easy process.
-Download CWM for your device - flash it using fastboot.
-Boot into recovery and flash the su binary via recovery. This will place the binary appropriately as well as chmod it.
-Done
-Profit?
krohnjw said:
You're "locked out" because you don't actually have root access. The OTA update chmods /system recursively (and as a result /system/bin and /system/xbin).
The triangle with the exclamation mark is the stock recovery (applied with the OTA update).
I'm not entirely sure what you've tried as it's a very easy process.
-Download CWM for your device - flash it using fastboot.
-Boot into recovery and flash the su binary via recovery. This will place the binary appropriately as well as chmod it.
-Done
-Profit?
Click to expand...
Click to collapse
Oddly I was getting the triangle intermittently from the get go, but I had been able to get around it by applying an earlier clockworkmod version in Rom Manager. I'm not able to do that now.
My whole problem is I'm unable to do anything at all in Fastboot. If I go to "recovery" to try and apply anything I get the triangle.
Am I missing something?
It does say "Lock State - Unlocked" in fastboot if that means anything.
sobamaflyer said:
Oddly I was getting the triangle intermittently from the get go, but I had been able to get around it by applying an earlier clockworkmod version in Rom Manager. I'm not able to do that now.
My whole problem is I'm unable to do anything at all in Fastboot. If I go to "recovery" to try and apply anything I get the triangle.
Am I missing something?
It does say "Lock State - Unlocked" in fastboot if that means anything.
Click to expand...
Click to collapse
Yeah, you have the stock recovery. You can't apply a new recovery through rom manager because the su binary doesn't have the appropriate permissions since the update.
Boot into the boot loader (Vol up and pwr). Don't go into recovery. Use fastboot from the boot loader to load CWM. Boot into CWM after flashed and flash the SU binary (mount /system first). After this boot up and delete/rename /etc/install-recovery.sh so that it won't overwrite CWM on each reboot. Install CWM again from Rom Manager or via fastboot (as it was overwritten on boot). Done.
Since you are being nice enough to try and help an id10t (apparently) and others may have the same issue and search this I'll ask the dumb questions. (I did a bit of googling a min. ago and found others with the same things I see but didn't get any further...).
When you say "go into Fastboot" you mean opening SDK Manager on my PC while I'm in the Boot Loader Screen?
At the bottom of the screen I see:
USB Control Init
USB Control Init End
[plug in usb get:]
STANDARD_SET_CONFIGURATION
Nothing shows up in SDK, I have the black CMD screen up but can't type anything at all in it?
......I did try loading pda_net (not sure what to do with that? but it was mentioned elsewhere) and I get a grey message at the bottom of the screen that says "FASTBOOT STATUS - FAILinvalid Command"
sobamaflyer said:
Since you are being nice enough to try and help an id10t (apparently) and others may have the same issue and search this I'll ask the dumb questions. (I did a bit of googling a min. ago and found others with the same things I see but didn't get any further...).
When you say "go into Fastboot" you mean opening SDK Manager on my PC while I'm in the Boot Loader Screen?
At the bottom of the screen I see:
USB Control Init
USB Control Init End
[plug in usb get:]
STANDARD_SET_CONFIGURATION
Nothing shows up in SDK, I have the black CMD screen up but can't type anything at all in it?
......I did try loading pda_net (not sure what to do with that? but it was mentioned elsewhere) and I get a grey message at the bottom of the screen that says "FASTBOOT STATUS - FAILinvalid Command"
Click to expand...
Click to collapse
Fastboot is merely a command line tool used for various operations on the device. Mainly though you'll use it to flash an image to a specific partition.
You'll need to boot the device into the boot loader (hold Vol up and power on).
Plug the device in via USB.
Open a command windows in the tools or platform-tools folder of the SDK (depending on your version of the SDK, where the fastboot.exe can be found) and issue the fasboot devices commmand. This should display the serial of any connected devices. If this comes back blank there is an issue with the installed driver. Reinstall the USB driver for the device using the supplied driver from an updated SDK.
Assuming fastboot devices shows one device you now can flash a recovery to the device. Download the appropriate recovery for your device (i9020(a), i9203 or NS 4G) http://mirror.sea.tdrevolution.net/cm/recoveries/. Place this file in the same directory for simplicity.
At this point you can flash your recovery.
fastboot flash recovery file.name.you.downloaded.img
If it is not in the same directory you can alternatively pass the full path to the image.
You now have a custom recovery installed. Select Recovery from the bootloader menu to now boot into this recovery.
Assuming you've already downloaded the su binary and it is on your SD card, mount /system from within CWM and then chose to install zip and select this from the SD card. You now have root access.
Now that a panic attack is settling...
I think I'm getting somewhere but not yet where I want to be. I go to Bootloader, I connect my USB and don't get anything different than above from my sdk tools menu (unusable cmd screen, fail showing on my phone). What does [eventually] work is going back to my "nexus S one click root" folder and clicking run.bat (as fastboot.exe and adb.exe in that folder also do the nothing).
This run.bat reads some sort of fail and boots my phone telling me that debugging is not checked (which it is) and takes me directly to there, then the cmd screen tells me to press enter when I've turned on the [already checked] usb debugging toggle.....what the hell I press enter. Now it goes into the old beautiful CWMR (3.0.xxxx) screen where I'm able to apply .zips, backup etc.
(luckily I think ahead and do a backup right this min.)
Then I go from that screen and decide to apply my new CM7.zip that started all this, I apply that and get a bootloop on the CM7 boot screen.......crap......I go clear my davlik and cache and install CM7 again. Same thing.....crap......
I try restoring my original backup from 9/5/11 I made right after first unlocking my phone.......CM7 bootloop screen.....dammmmiiiiit
I try restoring backup from 9/12 I made after getting everything just like I wanted it.......CM7 bootloop screen.......uh oh, panic beginning.
I restore the backup from a few lines ago, my phone comes back (thank god)
So:
-I have to have the right USB driver in my laptop because something from sdk ultimately talked to my phone?!
-Clockworkmod recovery 5.xxxx has never worked quite right for me, apparently 3.xxxx is still my magic answer?!
-Now that I've gotten this far should I try the same process to get back to my CWMR 3.xxxx screen and put some different files in my root to use than what I've done to this point?
....again, I apologize if I'm being myopic or asking dumb questions. I often say I only know just enough to be dangerous.
[SOLVED] - maybe/sort of
Between reading (and re-reading) the help above and continued research on my own I [think] I solved my problem.
I found the following 2 links:
http://theunlockr.com/2009/10/06/how-to-set-up-adb-usb-drivers-for-android-devices/
http://theunlockr.com/2010/12/17/how-to-root-the-samsung-nexus-s/
And basically started over from scratch, I deleted what I'd put in my pc and re-loaded using those instructions (in the right place, the right way). Doing this I was able to pull up a cmd window and this time it properly accessed my phone. I got it to fastboot recovery - load CWM 5.0... and from there got into my recovery menus on my phone this time.
One curious thing....I tried the part VI in "how to root the samsung" ...""stop the phone uninstalling the custom recovery image"...... I've tried several things there but still get an error that it is read only.
....I went on to install CM7, and it consequently updated right after to the latest CM7, At this moment I have full permissions, superuser access, was able to make a backup of yesterday, the CM7 this morning and then CM7.1.0.1 that loaded.
Will I ultimately have the same issue as before? But be able to overcome it in the same manner when I want to?
Thanks for the help
This is why one click methods are bad. When a problem arises you have no clue what to do because a software did it for you the first time. Glad you got it figured out.
Sent from my Nexus S 4G using xda premium
All I get now is the android with the yellow explanation. I know the step I missed..
I am trying the one in this thread
http://forum.xda-developers.com/showthread.php?t=1154947
1. Download repacked stock rom, stock recovery and stock firmware 3.1 update:
Repacked stock rom:http://dl.project-voodoo.org/transformer-roms/3.0.x/
Stock recovery:http://forum.xda-developers.com/atta...2&d=1306284085
http://usa.asus.com/Eee/Eee_Pad/Eee_...F101/#download
2. Copy the files onto your micro sd. Unzip stock update and place the Asus folder on root of sd card.
3. Boot into recovery. install repacked stock rom. Wipe all data, cache partition and dalvik cache. Reboot the tablet let it boot up then shut it down.
4. Boot into recovery and install stock recovery. Wipe all data, cache partition and dalvik cache. And then reboot and shut down.
5.
a.Boot into OS, there should be a notification for an update. select it and follow instuctions. Or
b.Boot into recovery(it should be stock recovery) then press up volume button within five seconds and the official update should install.
6. It should reboot automatically. When it does check about tablet info and check your apps to make sure the Super User icon is gone.
I forgot to install the stock recovery and immediately went to the next step. So my TF will boot now but I have no recovery to go too..
How do I get the recovery back?
acdcking12345 said:
All I get now is the android with the yellow explanation. I know the step I missed..
I am trying the one in this thread
http://forum.xda-developers.com/showthread.php?t=1154947
1. Download repacked stock rom, stock recovery and stock firmware 3.1 update:
Repacked stock rom:http://dl.project-voodoo.org/transformer-roms/3.0.x/
Stock recovery:http://forum.xda-developers.com/atta...2&d=1306284085
http://usa.asus.com/Eee/Eee_Pad/Eee_...F101/#download
2. Copy the files onto your micro sd. Unzip stock update and place the Asus folder on root of sd card.
3. Boot into recovery. install repacked stock rom. Wipe all data, cache partition and dalvik cache. Reboot the tablet let it boot up then shut it down.
4. Boot into recovery and install stock recovery. Wipe all data, cache partition and dalvik cache. And then reboot and shut down.
5.
a.Boot into OS, there should be a notification for an update. select it and follow instuctions. Or
b.Boot into recovery(it should be stock recovery) then press up volume button within five seconds and the official update should install.
6. It should reboot automatically. When it does check about tablet info and check your apps to make sure the Super User icon is gone.
I forgot to install the stock recovery and immediately went to the next step. So my TF will boot now but I have no recovery to go too..
How do I get the recovery back?
Click to expand...
Click to collapse
Get yourself the nvflash tool (You just have too look for it in Transformer Q&A Section) unzip it, install the drivers, if You haven't yet, get a nvflashable version of a rom (PRIME Rom has got an nvflash version) unzip the nvflash Rom to the nvflash tool, so recovery.img system.img and so on are in the same folder as download.bat and so on.
finally enter in APX mode on your transformer, and run download.bat.
when it's done, your tablet should restart.
Sent from my Asus tf101 running official Ice Cream Sandwich.
The android with yellow exclamation point is your stock recovery.
Try taking the "update" file out of the Asus folder and put it directly on the root of your sd card.
If that still don't work do the two file method.
well, I did the download.bat. But I turned it off when it just showed two lines.
Now it wont turn on at all..I am really screwing this up.
It just wont turn on at all..But it has a full charge. I knew I should have left it alone
acdcking12345 said:
well, I did the download.bat. But I turned it off when it just showed two lines.
Now it wont turn on at all..I am really screwing this up.
It just wont turn on at all..But it has a full charge. I knew I should have left it alone
Click to expand...
Click to collapse
What's the serial # of your TF?
baseballfanz said:
What's the serial # of your TF?
Click to expand...
Click to collapse
It starts with a B60
It now says entering NVS Flash recovery mode. Nothing else
acdcking12345 said:
It starts with a B60
Click to expand...
Click to collapse
Use NVFlash unbricking method
http://www.tabletroms.com/forums/tr...stock-3-2-recovery-roms-unbricking-tools.html
acdcking12345 said:
well, I did the download.bat. But I turned it off when it just showed two lines.
Now it wont turn on at all..I am really screwing this up.
It just wont turn on at all..But it has a full charge. I knew I should have left it alone
Click to expand...
Click to collapse
You should not have turned it off. When the installation process was done, your tablet should start up by itself.
Try it again, but this time wait for the tablet to start up.
I redid it and followed it exactly as outlined.
It is now installing the stock update. I think I am ok now.
I appreciate all the help..
Hello, I've recently completed the Bootloader unlocking method with Easy Ace Root Tool. Bootloader is unlocked and SHIP S-ON, I need to flash a rom. These roms require S-OFF and have no method to flash them with only an unlocked bootloader and S-ON.
So let me get this straight, us 'low level' and unexperienced users are left without any method to gain S-OFF privileges without following the vague guide provided at tau(dot)shadowchild(dot)nl/attn1/?p=411 Yeah... I can't.
Trying to find alternate methods I have only gone in circles and keep running into old how-to guides. The more I read the more confused I become. I hope someone can point me in the right direction, I would really appreciate it!
Thanks,
Ninjewbag
You don't need S-Off. Flash a ROM in recovery, then flash the ROM zip's boot.img in fastboot.
bananagranola said:
You don't need S-Off. Flash a ROM in recovery, then flash the ROM zip's boot.img in fastboot.
Click to expand...
Click to collapse
Good deal, thanks for the reply!
I put the ROM Android Revolution HD 9.0 on the root of my SD card, booted in recovery mode and chose the recovery option, I got the red exclamation mark icon so I pressed VOL up + power button which didn't work so I pulled the battery. I tried all above steps again but this time I was able to successfully get into "Android system recovery <3e> with VOL up + power button. With 4 options:
Reboot system now
Apply update from sdcard
wipe data/factory reset
wipe cache partition
I chose the option to wipe all data, said it could not find Efolder name)'s and "data wipe completed successfully".
Then I wiped cache, then chose the option to apply update from sdcard, it said "Invalid operation" then "success rebooting by reason 00" and proceeded to reboot by itself.
Phone factory reset, I rebooted into recovery again with the same red exclamation mark error. Pressed Vol up + power and back into "Android system recovery". At the bottom in yellow text it says "E: Can't open /cache/recovery/command". I tried another "update from SD card" and recieved error: "success rebooting by reason 00" and reboots.
I don't have a nandroid backup as I read I needed Root to make one, but the phone still works fine as far as I can tell. I don't have a working simcard in it though.
Also from what I've read my eMMC chip may be fried so it looks like I'm retiring early. I'll keep an eye on this thread among others with the same problems.
Cheers,
Ninjewbag
Volume + and power brings you to the factory recovery; you need to use vol - have you flashed a different recovery? If not, flash 4ext recovery through fast boot and try again
RadRacer said:
Volume + and power brings you to the factory recovery; you need to use vol - have you flashed a different recovery? If not, flash 4ext recovery through fast boot and try again
Click to expand...
Click to collapse
Thank you for the info! No luck finding the 4ext .IMG file anywhere yet, they're all dead links. I have the 4ext recovery.APK but that doesn't do me any good since I don't have root. Still looking and thanks again.
http://forum.xda-developers.com/showthread.php?p=31211732
ninjewbag said:
Thank you for the info! No luck finding the 4ext .IMG file anywhere yet, they're all dead links. I have the 4ext recovery.APK but that doesn't do me any good since I don't have root. Still looking and thanks again.
Click to expand...
Click to collapse
You can install the app and then open the app and use it to manually download the recovery zip which you can flash or copy it to your pc and extract the recovery.img file and flash with fastboot. It's a good idea to familiarize yourself wiht the adb and fastboot utils as they come in handy.
turboyoshi said:
You can install the app and then open the app and use it to manually download the recovery zip which you can flash or copy it to your pc and extract the recovery.img file and flash with fastboot. It's a good idea to familiarize yourself wiht the adb and fastboot utils as they come in handy.
Click to expand...
Click to collapse
Thanks for the reply but as for installing the 4ext free updater version, it wasn't on the market so I used android injector to place and install that APK. None of the options worked as they all give the same error "it seems your phone is not rooted, this option will not function" etc.
RadRacer said:
http://forum.xda-developers.com/showthread.php?p=31211732
Click to expand...
Click to collapse
Nice! Wasn't expecting to find the 4ext recovery within the adbfastboot.zip. With that I was able to move on, create a nandroid and successfully install a custom rom, thanks! Was a little scared after rebooting, it took around 5 minutes to load past the "quietly brilliant" screen but is working fine now nonetheless.
ninjewbag said:
Nice! Wasn't expecting to find the 4ext recovery within the adbfastboot.zip. With that I was able to move on, create a nandroid and successfully install a custom rom, thanks! Was a little scared after rebooting, it took around 5 minutes to load past the "quietly brilliant" screen but is working fine now nonetheless.
Click to expand...
Click to collapse
Glad to help. Wanna hit thanks?