[Q] force atrix into usb bootloader? - Atrix 4G Q&A, Help & Troubleshooting

ok, I've looked everywhere else but I haven't been able to find the answer. My friend was trying to put gingerbread on his atrix 4g (att) and the battery died halfway through. Now we borrowed a charged battery from a friend and now when ever we turn it on it says
SVF 105:1:2
failed to boot 0x1000
then waits a few seconds then flashes "starting hv flash recovery" then turns off. The hv part might be wrong. But no matter what I press the device will not go into usb bootloader for me to put a new sbf on
any help would be much appreciated. Thank you for your time

so you can't get into fastboot mode either?

How were you installing gingerbread?

turl1 said:
How were you installing gingerbread?
Click to expand...
Click to collapse
well when my friend was doing it it was rsd lite 4.6 i think

lifetaker said:
well when my friend was doing it it was rsd lite 4.6 i think
Click to expand...
Click to collapse
if you can only get into NVFlash mode, then i'm pretty sure that you're not gonna be able to fix it. i don't believe we have the nvidia flashing tools needed to get past this option.

Alcapone263 said:
if you can only get into NVFlash mode, then i'm pretty sure that you're not gonna be able to fix it. i don't believe we have the nvidia flashing tools needed to get past this option.
Click to expand...
Click to collapse
so what your telling me, is that under no circumstance, at all. there is no way to ever fix this phone. ever, in a million years. there is no way to force the phone into bootloader?

yea you need to charge the battery outside the phone then check the dev section there is a program just fir your situation!
A soft brick, in this case, is when you make a bad edit to your framework files and the phone won't fully boot and starts flashing a red LED at you.
There is one catch, you only get about 1-2min to do all of this before the phone reboots on its own. If that happens, do SuperOneClick steps again and continue where you left off. Better yet, build a script to do it all for you 
Power off your device
Enter Fastboot:
Hold Volume down + power until you see Fastboot at the top left
Use volume down to scroll down to "Early USB Enumeration" (only shows one item at a time, if you pass it, keep going down, up selects)
Press Volume up to select
Wait for ADB to enable, run "Shell Root" from SuperOneClick, wait until it says you have root.
Enter adb shell from command line, You should have root(#) access:
adb shell
Mount the system directory as read/write:
mount -o rw,remount /dev/block/mmcblk0p12 /system
Make a new directory on /data for your recovery files: (sdcard wont be mounted yet)
mkdir /data/recover
Exit adb shell:
exit
Push your known working files to the new directory:
adb push /path/to/local/file.ext /data/recovery
Enter adb shell from command line:
adb shell
Copy your newly pushed recovery files to their proper location:
cp /data/recover/services.jar /system/framework
cp /data/recover/framework.jar /system/framework
cp /data/recover/famework-res.apk /system/framework
Reboot:
reboot now

ltdanno360 said:
yea you need to charge the battery outside the phone then check the dev section there is a program just fir your situation!
A soft brick, in this case, is when you make a bad edit to your framework files and the phone won't fully boot and starts flashing a red LED at you.
There is one catch, you only get about 1-2min to do all of this before the phone reboots on its own. If that happens, do SuperOneClick steps again and continue where you left off. Better yet, build a script to do it all for you 
Power off your device
Enter Fastboot:
Hold Volume down + power until you see Fastboot at the top left
Use volume down to scroll down to "Early USB Enumeration" (only shows one item at a time, if you pass it, keep going down, up selects)
Press Volume up to select
Wait for ADB to enable, run "Shell Root" from SuperOneClick, wait until it says you have root.
Enter adb shell from command line, You should have root(#) access:
adb shell
Mount the system directory as read/write:
mount -o rw,remount /dev/block/mmcblk0p12 /system
Make a new directory on /data for your recovery files: (sdcard wont be mounted yet)
mkdir /data/recover
Exit adb shell:
exit
Push your known working files to the new directory:
adb push /path/to/local/file.ext /data/recovery
Enter adb shell from command line:
adb shell
Copy your newly pushed recovery files to their proper location:
cp /data/recover/services.jar /system/framework
cp /data/recover/framework.jar /system/framework
cp /data/recover/famework-res.apk /system/framework
Reboot:
reboot now
Click to expand...
Click to collapse
wont go into fastboot or i would have used that already

also i have a video of the phone. but i dont have enough posts to post the link. dont get mad mods
watch?v=XuV5A6mH-Qw
of course just post this at the end of a youtube url

lifetaker said:
also i have a video of the phone. but i dont have enough posts to post the link. dont get mad mods
watch?v=XuV5A6mH-Qw
of course just post this at the end of a youtube url
Click to expand...
Click to collapse
no, this is a hard brick to your Atrix. it's a nice paperweight now.
did you attempt to flash a froyo .sbf on a gingerbread Atrix?

Alcapone263 said:
no, this is a hard brick to your Atrix. it's a nice paperweight now.
did you attempt to flash a froyo .sbf on a gingerbread Atrix?
Click to expand...
Click to collapse

Alcapone263 said:
no, this is a hard brick to your Atrix. it's a nice paperweight now.
did you attempt to flash a froyo .sbf on a gingerbread Atrix?
Click to expand...
Click to collapse
it was the other way around. but now i guess ill sell it on ebay for $200. its still in perfect condition. lets see what happens. thanks guys

lifetaker said:
it was the other way around. but now i guess ill sell it on ebay for $200. its still in perfect condition. lets see what happens. thanks guys
Click to expand...
Click to collapse
Why would you sell a broken phone on Ebay and claim it's in perfect condition?
Sent from my MB860 using xda premium

Related

Hangs on boot to recovery mode and normal mode [Solved! :)]

Hello people
I think my HTC Hero is what you call softbricked.
When I hold Home + Power on to go to recovery mode I get this single line of text:
Build : RA-hero-v1.5.2
If I hold Home and press power on the text disappears leaving an all black screen. Pressing home + power on again brings the text back.
When I boot normally it just keeps saying "Hero"
I think I did a full wipe, installed VillainROM 6.0.0 and then did a OTA update to VillainROM 6.1.0. I did notice the latest rom being rather slow and hanging sometimes. Then three days ago it froze. I pulled the battery and when I put it back in I was left with what I've described above.
Can't access VillainROM's official website
Another frustrating thing is that w w w. villainrom .co .uk has seemed down to me this whole softbrick-period. But they've announced a new version and no one have commented on their site being down. Apparently I'm the only one who can't access it.
Vol. down + power on
I've never used this boot mode. But it's the only one which seems to work.
HBOOT says Sd checking and all the tests results in:
No image! or No image or wrong image!
FASTBOOT just gives a red box with the white text FASTBOOT in it.
What can i do?
I did a nandroid backup before installing VillainROM 6.0.0 but I can't access recovery mode.
I would like to install the official 1.5 RUU-rom but HTC Sync can't find my phone, neither can adb shell.
I can insert the SD card in my computer and put an update.zip file in the root. Is this a solution? I don't know how to make the phone boot the update.zip file or how this works.
Sorry for this long post. I've been searching the web ever since thursday without any luck. So now I'm just putting all I've experienced out.
I hope someone can help me. I would be very glad
Alright, if you can get to the fastboot screen, this is what you should do:
Plug your hero in fastboot mode into a computer with the latest android sdk installed.
DL the latest recovery for your device: I don't think I can post links yet so search the forum for Amon RA's recovery (1.6.2) and place it in the tools folder of the sdk.
Then:
Open a command prompt (or terminal for linux, idk for mac)
Go to the tools folder with cd
(./)fastboot boot recovery-RA-hero-v1.6.2.img
(./ is for linux ^^,) And that should normally work
From there your best bet is to use Nandroid to recover one of your backups.
Thank you for your response
But I got an error:
Code:
C:\android-sdk-windows\tools\fastboot boot recovery-RA-hero-v1.6.2.img
downloading 'boot.img' ... FAILED (remote: not allow)
finished. total time: 0.010s
The site I downloaded the recovery image from suggestion this installation:
via fastboot + adb -> In case you don't have a custom recovery, so when you get signature fail errors
Code:
adb shell reboot bootloader fastboot boot recovery-RA-hero-v1.6.2.img adb shell mount /sdcard adb push recovery-RA-hero-v1.6.2.img /sdcard/recovery-RA-hero-v1.6.2.img adb shell flash_image recovery /sdcard/recovery-RA-hero-v1.6.2.img adb shell reboot
I've also tried this but it resulted in: error: device not found
I've noticed how my phone says "fastboot usb" when connected to my computer.
Re: Hangs on boot to recovery mode and normal mode
NessGuard said:
Thank you for your response
But I got an error:
Code:
C:\android-sdk-windows\tools\fastboot boot recovery-RA-hero-v1.6.2.img
downloading 'boot.img' ... FAILED (remote: not allow)
finished. total time: 0.010s
The site I downloaded the recovery image from suggestion this installation:
via fastboot + adb -> In case you don't have a custom recovery, so when you get signature fail errors
Code:
adb shell reboot bootloader fastboot boot recovery-RA-hero-v1.6.2.img adb shell mount /sdcard adb push recovery-RA-hero-v1.6.2.img /sdcard/recovery-RA-hero-v1.6.2.img adb shell flash_image recovery /sdcard/recovery-RA-hero-v1.6.2.img adb shell reboot
I've also tried this but it resulted in: error: device not found
I've noticed how my phone says "fastboot usb" when connected to my computer.
Click to expand...
Click to collapse
Have you flashed the official 2.1 rom thats been floating round?
Sent from my HTC Hero using Tapatalk
AndroHero said:
Have you flashed the official 2.1 rom thats been floating round?
Click to expand...
Click to collapse
No, I haven't.
Just now I did this:
Code:
C:\android-sdk-windows\tools\adb devices
List of devices attached
And none was shown...
Then I did:
Code:
C:\android-sdk-windows\tools\fastboot devices
HT97TL903447 fastboot
Is this some sort of serial number of my phone?
Re: Hangs on boot to recovery mode and normal mode
Your sd card is seen by your phone or not ?
sebxd said:
Your sd card is seen by your phone or not ?
Click to expand...
Click to collapse
How can I check this?
Hboot says Sd checking and all the tests results in:
Code:
No image! [I]or[/I] No image or wrong image!
The site isn't down, but some people can't get to it due to their DNS setup.
Use 8.8.8.8 and 8.8.4.4 to get it, or go to http://villainrom.grense.no/villainrom.co.uk to get in.
Re: Hangs on boot to recovery mode and normal mode
Mmm if i'm right you can't boot normaly ? It's strange..
Have you tried to boot without your sd card ?
I don't really know what the answer of fastboot means..
anon2122 said:
The site isn't down, but some people can't get to it due to their DNS setup.
Use 8.8.8.8 and 8.8.4.4 to get it, or go to
[url not allowed] to get in.
Click to expand...
Click to collapse
Thanks, but I think I will just stick to this forum. Hope I can get a solution
sebxd said:
Mmm if i'm right you can't boot normaly ? It's strange..
Have you tried to boot without your sd card ?
I don't really know what the answer of fastboot means..
Click to expand...
Click to collapse
Yes, I have tried booting without SD card and without simcard aswell. My simcard is now in a good old Nokia 3310
I have updated the radio earlier
A while ago I updated the radio to this version: 63.18.55.06JU_6.35.09.26
Is that an android 2.1-radio? And is that what's causing "not allow" when running fastboot flash?
What recovery image would I then be allowed to flash? An official one?
Or is it my bootloader (that's SPL, right?) that needs to be flashed to a version that allows the fastboot flashing?
I haven't been able to find a guide on flashing SPL on HTC Hero.
Is this the way to go?
Still need help or is this now sorted?....
It's now working
My phone is now working. I did the following:
1. Connected my phone to a computer with HTC Sync and drivers installed.
2. Started the bootloader on my phone (vol. down + power on, hold until bootloader starts).
3. Pressed back to start fastboot. It said fastboot usb because it was connected to my computer.
4. I tried to install an official 1.5 RUU rom. The phone responded and began the process. It cleared/deleted some caches/files or something. But then my computer and my phone said that the ROM installation had failed and that I should find the right rom.
5. Somehow this cleaned up the phone so I now could boot in recovery mode as I used to (I didn't try a normal boot, so can't say if that worked). I did a full wipe and flashed a custom rom (not VillainROM 6.0.0 ).
Even though VillainROM has made me sad I will now go for VillainROM 10.
Wish me luck
And thanks for your responses.
Brilliant. Just edit the title of your thread to put [SOLVED] on.
And good luck, but i'm sure you wont need it.
EDIT...... Excellent, done it already.
ddotpatel said:
EDIT...... Excellent, done it already.
Click to expand...
Click to collapse
Hehe, yes, even though it's my first post I am a little bit smart
Oh nice ! You have done it ! It is really smart indeed and I'm happy for you !
its not solved for my hero
i tried everything within last two days. but i havent succeess. (i tried your solition too)
i did nondroid backup and then restore. finaly my phone doesnt open.
and after i have given the same your errors (from adb and phone)...
but i havent success..
where i do wrong?
thanks...
Can you explain what you did, what are the errors and when does it appears please
EDIT...... Excellent, done it already.
Click to expand...
Click to collapse
Hehe, yes, even though it's my first post I am a little bit smart
Click to expand...
Click to collapse
Indeed. I'm sorry, I never meant to sound like an ass.
-------------------------------------
Sent via the XDA Tapatalk App

Predictions for exact root date of the HTC Evo??? 3D

I'm predicting 8/1/2011
anyone bets bets? 5 dollars on June 23
I think it'll be a lot quicker than that.. Probably even before July. All the great Evo devs are switching to the 3VO says myn.
it will either be really quick or quite a while.
June 26th
This way they have a weekend to work on it.
dont really care since im keeping the phone root or not.
Tomorrow!
Sent from my PC36100 using XDA App
I bet it's already rooted and those responsible are keeping a tight lip about it.
erikivy said:
I bet it's already rooted and those responsible are keeping a tight lip about it.
Click to expand...
Click to collapse
If I had it rooted I'd post some proof without actually giving away the way it was rooted.
firemedic1343 said:
If I had it rooted I'd post some proof without actually giving away the way it was rooted.
Click to expand...
Click to collapse
Good point. It would be fun to tease the masses.
erikivy said:
Good point. It would be fun to tease the masses.
Click to expand...
Click to collapse
Got the ***** rooted
READ THIS GUIDE CAREFULLY SEE POST TWO FOR FAQ OR SEARCH THE THREAD.
Presenting the ONE AND ONLY surefire root method that backs up your RSA KEYS prior to rooting !!!!
Also I am aware that unrevoked has out their new tool. However while I was sitting in IRC, I saw many that it wasnt working for. So Until there is a surefire, easy method, I will keep this thread updated.
Credit goes to:
amoamare (Initial method)
toast (fake recovery and script)
unrevoked (thanks for your app)
amon_ra (fixed custom recovery)
chris1683 (thanks for the rom) (sprintlovers)
ryanza (z4root)
illogos, epicroot, xHausx, TrevE, Chubbzlou (Testing)
BooDaddy (RSA Backup Info)
and who ever else I missed
Help me finance my Vette!
zikronix
Disclaimer and well a little fun:
This has been tested on many phones and it worked fine...but if it breaks your **** dont come cry to me about it...you knew the risks! No one here is responsible if you break, brick, set fire, punch, smash, stab, destroy, your self, computer or your phone. The only person responsible is you! Just because it worked for me and others does not mean it will for you. Anytime you flash something its a risk.
Ladies and gentlemen... I've traveled over half our forum to be here tonight. I couldn't get away sooner because I had a POST coming in and I had to see about it. That phone is now rooted at and running well. I have two others comming in and this method has rooted many on the board. So, ladies and gentlemen... if I say my guide works you will agree. You have a great chance here, but bear in mind, you can lose it all if you're not careful.
Out of all methods that beg for a chance to root your phone, maybe one in twenty will work; the rest will be trolls-that's posters trying to get between you and the guide-to get some of the root action that ought by rights come to you. Even if you find one that has a simpler guide, and means to root, he'll maybe know nothing about helping. This is... the way that this works. This method is reliable like no other in this field and that's because its been tested and tested time and time again. I assure you, whatever the others promise to do, when it comes to the showdown, they won't be there...
Downloads
================================================== ====
STOP HERE READ THIS
This Method soley uses Amon_RA Recoveries....Period. A poor soul that lost his RSA keys (broken 4g forever) by recent clock work shenanaigans here
VX - Updated Amon Ra Recovery. Download Here: hboot_2.xx_soff-VX.zip
MD5: 27eb4a36ba01078193975fc93723dd60 <---VERIFY YOUR MD5, IF ITS NOT THIS REDOWNLOAD
Lets Get Rooted!
================================================== ====
Prerequsites:
Extract only the main zip file to a folder of your choice. I recommend the root of C:\ into a folder of your choice or on the desktop. Make sure you have the drivers installed for your phone (recommended: SDK Drivers or unrevoked hboot drivers) and USB debugging is on. This was setup for people running windows, if you have access to it do it on a 32bit version. I can't stress this enough you must use the adb.exe included with the package This is command line based do NOT double click the exe. Assume nothing, and cut and paste or type the commands EXACTLY as listed, they are case sensitive and each line is a seperate command. Oh and Read the FAQ and Warnings for f-sakes
1) Connect your phone to the computer (Rear USB Port Perferred) make sure the computer detects the phone (DO NOT MOUNT USB) If it doesnt install the drivers. Now master Reset your Phone (Menu>settings>Sd & Phone Storage>Factory Data Reset). Your phone will reboot. While your phone is rebooting it ctrl+alt+delete on your computer and open up task manager and click the processes tab look for anything that says adb.exe click it and hit end process.
2) Your phone should be booted and in the rom. You can skip the setup. On your phone enable install applications from unknown sources.(menu>settings>applications>unknown sources) and turn on usb debugging.
3) Open a command prompt (do NOT click adb.exe) and change to where ever you extracted the files to.
4)Type the following (this must be excuted from the folder you extracted to)
adb push root/unrevoked-forever.zip /sdcard/
adb push root/mtd-eng.img /sdcard/
adb push pc36img/PC36IMG-ENG.zip /sdcard/PC36IMG.zip
adb push pc36img/PC36IMG-MR.zip /sdcard/PC36IMG-MR.zip
adb push root/flash_image /data/local/
5) Now were gonna install z4root. When its done look at your phone z4root should be running. Select temporary root... It will go thru the process will eventually come to a white screen *Wait* after a sec or so screen will come up saying temp root was a success. Ok so now type the following
adb -d install -r root/z4root.apk
adb shell am start -a android.intent.action.MAIN -n com.z4mod.z4root/com.z4mod.z4root.z4root
6) Your command should still be open and you should be in the directory where you extracted the files. Once you have typed "su" command below look at your phone and click allow for SuperUser...Ok so now type the following from the command prompt
adb shell
su
6A) REQUIRED RSA BACKUP This will back up your RSA keys just in case something goes wrong in that department. You should still be in your command window inside the shell with a #. (The following came from this thread)
mkdir -p /sdcard/nandroid/RSA-PR-BACKUP
cat /dev/mtd/mtd0 > /sdcard/nandroid/RSA-PR-BACKUP/wimax.img
This saves it in a file that can actually be restored. This next step is another type of backup just for good measure
busybox sed -n '/BEGIN CERTIFICATE/,$p' /dev/mtd/mtd0 > /sdcard/rsa_OEM.key
This will dump the RSA keys to a text file on your SD Card named rsa_OEM.key
Mine was about 4575 KB in size, but the size could vary. Go ahead and switch the phone's USB connection over to "Disk Drive" and then browse to your SD Card and verify that the file rsa_OEM.key is indeed on the card.
Proceed to Step 7
7) You Should still be at a "#". This means you have root if you see a "$" or some other error message. Reboot your phone, check your drivers, usb debugging and cable and start over. If you got a "#" You can Proceed. You should still be in the shell at a "#" If not start over...Otherwise
chmod 0755 /data/local/flash_image
./data/local/flash_image misc /sdcard/mtd-eng.img
sync
8) Now we are going to reboot your phone into the boot loader to flash the first PC36IMG.zip. You should still be in the shell So Type:
reboot bootloader
9) Once your phone is in the boot loader highlight bootloader, and press the power button. It will load the PC36IMG File...When it ask you to flash press VOL-UP. You will notice that it says bootloader bypassed and maybe some other errors. Dont worry this is normal. Once the flash of the file is done it will ask to reboot, Select NO by Pressing VOL-DOWN. Now some people have gotten some errors here and there during the flashing just continue as normal.
10) You should still be in the boot loader at this point. Scroll down to recovery and press the power button. It Should take you to a red triangle. If not and you get stuck at a white htc screen pull the battery and then repower the phone with power + vol down and select recovery. When you see the red triangle. Type the following (IF YOU GET STUCK HERE CHECK THE FAQ):
adb push recovery /
adb shell busybox --install /sbin
adb shell nohup /sbin/recovery &
With any luck you should be at a recovery (green screen with text)
11) Select enable USB-MS. This will mount your sdcard. Look in the root of your sdcard and you should have two files. One named PC36IMG.zip and one named PC36IMG-MR.zip. Rename the file named PC36IMG.zip to PC36IMG-ENG.zip and then rename PC36IMG-MR.zip to PC36IMG.zip when your done follow the instructions on your phone to disable usb (press power) then proceed to step 12
12) Now Select flash zip from the menu and choose unrevoked-forever.zip. Wait for it to complete. Select Reboot from the menu.
Now pay attention. It might kick you back into:
BOOT LOADER: See 12A
ROM: See 12B
WHITE HTC SCREEN: See 12C
12A) Ok so you got kicked to the boot loader. It should scan your card and find the PC36IMG.zip chose yes to flash this file and when it ask you to reboot....reboot by pressing vol-up....Proceed to step 13
12B) Ok so the phone booted into a rom. Power the phone off. Then repower the phone on pressing power and vol-down at the same time. It should take you into the bootloader and scan your card and find the PC36IMG.zip chose yes to flash this file and when it ask you to reboot....reboot by pressing vol-up....Proceed to step 13
12C) Ok so the phone is stuck at a white htc screen. Power the phone off by pulling the battery. Then repower the phone on pressing power and vol-down at the same time. It should take you into the bootloader and scan your card and find the PC36IMG.zip chose yes to flash this file and when it ask you to reboot....reboot by pressing vol-up....Proceed to step 13
13) Ok your phone is rooted now, and you should be inside the rom. The rom you just flashed is Sprint Lovers rom with the modified recovery. Download a rom of your choice copy it to the root of your sd card and flash it. But type the following first
adb shell mv /sdcard/PC36IMG.zip /sdcard/PC36IMG-MR.zip
adb reboot recovery
14) You Should be in the recovery menu now (green text screen). Do a backup by navigating to backup/restore press power to select then do a Nand backup in the next menu. Once thats done, select return, then reboot or flash a rom of your choice. If you flashed a different custom rom than the one thats included in the package cool. If not no big deal eitherway. Do a PRL/Profile update while in the rom after the phone is done rebooting. Your Done.
15) Read the FAQ for questions
jk jk
You are joking about it being kept quite right? with how many people like to be the HERO and post anything and everything first? trust me once root people wish rush to post IM THE FIRST TO HAVE IT ROOTED HERE IS PROOF.
TRUST ME THE HERO EFFECT NEVER FAILS.
root
toast has said we are good .....we have eng hboot and he did root the og evo ...... if he said anything htc could patch the exploit with ota ..... we will have root s-off really soon
...............

Cant save my Prime

Flashed the Broccoli nightly rom I can no longer boot or get back into CWM. Computer cannot start the device. Can someone please help me? Tried all the tools and methods. It won't work unless I can get the device to start when connected to my computer.
RIght now when I press Vol Up and power, it brings me to cold boot linux. Cannot select anything or do anything. When connected to comp, it says device cannot start Code 10. Don't know what else to do. Help please
Looks like you're having an issue similar to mine. You'll need to setup ADB and push another rom to your Prime.
Can you get into recovery?
Sent from my WabiSabiGeek'd out Transformer Prime using the Interweb
This thing is completely frozen no matter what. I can power off and on but that's about it. The device won't start according to windows. I'm praying I won't have to RMA or something.
You shouldn't be getting that screen pressing vol up and power.....that should be vol down and power, then doing nothing.
Sent from my WabiSabiGeek'd out Transformer Prime using the Interweb
Thats pretty strange. You kinda screwed unless you can get into recovery or fastboot
Sent from my WabiSabiGeek'd out Transformer Prime using the Interweb
Hi,
where it says press down to change mode you should be able to highlight the middle icon. If so that is fastboot and you have a chance.
I had a very bricked Prime and it only got that far. Then I followed this post.
You must download the fastboot and adb from the links given. I had some from elsewhere and they didn't work so well.
Also, I am not an Android hacker and I think that the dd command is somehow dangerous. At the end of the day, on my machine, I'm back with AndroWook and latest Motley kernel
Best of luck.
Tritium
Thanks let me try now. I hope it works. How did you get the computer to recognize the prime? Do I need to enable asus sync?
Tritium3.016 said:
Hi,
where it says press down to change mode you should be able to highlight the middle icon. If so that is fastboot and you have a chance.
I had a very bricked Prime and it only got that far. Then I followed this post.
You must download the fastboot and adb from the links given. I had some from elsewhere and they didn't work so well.
Also, I am not an Android hacker and I think that the dd command is somehow dangerous. At the end of the day, on my machine, I'm back with AndroWook and latest Motley kernel
Best of luck.
Tritium
Click to expand...
Click to collapse
It's alive!!! Thanks for the help. :good:
wao i have the same problem but i only go on CWM and not fastboot and still cant get it on fastboot and its not reconized the drivers any ideas??
klutch said:
wao i have the same problem but i only go on CWM and not fastboot and still cant get it on fastboot and its not reconized the drivers any ideas??
Click to expand...
Click to collapse
So when your device turns on its in a recovery loop right? You try to reboot and it goes right back to recovery?
It's ok don't worry, we will get it fixed. If that's what your problem is its referred to brick 1a in the unbrick your prime sticky thread.
We just need to setup ADB if you haven't already, and run one command. PM me if you need some help and ill try my best to get you through it or remotely connect to your computer to help you.
I highly suggest TWRP recovery after you get rebooted.
Sent from my ADR6425LVW using xda premium
klutch said:
wao i have the same problem but i only go on CWM and not fastboot and still cant get it on fastboot and its not reconized the drivers any ideas??
Click to expand...
Click to collapse
This is what I did while in CWM. Below is a copy of an insert from this thread.
http://forum.xda-developers.com/showthread.php?p=24923189#post24923189
Anyhow, so after you have that version installed:
1. Download "ROOTED 9.4.2.21 CWM compatible signed US version"
d - h . s t / r 4 4 -> WITH NO SPACE! (This is from the Primeval: The STOCK stock rom) Thread.
2. EXTRACT IT to the same directory where your ADB is! We only need the BLOBFILE from that zip folder!
3. Once you have the files extracted just run the following on your Command line:
adb push blobfile /sdcard/ ---> Its going to look like its not doing
nothing but dont worry its doing it in the background after 401 or some
seconds the command line will returned to you with a message like this:
1275kb, dadadada...
4. VERY IMPORTANT!: enter:
adb shell
dd if=/sdcard/blobfile of=/dev/block/mmcblk0p4
(Same as the previews step it will take forever but it will work dude!)
5. DONE! at least this is what worked for me man!
Im so happy now my Asus is freaking Brand NEw again! i was JUST about to through this garbage away but im so happy "dklue" gave me the BLOB concept idea! heheheh i guess i learned something new now..
the thing is the computer is not picking it up i tried diffrent drivers and still nothing i try doing ADB Shell device not found in order to do some commands i have to have it mount and thats the problem what ever i do wont move nothing so basicly is still on CWM only reboot and back again to CWM
Hold power and vol down to boot into CWM. Then you can do the blobfile push. It worked for me

Question with this Downgrading procedure: [Procedure]No HTC unlock HC-GB downgrade fo

Hello all,
I have been trying to downgrade my Flyer (wi-fi Best Buy version) by using the procedure provided by our awesome helper and mentor, globatron. The procedure is titled as [Procedure]No HTC unlock HC-GB downgrade for official HC OTA and found at http://forum.xda-developers.com/showthread.php?t=1428104.
I have gone through all 13 pages on that thread to find out if anyone has a problem I am having. But it appears no one had the same problem. As a new user, I was not allowed to post a question on that particular thread. So here I am....
Here is the procedure/instruction from the posting I mentioned above.
Procedure
1. Check the version number for your gingerbread RUU
In my example I am using this RUU: RUU_Flyer_HTC_WWE_2.00.405.3_R_Radio_20.3501.30.08 9BU_3809.05.04.10_M_release_194964_signed.exe
The version is the part highlighted in red.
2. Boot your flyer up to android if it's not already on, with usb debugging enabled and connect it to the PC.
3. Run the following adb commands
adb push tacoroot.bin /data/local/
adb push misc_version /data/local/
adb shell chmod 755 /data/local/tacoroot.bin
adb shell chmod 755 /data/local/misc_version
adb shell /data/local/tacoroot.bin --setup
At this point your device will reboot to recovery
4. Simultaneously press Volume Up, Volume Down and Power
5. Reboot your device
6. Run the following command
adb shell /data/local/tacoroot.bin --root
* Your device will reboot, do not worry if it does not boot fully, it doesn't matter for this procedure, and it is a side effect of this root exploit.
7. Run the following command:
adb shell /data/local/misc_version -s 2.00.405.3
* Note that the number in RED is the version number retrieved in step 1.
8. Reboot to fastboot:
adb reboot bootloader
I could not move forward after 8, I will not post the steps from 9 to 11.
Here we go.... I have two troubles.
First, I am not sure of the timing of "pressing Volume Up, Volume, Down, and Power." Is it something I should do manually? If so, when should I do it. It seems like the Flyer automatically re-boots itself into "Recovery" without me forcing it.
As it is going into the "Recovery," there were two images popped up in a row. The first one looks like a SD disc, which moved quickly moved to the next image. The second image is a tablet with a red triangle, which has a exclamation sign in it.
THEN the procedure STOPS at the second image.
That is my first question. Does anyone have any idea of what's possibly going on?
My second starts here as well.
After not moving on, I decided to manually reboot the Flyer so I can move on to the Step 7.
Somehow I can pass the Step 7. But at Step 8, I got the message saying "Error: Device not found." So I tried "fastboot getvar cid" to see if the tablet is really not connected. But weirdly, the "fastboot getvar cid" worked. But I still get the same error message (device not found) whenever I run the code at step 8.
This is it. There are my two questions.
As I went through all 13 pages, many people were able to go through the procedure without any problem. Having those problem and taking considerable amount time to figure our what's going on and still not successful make me feel pretty stupid and extremely frustrated. Please someone put me out of this horrible misery.
I love my Flyer. But I am starting to understand why many of my friends paid a lot more $$$ to get their iPad.
Not sure what went wrong, but you could try doing step 8 manually. Hold volume down and power for roughly 10 seconds, you should get into the H-boot screen. Press the power button once on Fastboot ( its the first option) use the volume keys to navigate to "reboot bootlader" use power key to select it.
Thanks, but didn't work.
Havoc-X said:
Not sure what went wrong, but you could try doing step 8 manually. Hold volume down and power for roughly 10 seconds, you should get into the H-boot screen. Press the power button once on Fastboot ( its the first option) use the volume keys to navigate to "reboot bootlader" use power key to select it.
Click to expand...
Click to collapse
I tried it. But, I am still having that "error: device not found" message.
Thanks for your advice though. I clicked "Thanks."
still getting the same image
Havoc-X said:
Not sure what went wrong, but you could try doing step 8 manually. Hold volume down and power for roughly 10 seconds, you should get into the H-boot screen. Press the power button once on Fastboot ( its the first option) use the volume keys to navigate to "reboot bootlader" use power key to select it.
Click to expand...
Click to collapse
Somehow the thread doesn't allow me to edit my own reply.
Anyway, I still end up with the tablet image with the red triangle, which has a exclamation sign (!) in it. I was afraid of bricking my Flyer and stopped trying anything further.
Try with DEBUG turned OFF althow stated ON. Worked for me like that when i was runing revolutionary. I coudnt make it work then just out of curiositiy i switched and it worked.
jprednik said:
Try with DEBUG turned OFF althow stated ON. Worked for me like that when i was runing revolutionary. I coudnt make it work then just out of curiositiy i switched and it worked.
Click to expand...
Click to collapse
Thanks for the advice. I'll give it a shot and keep you posted. Thanks again.
jprednik said:
Try with DEBUG turned OFF althow stated ON. Worked for me like that when i was runing revolutionary. I coudnt make it work then just out of curiositiy i switched and it worked.
Click to expand...
Click to collapse
It didn't work for me.
I cannot get the access to the tablet. THANK YOU for your advice though!! Have a great day!!!

Restoring Rooted TF201

Hello. This is my 2nd post after here. I hope this will not bother anybody.
I have a situation. I did root my TF201 using CWM and virtuous_prime_s_9.4.2.21_v1 a month ago. Just now, I plan to sell my TF201. So, I go to the tablet setting and click at the reset data or something like that. I think it's just a normal data deletion process which is not effecting the rooted system. Unfortunately, after I reset / delete the data, the tablet is not going to boot. It just keep showing the CWM Recovery page with options to reboot the system, install zip from sdcard, wipe data, and so on. I selects to reboot the system, but nothing is happening. The tablet is turned off and turned back on with same display (CWM Recovery page).
What should i do?
titanbullet said:
Hello. This is my 2nd post after here. I hope this will not bother anybody.
I have a situation. I did root my TF201 using CWM and virtuous_prime_s_9.4.2.21_v1 a month ago. Just now, I plan to sell my TF201. So, I go to the tablet setting and click at the reset data or something like that. I think it's just a normal data deletion process which is not effecting the rooted system. Unfortunately, after I reset / delete the data, the tablet is not going to boot. It just keep showing the CWM Recovery page with options to reboot the system, install zip from sdcard, wipe data, and so on. I selects to reboot the system, but nothing is happening. The tablet is turned off and turned back on with same display (CWM Recovery page).
What should i do?
Click to expand...
Click to collapse
If you still have the virtuous prime file on there just.go to install zip and select it then reflash and youl be good to go. If not then you need to search on here for a program called knives and forks which is the easy way to install adb android debug bridge once installed download virtuous prime zip and place it in the same Rwhere you just installed adb then make sure you are in the cmw main screen and type adb push (filename) this will send the to tablet it may take up to 10 minutes and will just show a flashing cursor . Then flash.as normal. Sorry for spelling mistakes typing.g this on my phone and its being stupid
Uberjim said:
If you still have the virtuous prime file on there just.go to install zip and select it then reflash and youl be good to go. If not then you need to search on here for a program called knives and forks which is the easy way to install adb android debug bridge once installed download virtuous prime zip and place it in the same Rwhere you just installed adb then make sure you are in the cmw main screen and type adb push (filename) this will send the to tablet it may take up to 10 minutes and will just show a flashing cursor . Then flash.as normal. Sorry for spelling mistakes typing.g this on my phone and its being stupid
Click to expand...
Click to collapse
Thanks for the reply. I appreciate the info given. Will try to use the tool now since the rom file is no longer saved in the tablet.
Will update soon.
Thanks.
I'm just done installing the Knivesandforks on my win7. After that, the system automatically install the phyton. I dont know what its function, but as i follow this steps, i get error with cmd which shown as below:
Code:
c:\users\pc>adb reboot
error: device not found
i think i didn't miss any steps. Anybody here could help me with this?
Thanks in advance.
* my tablet is still in cmw main page and not showing anything even has been connected to the PC. i think that's the reason why the error occurs - device not found. anybody who could give some ideas on this will much appreciated.
You may need the fast boot drivers I wasn't sure if you would with being in cmw download those and extract them to the same folder as adb then load it up by using shift right mouse click run command and type and type adb devices if it shows up your good to go try the above steps again
titanbullet said:
Hello. This is my 2nd post after here. I hope this will not bother anybody.
I have a situation. I did root my TF201 using CWM and virtuous_prime_s_9.4.2.21_v1 a month ago. Just now, I plan to sell my TF201. So, I go to the tablet setting and click at the reset data or something like that. I think it's just a normal data deletion process which is not effecting the rooted system. Unfortunately, after I reset / delete the data, the tablet is not going to boot. It just keep showing the CWM Recovery page with options to reboot the system, install zip from sdcard, wipe data, and so on. I selects to reboot the system, but nothing is happening. The tablet is turned off and turned back on with same display (CWM Recovery page).
What should i do?
Click to expand...
Click to collapse
Recovery bootloop, see here, option 1a: http://forum.xda-developers.com/showthread.php?t=1514088
Use only Universal Naked Drivers (see related thread).
Sometimes even with proper drivers adb is a mess, then uninstall adb and search the net for a ready to use adb, there are some easy to find.
Uberjim said:
You may need the fast boot drivers I wasn't sure if you would with being in cmw download those and extract them to the same folder as adb then load it up by using shift right mouse click run command and type and type adb devices if it shows up your good to go try the above steps again
Click to expand...
Click to collapse
i did those steps again, but it seems like not helping. the script is only rebooting the tablet instead of giving me the option to flash the rom. i don't know if i did wrong. but as i know, i did as posted here.
* frust to see the cmw recovery for the whole day
Striatum_bdr said:
Recovery bootloop, see here, option 1a: http://forum.xda-developers.com/showthread.php?t=1514088
Use only Universal Naked Drivers (see related thread).
Sometimes even with proper drivers adb is a mess, then uninstall adb and search the net for a ready to use adb, there are some easy to find.
Click to expand...
Click to collapse
i did follow this tutorial
at first, install universal naked drivers - done
Now do the following:
Make sure your Prime is in Recovery mode (CWM) - YES
Open a cmd line on your pc - DONE
Type: "adb shell" - DONE
You should see a "#" now - YES
Once you have that "#", please type: dd if=/dev/zero of=/dev/block/mmcblk0p4 bs=100 count=1 and press [Enter] - Ok. This part was very difficult. I see the "#" but to type all those command, I can't. Why? Because the line in cmd instantly extended to a new line of command. I mean it just like I press the ENTER button. So, the line move to below and i can't finish typing all those command.
Now type: dd if=/dev/zero of=/dev/block/mmcblk0p3 bs=16 count=1 and press [Enter]
Exit the shell and reboot your Prime via CWM
It should not reboot to CWM automatically now. It either boots your ROM or is stuck at the splash screen. If it is stuck, boot to recovery and install any ROM you want.
Click to expand...
Click to collapse
titanbullet said:
i did follow this tutorial
at first, install universal naked drivers - done
Click to expand...
Click to collapse
Very strange, try to expand your command line window first. It doesn't matter if the text goes on following line, as long as you don't press Enter it's considerd as the same line. Try copy/paste instead ot typing.
Striatum_bdr said:
Very strange, try to expand your command line window first. It doesn't matter if the text goes on following line, as long as you don't press Enter it's considerd as the same line. Try copy/paste instead ot typing.
Click to expand...
Click to collapse
this is my first time, so i don't know if that was strange. ha ha. well, it's not about the command line which is extended or not. but the line itself creating a new line, as i said - just like i press the ENTER button.
i try to use copy-paste function (ctrl + c and ctrl + v). but i don't think it functions in cmd.
please help..
[Solved]
What i do?
I follow this step again
Installing the ADB again
And the most important thing is, pushing ROM into /sdcard should be like this:
Code:
adb push rom.zip /sdcard/rom.zip
And right-click copy paste function solving my strange cmd
Then i just follow the steps by installing the zipped rom thru cwm when my screen did not stuck at splash screens
Thanks for your kindness
My TF is now back to normal
THANKS!

Categories

Resources