HTC Magic - Help required, stuck on splash screen. - myTouch 3G, Magic General

Hi guys, here is the situation:
A friend of mine brought his HTC Magic for me to look at last night. The phone starts but sticks on the 'HTC Magic' screen (I think this is called the splash screen?).
It boots into safe mode when I hold Home and Power, however it says this on the bottom of the safe mode screen: E:Can't open /cache/recovery/command
I tried a factory reset from this screen but that didn't help.
However, on the safe mode screen there is an option to apply update from SD Card, which brings me to my questions:
1) Firstly, I'm not a complete beginner when it comes to dealing with this kind of stuff, I have successfully rooted my MyTouch 3G and installed CaNNoNs complete eclair, so I was wondering, with regards to this phone, can I just get a copy of the original ROM and flash it using the update from SD?
2) Also is there anyway to know if the phone is already rooted, besides the fact that the standard recovery screen came up? (which would mean it isn't, right?)
3) If the flash from SD card would work, where do I get the ROM from? There is the word 'TIM' and a weird 3 squiggly line symbol when you first turn on the phone. I think this means its originally from an Italian provider. If so where would I get that ROM.
Thanks in advance for your help. This community has been a great source of information and experience in my life. I thank you all.
Oh yeah I forgot to tell you guys, I CAN get into fastboot, just don't know what to do after that.

Procedure
1.Turn your phone off. Turn it on by holding Back and Power, or Vol. down and Power. Either way, boot into the bootloader.
You should see the three Androids on skateboards, and the menu title should say "Fastboot".
2.Connect your device to the computer. The display on your phone should now say "Fastboot USB".
3.Open up the shell/terminal on your computer, and type
fastboot devices [enter]Your device should be listed with it's serial number, and should say "fastboot".
4.Change directory to where you have saved your recovery image. I.e. type "cd /path/to/recovery.img in windows prompt, press enter.
5.You may issue a "dir" command (Windows) or "ls" (Unix/Linux) to make sure you are at the right directory, or just skip this step.
6.Type
fastboot flash recovery recovery.img
Check your phone's display, as recovery is being sent and flashed to your device.
Check your command prompt/shell to make sure the process is over.

Hey, sorry for the late reply, plenty happing at home now. You said flash with the recovery image that I have saved. Do you mean the original recovery image...or....do you mean I can put on a custom one such as Amon Ra or Cyanogen?

sike89 said:
3.Open up the shell/terminal on your computer, and type
fastboot devices [enter]Your device should be listed with it's serial number, and should say "fastboot".
Click to expand...
Click to collapse
^^This doesnt happen^^
Any ideas?

Download FastbootCommanderV.1.5

Related

Unbricking mytouch/g1 ( soft bricks only but no harm trying )

I found a site with someone who bricked their phone but found a loop hole. I have never bricked my phone and hoping i never will but for those who have bricked their phone here are some steps to try to unbrick it! HOPE IT HELPS! SEND FEED BACK!!
So you can’t access bootloader or recovery and the only thing that works is the blue led trick when pressing trackball + power button??
Try the procedure below.
Step 1: Turned Phone off by taking out the battery.
Step 2: Prepared SD card
Put SD card in card reader and formatted it as FAT32, copied the DREAIMG.nbh onto it.
Or try Sapphimg.nbh
Step 3: Put SD card back in phone
Step 4: Hold Vol down + Power + track ball together and put battery to start phone
Step 5: Run update
IF THAT DIDNT WORK!
TRY THIS!
Step 1: Turning Off Your Phone
Because you have a bricked phone, you can't just hold the power button. So if your phone is not already off then you're going to want to take out the battery.
Step 2: Preparing Our SD card
Take out your SD card and put it into an SD card reader or some type of other adapter so that we can view it from our computer. If you cannot view the SD card on your computer then you're going to need a new SD card.
Download DREAIMG-RC29.zip and unzip the file.
Reformat the SD card to FAT32 and copy the DREAIMG.nbh onto it.
Safely eject the SD card.
Put the SD card into your device.
Step 3: Wipe The Phone
Hold home and press the power button.
When you see the image of an ! mark, open your keyboard and press Alt + L if you cannot see any command options.
Do a factory reset by pressing Alt + W or just using the trackball.
When the reset is done, go ahead and hold the camera button and select the reboot system now option with your trackball.
Step 4: Flashing The Phone
Once the grey screen pops up (or the white screen if your phone was rooted with JesusFreke) it will ask you to hit a button to start installing the image…press that button. DO NOT DO ANYTHING TO STOP THIS PROCCESS. It will take about 8-12 minutes.
When the image has completed the installation (it will say completed), go ahead and press the green, red, and menu buttons at the same time. The phone will reboot.
And your done! Your phone is now unbricked!.
The G1 screen will hang there for a good minute or two, but be paticiant, it will boot. Now you have a choice. Try to hack your phone again, because you're in the correct state to have another go, or, you can stick with the official Android. Now if you choose to stick with the official Android, here's what you do.
Step 1: Upgrading to Android 1.0 RC33
Download the file signed-PLAT-RC33-from-RC30.zip
Rename the file to update.zip and copy it to your SD card
Reboot your phone into recovery mode. Power off the phone first and then hold down the Home key while powering it back on.
The recovery mode is finished loading when you see the ! mark inside the triangle. Press Alt + L to display the list of options.
Press Alt + S to flash the file update.zip.
Wait for the update to apply. Your phone may reboot during this process so be patient.
Press Home + Back if prompted to reboot your phone.
Step 2: Upgrading to Android 1.5 CRB43
Download the file signed-kila-ota-148830.de6a94ca.zip
Repeat the steps from above to flash the update file.
Step 3: Upgrade to Android 1.5 CRC1
Download the file signed-kila-CRC1-from-CRB43-FIX.7ca4a1d7.zip
Repeat the steps from above to flash the update file.
Step 4: Upgrade to Android 1.6 DRC83
Download the file signed-kila-DRC83-from-CRC1.c41b93c1.zip
Repeat the steps from above to flash the update file.
PM FOR THE DIRECT WEBSITES!
sad cause this will get locked soon.
domuhhnic said:
sad cause this will get locked soon.
Click to expand...
Click to collapse
why? all we need is someone who can confirm this is true on xda and it will be stickied EVERYWHERE
LOCKED?
domuhhnic said:
sad cause this will get locked soon.
Click to expand...
Click to collapse
Why will this get locked??
Yuppie
oshizzle1991 said:
why? all we need is someone who can confirm this is true on xda and it will be stickied EVERYWHERE
Click to expand...
Click to collapse
Exactly .. but i dont know anyone with a bricked phone so i cant ask them if it works.. if it gets locked (whatever that means) i'll repost it!
id be interested to see if this works... although its assuming you have a dream/g1 .. did you post this in the g1 section?
POST?
digitaljeff said:
id be interested to see if this works... although its assuming you have a dream/g1 .. did you post this in the g1 section?
Click to expand...
Click to collapse
Yes, I have a HTC MAJIC/MYTOUCH .. nope i have not posted it there but i will now
i tried to update radio and now :
So you can’t access bootloader or recovery and the only thing that works is the blue led trick when pressing trackball + power button??
Try all of this methods , but no result..
phone just shows htc magic when i turn it on usually, and nothing!
what can i do?
...
Im still looking of ways to unbrick phones
Possible hint!
Has anyone tried using adb .. Reflashing the recovery img??
...another hint..
kemimarie said:
Has anyone tried using adb .. Reflashing the recovery img??
Click to expand...
Click to collapse
run fastboot boot recovery-image.img or whatever you named your recovery image. It'll display "waiting for device..." message just keep pluging it in, unplugging, popping the battery and eventually your device will respond and boot into recovery.
Someone bricked and i did it... twice trying to flash the eng 2010 SPL. It worked the third time and my device is up and running again with an engineering SPL.
if your device is stuck on the first splash but displays in red "Fastboot USB" message in the upper left corner of the screen, DO NOT power it down. run the above mentioned command and reflash.
deleted... double post.
Found another hint
ch3w said:
confirmed...
-I Connected USB.
-I inserted the battery.
-I booted the phone while holding the HOME key.
-The phone still froze at the first splash screen, but then suddenly, the waiting fastboot command detected the phone and booted the recovery image!
Click to expand...
Click to collapse
try that on your g1/mytouch!
kemimarie said:
try that on your g1/mytouch!
Click to expand...
Click to collapse
this method worked on my second bricked magic, still trying it on the first one but... no luck yet. i had the same problem with both of them tho
kemimarie said:
run fastboot boot recovery-image.img or whatever you named your recovery image. It'll display "waiting for device..." message just keep pluging it in, unplugging, popping the battery and eventually your device will respond and boot into recovery.
Someone bricked and i did it... twice trying to flash the eng 2010 SPL. It worked the third time and my device is up and running again with an engineering SPL.
if your device is stuck on the first splash but displays in red "Fastboot USB" message in the upper left corner of the screen, DO NOT power it down. run the above mentioned command and reflash.
Click to expand...
Click to collapse
fastboot boot recovery?
boot.img and recovery.img are two totally different things.
The recovery (amon_ra is preferred)
The boot.img is where the kernel, ramdisk, etc resides.
you must've meant fastboot flash boot boot.img
or
fastboot flash recovery recovery.img
but not both.
ch3w said:
this method worked on my second bricked magic, still trying it on the first one but... no luck yet. i had the same problem with both of them tho
Click to expand...
Click to collapse
YAAYY!! Im glad to hear you say you had some success!
Binary100100 said:
fastboot boot recovery?
boot.img and recovery.img are two totally different things.
The recovery (amon_ra is preferred)
The boot.img is where the kernel, ramdisk, etc resides.
you must've meant fastboot flash boot boot.img
or
fastboot flash recovery recovery.img
but not both.
Click to expand...
Click to collapse
I just copied and pasted from a website.. THEY did that and it worked for them lol
bricked Mytouch3g
Bricked mytouch3g -- brandnew phone. Just tried to flash cyanogen test3 and everything went fine but then I rebooted and all I have is vodafone boot screen, nothing else works but the blue led which will not load any img. adp doesn't work it never detects a phone no matter what you do. It was the first flash too. Crazy how HTC didn't make a built in hard reset like you have on windows mobile phones. You wonder if they want people to crash there phones so they have to replace them ect etc.
Hello.
My phone has the same problem.
Anything that is needed done. But no no avail.
My phone is brick.
Help help help
Mod edit: not dev related, moved to general

stupid reason to take back evo to get an epic?

cause the newest evo's arent rootable? lol i just got my evo yesterday and ive searched everywhere that the newest hboot 2.02 and 3.30 cant get rooted? the evo is pretty good but im all customizations. i read that the epic is super easy to root.
It can be rooted you just have to work harder at it. Dont take it back you'll regret it.
Clearly you haven't done any searching in the Android Development section.
But that's OK. Go ahead and get an Epic. Enjoy your screwed-up GPS and all that, and make sure to change your password on here to something you won't remember, so we never have to see you again.
mainguy21 said:
cause the newest evo's arent rootable? lol i just got my evo yesterday and ive searched everywhere that the newest hboot 2.02 and 3.30 cant get rooted? the evo is pretty good but im all customizations. i read that the epic is super easy to root.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=829045
there you go. Just follow the directions and make sure you use the correct file locations.
real problem
What he really meant to say is . I am 16 and have Attention deficit hyperactivity disorder and cant bother myself to use the search button above me nor can i follow simple written instructions on rooting phone . If it dont have one click root i wont do it ........ i have both phones and the devs on evo are much better
thats funny i just typed in the search bar root evo hboot 2.02 and the first thread was the guide on how to do it.
@op if you are going to lie about searching the forum do it somewhere else. we know when a search isnt performed.
mainguy21 said:
and ive searched everywhere
Click to expand...
Click to collapse
Sure you have, buddy... sure you have.
ohhhhhhhhhhhhhh
You have been misinformed due to stupid people making stupid and false posts such as this one:
http://forum.xda-developers.com/showpost.php?p=9578042&postcount=8
Kingmac38 said:
What he really meant to say is . I am 16 and have Attention deficit hyperactivity disorder and cant bother myself to use the search button above me nor can i follow simple written instructions on rooting phone . If it dont have one click root i wont do it ........ i have both phones and the devs on evo are much better
Click to expand...
Click to collapse
Sent from my PC36100 using XDA App
I am 20 and have ADHD and search is my best friend plus I've followed many rooting guides successfully so op has no excuse
Second that my girls epic is a pain in the ass and she kinda of.wish she got my phonr instead
Sent from my PC36100 using XDA App
thanks for help even though i searched everywhere.
but since i cant root my phone im stuck in the middle of it with a red triangle can i atleast go back to my phone? like unroot or something even though i didnt get all the way to root? please thanks
Follow these revised instructions from illogos pg 121 of hboot 2.02 root guide and everything should work. I've already rooted two hboot 2.02 hw 004 and in process of doing another one now. Everything works just fine if you understand and follow the instructions. Anyways, this was a lot simpler than the old school toast part 1 and 2 root methods so acquire some knowledge so you can someday help others and not be such a newbie.
thats what i followed and im still stuck at steps 10-11..my phone says in bootloader its "s-off" but i cant get that file to read after rebooting. ive tried over and over from the start and nada i even downloaded the file like 5 times.
mainguy21 said:
thats what i followed and im still stuck at steps 10-11..my phone says in bootloader its "s-off" but i cant get that file to read after rebooting. ive tried over and over from the start and nada i even downloaded the file like 5 times.
Click to expand...
Click to collapse
Which instructions though? Please follow these ones by illogos-
illogos said:
1. Make sure that you downloaded and installed HTC Sync from HTC website.
2. Unzip hboot202-s_off-V8.zip to a folder in your C: drive. I used C:\hroot
3. This hroot folder should have a folder inside it called root. If you have a folder called hboot202-s_off-V8 then you need to move all the files from that subfolder to c:\hroot.
4. In Vista/7 slick on the start button and type in cmd. You will see in the program list the command prompt. Right click and open as Administrator.
5. In the command prompt type cd c:\hroot
6. On phone goto-> Setting>Applications>Debugging make sure usb debugging is on.
7. Connect the usb cable to your computer and phone. The phone should change it's screen to ask you what type of connection mode you want. Make sure that it is on charge only. Do not mount.
8. Type into the command prompt: adb push root/unrevoked-forever.zip /sdcard/ After a pause you should see a confirmation message that states the file size and transfer speed when the file is done being pushed.
9. Type into the command prompt: adb push root/mtd-eng.img /sdcard/ After a pause you should see a confirmation message that states the file size and transfer speed when the file is done being pushed.
10. Type into the command prompt: adb push pc36img/PC36IMG-ENG.zip /sdcard/PC36IMG.zip After a pause you should see a confirmation message that states the file size and transfer speed when the file is done being pushed.
11. Type into the command prompt: adb push pc36img/PC36IMG-MR.zip /sdcard/PC36IMG-MR.zip After a pause you should see a confirmation message that states the file size and transfer speed when the file is done being pushed.
12. Type into the command prompt: adb push root/flash_image /data/local/ After a pause you should see a confirmation message that states the file size and transfer speed when the file is done being pushed.
13. Type into the command prompt: adb push root/rageagainstthecage /data/local/tmp After a pause you should see a confirmation message that states the file size and transfer speed when the file is done being pushed.
14. Type into the command prompt:adb shell You should see a $, this means that you are "in" the phone.
15. Type into the command prompt:chmod 0755 /data/local/tmp/rageagainstthecage You should see this echoed on your screen. This is normal. You should still have $ on your cmd line.
16. Type into the command prompt: chmod 0755 /data/local/flash_image You should see this echoed on your screen. This is normal. You should still have a $ on your cmd line.
17. Type into the command prompt:./data/local/tmp/rageagainstthecage A message will pop up on the screen. It will take a few seconds, and your will be kicked "out" of the phone. The $ should now be gone.
18. Type into the command prompt: adb shell You should have a # on your command line instead of a $. # means you have temporary root in your phone. If you do not have #, then start over.
19. Type into the command prompt that has #: ./data/local/flash_image misc /sdcard/mtd-eng.img
20. Type into the command prompt that has #: sync
21. Type into the command prompt that has #: reboot bootloader
22. Your phone will be rebooting now. Eventually your phone will be at the bootloader menu. On your phone use volume up/down to highlight bootloader and press the power button once. It will start loading the PC36img.zip file.
23.After it loads, it will ask if you want to flash. Press Volume UP to say yes. It will now flash, which can take some time. You may see some red fail messages. This is normal.
24.When it is done flashing it will ask you if you want to reboot. Press Volume Down to say now to reboot.
25. Use volume up/down to highlight recovery. Press the power button once. This will try to boot into recovery mode but fail and load a screen with a red triangle. This is normal because you have not installed recovery yet.
26. Go back to your computer screen and your command prompt. You should not have a #
27. Type into the command prompt: adb push recovery /
28. Type into the command prompt: adb shell busybox --install /sbin
29. Type into the command prompt: adb shell nohup /sbin/recovery &
30. After a pause you should see a new screen on your phone. It should be green text with your recovery options.
31. Highlight backup/restore. Press the power button. Highlight backup nand and press the power button. Press the power button again to confirm the action. Your phone is now doing a nandroid backup. This will backup your wimax keys amongst other things.
32. It will take a little time to do the backup. After it is done press the power button once to return to the recovery menu.
33. Highlight enable USB-MS and press the power button.
34. On your computer, you should see a new drive in my computer or a pop up asking you for an action. Click on Explore, or open the drive in my computer, to access your phone like you would a thumb drive.
35. Rename the file named PC36IMG.zip to PC36IMG-ENG.zip and then rename PC36IMG-MR.zip to PC36IMG.zip
36. On your phone, press the power button to disable USB-MS mode. You should be back at the recovery menu.
37. Highlight the option to flash image from zip. Press the power button.
38. Highlight unrevoked-forever.zip and press the power button. Press the power button again to confirm if told to do so.
39. When it completes flashing the image, select reboot from the menu.
40. When it reboots a few things could happen. If you think your phone is frozen, you are okay because that is a normal occurrence on this step.
----->Your phone gets "stuck" on a white screen with the word HTC on it for more than a minute. You need to take the back case off your phone and pull your battery out. Put the battery back in and put the back case on again. Hold down Volume Down and press(and release) the power button while you continue to hold down the volume down button. Your phone should go into the boot loader like it did at the start of the guide.
----->You phone started up and fully booted. You need to completely power off.Hold down Volume Down and press(and release) the power button while you continue to hold down the volume down button. Your phone should go into the boot loader like it did at the start of the guide.
----->The phone returns to the boot loader.
41. No matter which of the 3 scenarios occurred to you in the last step, you are now in the boot loader. Obviously the 3rd scenario is the best, but all are OKAY.
42. The phone should find PC36img.zip. It then loads this file and asks if you want to flash. Use volume up for yes. When it asks to reboot press volume up for yes.
43. When it is done booting, return to your computer screen and type adb shell mv /sdcard/PC36IMG.zip /sdcard/PC36IMG-MR.zip into the command prompt.
44. Type into the command prompt: adb reboot recovery
45. Highlight backup/restore in recovery and then press power. Highlight backup nand and press power. Press power again to confirm. Wait for the backup to complete.
46. Press power to return to recovery menu. Highlight reboot phone and press power.
47. Your phone is now rooted, S-OFF, and booted into stock 3.30.651.2.
-------------------------------------------------------------------------
After Root:
1. Run through setup and get to the actual phone screens.
2. Try to turn on 4G/wifi/etc and see if it all works. It may not and this does not mean disaster.
For me, I had to flash Stock RUU root 3.30.651.3 to get 4G to work. Here is what I did next:
1. Download stock RUU root 3.30.651.3(I opted for Odexed version) from http://forum.xda-developers.com/showthread.php?t=836728
2. Reboot phone into recovery by completely powering off. Hold down volume down and press power. When you get into the boot loader it will try to find PC36img.zip and fail (we renamed that file remember?) and that is normal. Use volume up/down to highlight recovery and press the power button.
3. In recovery highlight USB-MS and press power to enable.
4. Your phone should be mounted as a drive in your computer again like before. Copy the whole zip file that you downloaded for RUU 3.30.651.3 rooted odexed to your phone. Wait for it to finish the transfer.
5. On your phone press power to turn off USB-MS mode.
6. On the recovery menu highlight wipe and press power.
7. Highlight the first wipe option which is something like wipe cache/factory reset. Press power. Press power again to confirm if needed.
8. Hightlight the second wipe option which is wipe cache. Press power and then press power again if needed.
9. Highlight the third wipe option which is wipe dalvik-cache. Press power and then press power again if needed.
10. Return recovery menu.
11. Hightlight flash image from zip and press power.
12. Highlight the file that you just transfered over that is for RUU 3.30.651.3 and press power. Press power again to confirm if asked. It will start flashing the image to your phone, but you will not see progress bars. It will take a few minutes.
13. When it is complete select the option to reboot the phone.
14. The phone should fully boot up into the stock rooted 3.30.651.3 rom.
15. Now try to turn 4G/wifi/etc on and make sure it works. It did for me.
16. Assuming that everything is working fine, fully power off, boot into recovery, and do another backup. This newest backup is your holy grail backup. It is stock rooted S-OFF and 4G working backup.
Note: these last 15 steps can be used to flash any custom rom too. Just make sure that you get your "holy grail" backup first before you experiment.
Click to expand...
Click to collapse
my wife got an evo on black friday from radio shack and i rooted it with unrevoked in like 5 minutes.
I have adhd... I wonder if 4g transmissions cause an increase in autistic spectrum disorders!?!?
Sent from my PC36100 using XDA App
animal7296 said:
It can be rooted you just have to work harder at it. Dont take it back you'll regret it.
Click to expand...
Click to collapse
he wouldn't regret getting the epic, it's a cool ass phone. if you want a crisper lcd and a keyboard get the epic.
fixxxer2008 said:
If you want a cheap-ass plasticky POS, get the epic.
Click to expand...
Click to collapse
Fixed that for you.
tejasrichard said:
Fixed that for you.
Click to expand...
Click to collapse
Thank you. It seems all these Samsung phones feel like garbage. Way too flimsy. Now I have a friend with an LG Optimus S which I just rooted for her, and I have to say the build quality is very nice.

im stuck!!!!! already

i just rooted my phone 10 minutes ago and now i cant get into recovery to restore the back up i made. the only recov i can get into is H-boot then from there it just gets stuck at the htc white screen.. did i brick it ???? i cant find any recent posts on this please help AGAIN sorry
stevo760 said:
i just rooted my phone 10 minutes ago and now i cant get into recovery to restore the back up i made. the only recov i can get into is H-boot then from there it just gets stuck at the htc white screen.. did i brick it ???? i cant find any recent posts on this please help AGAIN sorry
Click to expand...
Click to collapse
So you are at the white screen that says hboot? It should be the second option on that screen saying recovery, use the volume keys to move to it, then use the power button to select it.
Sent from my Xoom using Tapatalk
you can boot into your rom and then reflash recovery, I flash mine a few times as rarely its there the first time
Grab the PC36IMG.zip file from the Amon Ra thread and put it on your SD card. Boot to the bootloader, let it find the file, and update to flash the amon ra recovery. I hate clockworkmod. It's never been as consistent for me as Amon Ra.
you wiped your boot or system partition didn't you?
hold volume down while turning your phone on and it should bring a menu with three android guys at the bottom, once there use the volume buttons to select recovery and then push power to select it. That will get you into the recovery where you can flash a ROM. If it doesn't let you get into the recovery from there and you still have the autoroot folder on your computer you can run the file 'FlashZip' script and tell it to flash the SprintLovers_AmonRA... file. Just put it in fastboot mode before hand by selecting fastboot instead of recovery from the hboot
bwcorvus said:
So you are at the white screen that says hboot? It should be the second option on that screen saying recovery, use the volume keys to move to it, then use the power button to select it.
Sent from my Xoom using Tapatalk
Click to expand...
Click to collapse
i did that and i just takes me to a black screen with a triangle in it
xHausx said:
you wiped your boot or system partition didn't you?
hold volume down while turning your phone on and it should bring a menu with three android guys at the bottom, once there use the volume buttons to select recovery and then push power to select it. That will get you into the recovery where you can flash a ROM. If it doesn't let you get into the recovery from there and you still have the autoroot folder on your computer you can run the file 'FlashZip' script and tell it to flash the SprintLovers_AmonRA... file. Just put it in fastboot mode before hand by selecting fastboot instead of recovery from the hboot
Click to expand...
Click to collapse
you gotta help me man!!!! how do i flash just the recovery in auto root commands??????
stevo760 said:
you gotta help me man!!!! how do i flash just the recovery in auto root commands??????
Click to expand...
Click to collapse
It sounds like you have the old debug firmware installed, the screen with the red triangle is the stock recovery. Pushing vol up + power in it should bring up a menu although there is nothing in there that is of use except reboot.
With the triangle showing on your phone run the FlashZip script and it should reboot you in to the bootloader, once it does that hit enter when it warns you about your bootloader being unlocked and it will give a list of different PC36IMG files. You'll want to flash the one that says SprintLovers-AmonRA to make sure everything is up to date.
xHausx said:
It sounds like you have the old debug firmware installed, the screen with the red triangle is the stock recovery. Pushing vol up + power in it should bring up a menu although there is nothing in there that is of use except reboot.
With the triangle showing on your phone run the FlashZip script and it should reboot you in to the bootloader, once it does that hit enter when it warns you about your bootloader being unlocked and it will give a list of different PC36IMG files. You'll want to flash the one that says SprintLovers-AmonRA to make sure everything is up to date.
Click to expand...
Click to collapse
in the triangle recovery screen no button will bring up any menu... i think im ****ed man this blows
stevo760 said:
in the triangle recovery screen no button will bring up any menu... i think im ****ed man this blows
Click to expand...
Click to collapse
what did it say when you ran the FlashZip script?
stevo760 said:
in the triangle recovery screen no button will bring up any menu... i think im ****ed man this blows
Click to expand...
Click to collapse
i can do it in fast boot mode but as soon as i select number 1 and press enter the dos screen goes away and nothing happens
stevo760 said:
i can do it in fast boot mode but as soon as i select number 1 and press enter the dos screen goes away and nothing happens
Click to expand...
Click to collapse
k, it's not working right then. Can you do me a favor and use the StartShell file then run it from there. If it fails again right click -> select all and then copy and paste it.
To run it from the dos prompt just type flashzip and enter
xHausx said:
k, it's not working right then. Can you do me a favor and use the StartShell file then run it from there. If it fails again right click -> select all and then copy and paste it.
To run it from the dos prompt just type flashzip and enter
Click to expand...
Click to collapse
[1] C:\Documents and Settings\Steven Cirocco\Desktop\AutoRoot_v2.3\res\PC36IMG-S
printLovers-AmonRA_2.3-hausmod.zip
[2] C:\Documents and Settings\Steven Cirocco\Desktop\AutoRoot_v2.3\res\PC36IMG_A
monRA-v2.3-hausmod.zip
[3] C:\Documents and Settings\Steven Cirocco\Desktop\AutoRoot_v2.3\res\PC36IMG_U
D.zip
[4] Cancel
Type a number and press Enter/>1
ERROR: File 'C:\Documents' does not exist!
C:\Documents and Settings\Steven Cirocco\Desktop\AutoRoot_v2.3>
xHausx said:
k, it's not working right then. Can you do me a favor and use the StartShell file then run it from there. If it fails again right click -> select all and then copy and paste it.
To run it from the dos prompt just type flashzip and enter
Click to expand...
Click to collapse
if you can fix this world of **** im in im donating for sure dude
ok, I see what it's doing. Copy and paste the following into the prompt to do it manually
Code:
fastboot oem rebootRUU
Code:
fastboot flash zip res\PC36IMG-SprintLovers-AmonRA_2.3-hausmod.zip
then once it finishes...
Code:
fastboot reboot
xHausx said:
ok, I see what it's doing. Copy and paste the following into the prompt to do it manually
Code:
fastboot oem rebootRUU
Code:
fastboot flash zip res\PC36IMG-SprintLovers-AmonRA_2.3-hausmod.zip
then once it finishes...
Code:
fastboot reboot
Click to expand...
Click to collapse
it says sending zip with blinking cursor and no status meter on my phone but it does say htc
stevo760 said:
it says sending zip with blinking cursor and no status meter on my phone but it does say htc
Click to expand...
Click to collapse
give it a second, it's a big file
xHausx said:
give it a second, it's a big file
Click to expand...
Click to collapse
ok it finished it rebooted and now its at htc quality brilliant screen for 2 minutes and counting
When I experienced the red triangle and inability to boot into recovery, following step #10 of the link below pushed a temporary recovery onto the phone.
http://forum.xda-developers.com/showthread.php?t=829045
You still need to flash (by some means), a permanent recovery.
You can do so using either the PC36IMG.zip method, adb shell, or through console.
holy f !!!!! you developin son of *****!!!!! you are the man!!!!! you literally just saved my life i just got this phone yesterday and my girlfreind is on her way to kill me... so now what do i do about recovery and am i still rooted... and how do i give you money???

[Q] Nexus 7 stuck

Hi,
my Nexus 7 (2013) is stuck on Google screen...
a few days ago I downloaded a lot of movies via utorrent, and utorrent kept crashing. So i forced stop, removed the app, reinstalled it from google play and continued.
My nexys then suddenly freezed for about 1-2mins before i shut it down via the power buttom, and since then it wont start...I've tried almost everything.
The device is stuck on Google screen. I've tried to boot it through the bootloader, recovery mode etc, but it's still stuck on the google screen. downloaded the nexus root toolkit to unlock my device, but it keeps tellin me i've to enable USB debugging. which I can't since my device won't start.
I've downloaded the SkipSoft Android tookit, but not too familiar with the tookit so haven't really tried anything yet (also not sure which android version i'm running)..
Is there ANYTHING i can do?
EDIT: tried using skipsoft android tookit to unlock bootloader, but when coming to the stage where i've to chose yes or no, the device get stuck and the power button does not respond => I can't chose Yes..
EDIT: So I've tried a few things but nothing seems to work..
downloaded a new adb+fastboot directory from another thread. Fastboot commands seems to work, but when i try and erase boot/cache etc the cmd does nothing...had this line for about 10min:
erasing 'boot'..
nothing happens.. when i unplug my device an error message shows (too many links).
so, fastboot won't erase my boot nor my cache, so i tried to fastboot flash bootloader bootloader.img, and it says my bootloader is locked.
fastboot oem lock --> bootloader is alrdy locked
fastboot oem unlock --> stuck at "YES", just as i was when trying with different toolkits.
fastboot -w update image-razor --> Error, failed to load 'img-razor'
soo i'm getting kinda desperate here...
remeber, this was all from a stock rom, no root, no custom rom, just from a freeze when dl movies from utorrent...
i have been stuck like that before. get into to the bootloader screen from where its hung at the google splash screen. once there you can fastboot a factory image.
from the google screen:
1. hold volume up, volume down and power until you get to the screen with the android and its belly open
2. connect to pc
3. download factory image from HERE
4. unzip the tar file you just downloaded and place the contents in your platform-tools folder
5. double click the file named flash-all.bat
6. wait for it to finish and it should boot up just fine.
jase33 said:
from the google screen:
1. hold volume up, volume down and power until you get to the screen with the android and its belly open
.
Click to expand...
Click to collapse
say what? Hold vol.up, vol.down and power until i get to bootloader?
when i press vol up, vold down, and power, holding them all in together from the google screen the device shuts down..
Do you have a youtube tutorial gudie or something?
EDIT:
Also, I've never rooted or done anythign with this tablet except downloading a few apps etc...this crash happened when downloading from utorrent...
The key combination is to be used from being powered off.
Fuzzra said:
The key combination is to be used from being powered off.
Click to expand...
Click to collapse
Yeah, and from what i can read it also needs an unlocked bootloader, which i don't have..
just keep holding the keys down. it will shut down. keep holding it will try to boot back up and take you to the bootloader screen. you do not need an unlocked boot loader. all my nexus devices have locked bootloaders, are rooted and run custom roms.
jase33 said:
just keep holding the keys down. it will shut down. keep holding it will try to boot back up and take you to the bootloader screen. you do not need an unlocked boot loader. all my nexus devices have locked bootloaders, are rooted and run custom roms.
Click to expand...
Click to collapse
shuts down, then nothing... tried holding it down for about a minute.
skampflens said:
shuts down, then nothing... tried holding it down for about a minute.
Click to expand...
Click to collapse
like this
jase33 said:
just keep holding the keys down. it will shut down. keep holding it will try to boot back up and take you to the bootloader screen. you do not need an unlocked boot loader. all my nexus devices have locked bootloaders, are rooted and run custom roms.
Click to expand...
Click to collapse
also, should add that i tried to unlock oem via the cmd, tried to flash boot.img but nothing..
when typing fastboot oem unlock, it got stuck at "Yes" when trying to unlock bootloader, and when typing flash boot, it said error, cannot flash boot.img..
AND i'm not running a custom rom, just the standard stock rom
one step at at a time. lets get you to the bootloader screen first. all good things happen from there.
jase33 said:
one step at at a time. lets get you to the bootloader screen first. all good things happen from there.
Click to expand...
Click to collapse
uploading a video....
only way i can access fastboot is via volume down and powerbutton..and that's when the device is shut down
<iframe width="560" height="315" src="//www.youtube.com/embed/SRfrjR9Y8fI" frameborder="0" allowfullscreen></iframe>
OK. but you can get there. yes?
jase33 said:
OK. but you can get there. yes?
Click to expand...
Click to collapse
Yes, I can access bootloader (fastboot mode).
tho i don't know which version i'm running..
it's either 4.4.2 (KOT49H) or 4.4 (KRT16S).
however, when running flash-all it says "fastboot is not recognized as an internal or external command"
http://www.youtube.com/watch?v=SRfrjR9Y8fI&feature=youtu.be
dont worry about version. it does not matter. lets focus on your connection to the device. do you have ADB setup on your pc? if you dont, go to THIS thread and get minimal ADB & fatboot from shimp208. install it and run it.
jase33 said:
dont worry about version. it does not matter. lets focus on your connection to the device. do you have ADB setup on your pc?
Click to expand...
Click to collapse
Yeah, at least i think so.. downloaded the adb bundle pack..
plug in your device and type "fastboot devices". tell me if you see a serial number display
jase33 said:
plug in your device and type "fastboot devices". tell me if you see a serial number display
Click to expand...
Click to collapse
nope, it says "fastboot" is not recognized as an internal or external command, oparable program or batch file.
http://www.youtube.com/watch?v=RLjLdHxuENg&feature=youtu.be
ok. you dont have fastboot. go and install Minimal ADB and Fastboot
jase33 said:
ok. you dont have fastboot. go and install Minimal ADB and Fastboot
Click to expand...
Click to collapse
serial nr does show!
great! have you downloaded the factory image for your device yet? get it HERE if you have not. make sure you get the right one. if your device is wifi only select that one, if it had mobile data and a sim card get the one for mobile..

[TUTORIAL][CM11][4.4.2] CyanogenMod Tutorial for Sony Xperia Tablet Z (pollux)

I went through a lot of searching and trouble to install CM11 on my Xperia Tablet Z, and I'd like to share a tutorial I made for anyone who is also wanting to accomplish this.
All links are in Dark Green because I cannot post links yet.
1. Download and extract the ADB+Fastboot+Drivers zip (alexpja.com/sony/adb-fastboot-win.zip)
2. Now we’ll unlock the bootloader.
a. If you do not have a Phone app (like I don’t on the SGP351), you can either get the IMEI from About -> Status in the settings OR you can find the IMEI right after the IC code, nearby the barcode on the bottom of the tablet.
b. If you do have a Phone app, enter *#06# to retrieve the IMEI.
c. Save this for later use.​3. Place the tablet into fastboot mode and connect it to the computer.
a. Power off the device
b. Connect USB to computer
c. While plugging in the other side of the USB cable into the tablet, hold down the Vol + button.
d. If your speakers are on, you should a sound.
e. We have to install the drivers for fastboot. Open devmgmt.msc via the Run window or in the Start menu and in Other Devices section, you should see S1 Service or S1 Fastboot (anything containing S1).
i. If it is showing a yellow exclamation mark: Follow 3.e.i.1. If it is not, continue to 3.f.
1. We need to download Flashtool and use the driver setup. Download Flashtool (unrestrict.li/flashtool) and install it.
2. Find cmd.exe, right click it, and select Run as administrator.
a. Type in
Code:
bcdedit /set testsigning on
and press enter.
b. Reboot your computer.​3. Once you have rebooted the computer, open the folder where you installed Flashtool (default: C:\Flashtool).
4. Open up the drivers folder and open Flashtool-drivers.exe.
5. Select the first two driver choices (Flashmode and Fastboot) and select “Xperia Tablet Z Drivers” and continue.
6. A new window will appear, continue on with that.
7. A window like this may appear a few times, just press Install this driver software anyway.
8. Run 3.e.2. again and run
Code:
bcdedit /set testsigning off
. Reboot your PC now or after the tutorial.​f. The LED pulse light above it should be emitting a blue-ish color. The screen will be dark.​4. Now we’ll verify if you have fastboot running.
a. Open the tools folder that was extracted from the ADB ZIP and double-click on START.cmd to open Command Prompt in the current directory (all it does is literally open cmd.exe, you can edit the script to verify).
b. Run the command
Code:
fastboot -i 0x0fce getvar version
. If you get
Code:
<waiting for device>
, then you did something wrong. Retrace your steps! (For example, I get
Code:
version: 0.5
)​5. Go to (unlockbootloader.sonymobile.com) and continue until you reach the screen where you put type in the IMEI and an email address. Type in the first 14 digits of the IMEI (remove the last one) and your email address (not sure if name is required). You should get an email instantly with the key.
6. In the Command Prompt, run
Code:
fastboot -i 0x0fce oem unlock 0xKEY
where KEY is the key you received in the email from Sony.
7. Download whatever release you would like to use on the tablet (I’m using CM 11 nightly) from (download.cyanogenmod.org/?device=pollux)
a. Optional: Also download gapps for Google apps such as Gmail, Google Play Services, etc. (wiki.cyanogenmod.org/w/Google_Apps)​8. Extract the ZIP file (but don’t delete it either) and copy boot.img to the tools folder.
9. If your device is still turned off, turn it on and enable USB storage mode. Copy the CM zip to either the internal storage (sdcard) or, if one is inserted, the microSD card (sdcard1).
10. Place it into fastboot mode again (#3).
11. Go back into the Command Prompt and enter:
a.
Code:
fastboot -i 0xfce flash boot boot.img
b.
Code:
fastboot -i 0xfce reboot
c. Enter recovery.
1. Once it shuts down, rapidly tap the Vol + button in order to get into the recovery.
2. Grep_The_Truth's tip: Look at the LED. It will turn orange and afterwards it'll turn purple. You want to press Vol+ as soon as it changes colors.​12. Select “wipe data/factory reset” and wipe it. Afterwards, go back to main menu.
13. Select “Install zip” and either select “Choose zip from /sdcard” (internal storage) or “Choose zip from /storage/sdcard1” (microSD card).
I’ve had varying experience with installing from the /sdcard because sometimes it doesn’t want to mount /data while wiping (/data/media which is /sdcard is safe in wipe) the tablet, so if you were to install the zip from /sdcard with the error present, it would screw things up. I prefer the microSD card route (/storage/sdcard1), and you don’t even need a big one. 512MB works just fine. The actual path would be /sdcard/0/ when looking for the cm.zip in the internal storage.
14. When you have chosen to install from either /sdcard or /storage/sdcard1, select the cm.zip and install it.
a. If you downloaded gapps.zip, install it the same way as you did with the cm.zip.​15. Go back to the main menu now and select “reboot system now”
a. Once, I had the option to install root access before rebooting, I declined (was planning on rooting after tutorial) but it gave me root anyway.​
That’s it! You can now use CyanogenMod with the Sony Xperia Tablet Z.
Getting in to recopvery
I just struggled with entering recovery for way too long and I want to help others avoid this. I kept finding vague instructions.
The step I want to clarify is:
c. Once it shuts down, rapidly tap the
Code:
Vol +
button in order to get into the recovery.
Click to expand...
Click to collapse
This didn't work for me because if you press Vol+ too soon it goes right back in to fastboot mode. If you press it too late you will miss the recovery mode. You only have to press Vol+ once.
Please change step c. to read:
Look at the LED. It will turn Orange and then Purple. You want to press Vol+ as soon as it changes from Orange to Purple to enter recovery mode.
Grep_The_Truth said:
I just struggled with entering recovery for way too long and I want to help others avoid this. I kept finding vague instructions.
The step I want to clarify is:
This didn't work for me because if you press Vol+ too soon it goes right back in to fastboot mode. If you press it too late you will miss the recovery mode. You only have to press Vol+ once.
Please change step c. to read:
Look at the LED. It will turn Orange and then Purple. You want to press Vol+ as soon as it changes from Orange to Purple to enter recovery mode.
Click to expand...
Click to collapse
I'll add it along with mine, because I can do it with no problem.
alexpja said:
I'll add it along with mine, because I can do it with no problem.
Click to expand...
Click to collapse
alexpja Thanks for your tutorial, this is very detailed and easy to follow.
my Xperia is SGP321.
I put it into practice and the results it gives me the "oem unlock" is:
FAILED: (remote: Command nor allowed).
I guess you should treat my tablet has the bootloader locked and not allowed (for now??) the unlocked.
I hope someone gives us the opportunity to unlock the devices and in the future can be unlocked.
I had the same experience where at times the steps were a little confusing, especially for a beginner. Each set of instructions would either leave something out or skim over it as if everyone already knew it. That's understandable since they were probably written for that audience. I soft-bricked my SGP311 at least 10 times.
I was even going to write something like this but I got lazy.
One suggestion I would offer is to request the bootloader unlock key first since it sometimes takes a little while and a person can reduce the possibility of having to stop and wait just when they are making progress.
And for anyone going this route for the first time, don't make my mistake - flash exactly what the instructions say to flash, particularly boot.img. Once you have that recovery flashed you have a lot more control over your device. If something goes wrong in a following step like getting boot loops you can still fix it. But if you get annoyed and start poking at it then you can mess up the recovery. Then you have to reset everything to stock and just about start over.
While I don't want to say something stupid like claiming the tablet is indestructible, I found that whether I got stuck in a boot loop I couldn't get out of or screwed it up so bad that all I could get from the tablet was an occasional LED flash, I could always restore it using Emma. It's annoying to have to start all over but it's a huge relief when it boots normally.
for me flashing was fine and without any error but my Tab doesn't boot up with CM flashed...any idea?
Hanging at reboot
Hi.
I tried this procedure on my sony xperia tablet z 311. It unlocked fine and wrote boot.img fine but on reboot command, I get a red light and it hangs there.
I've managed to get it back to fastboot mode (pressing power and vol+, some white blinking lights).
But that's it, that's all I can do with this right now. It's a brick that can get into fastboot mode and that's it. Any time I write a boot.img (have tried a different one also), it writes fine but hangs with a red light at reboot.
Edit:
Used Sony's Emma in flash mode to get back to stock, tried again and it worked.
Maybe the problem was using the pollux instead of pollux_windy download, my bad.
Guess my bootloader won't be unlocked. This is A lot of work. Good job on the write up though maybe one day I'll tackle it.
BOOT LOOP Step 9
All was going well, but step 9 powering on device, now its looping.....Ill use flash tools to put jelly bean on and try again, since i was trying with kitkat...why i suspect kitkat is the issue, before i used to be able to unlock and lock boot-loader with jelly bean but with kitkat it didn't work, which i then forced it via cmd
No GPS
I used the tutorial for my Pollux Windy (WiFi Only) and used the latest nightly. everything went well but my GPS is now broken. Is this a known issue?
kevinsickles said:
Is this a known issue?
Click to expand...
Click to collapse
yep! use search to find out more.
mulebreath said:
Hi.
I tried this procedure on my sony xperia tablet z 311. It unlocked fine and wrote boot.img fine but on reboot command, I get a red light and it hangs there.
I've managed to get it back to fastboot mode (pressing power and vol+, some white blinking lights).
But that's it, that's all I can do with this right now. It's a brick that can get into fastboot mode and that's it. Any time I write a boot.img (have tried a different one also), it writes fine but hangs with a red light at reboot.
Edit:
Used Sony's Emma in flash mode to get back to stock, tried again and it worked.
Maybe the problem was using the pollux instead of pollux_windy download, my bad.
Click to expand...
Click to collapse
Hi,
I've been trying with my Xperia Tablet Z Wi-Fi SGP311. Ran into the same problem. On reboot command the LED was stuck on red for 10 minutes and the cmd window was still open. I unplugged the USB and the LED would not turn off. Tried some things, I don't remember specifically what, but it got the LED to turn off. Now my device can't be detected. I've downloaded Emma and it is not recognising my tablet. I've tried to plug the USB in while hold Vol +, Vol -, and the Power button. No detection for any. All I can do with my tablet is make the LED flash white, purple and red in rapid succession by holding Vol + and Power for 5 seconds.
Anyone know what's happened? I suspect I've completely bricked it :L
EDIT: Apparently there are different modes which you can cycle through. If you hold down Vol + and Power for 5 seconds, the LED will flash according to which mode the tablet is in. The different modes give these flashes:
- 1 White flash
- 3 Rapid which flashes
- A white, purple and red flash in quick succession
To switch between the modes, I hold down Vol+ and Power, and after 5 seconds it will take around 3 more seconds to change modes. One of these modes will not appear unless plugged into a PC. What do these mean and can I do anything with it? Tablet is still bricked.
EDIT2: I've managed to get Emma to recognise my tablet. Turns out the modes do have different purposes. I should be fine now, problem solved. I will just leave the solution here in case anyone runs into the same problem.
Unplug your device and hold Vol + and Power for 10 seconds. At the 5 second mark your LED should flash white ONCE. Keep both buttons held and within 5 more seconds, your LED will flash white THREE times consecutively. This will allow you to enter Flashmode (plug in USB while holding Vol -) and Fastboot (plug in USB while holding Vol +). For Emma to recognise your device, enter Flashmode and you can restore and try again.
Bootloop
I've tried many times to flash cyanogenmod onto my Xperia Tablet Z (SGP311). This is a Wi-Fi only tablet and I have downloaded the versions of CM from (download.cyanogenmod.org/?device=pollux_windy) I've followed all of the steps and tried all of the versions of CM down to 10.2 (I used GApps10.2 for CM10.2). Each version gets stuck in bootloop. I've cleared all data (in CWM - wipe data/factory reset, wipe cache partition, wipe delvik cache) before flashing CM and GApps; however, when I try to clear data I get an error. This is what the tablet says:
-- Wiping Data...
Formatting /data...
Error mounting /data!
Skipping format...
Formatting /cacha
Formatting /sd-ext...
Formatting /sdcard/.android_secure!
Skiiping format...
Data wipe complete.
Click to expand...
Click to collapse
I'm thinking the "Error mounting /data" is the problem, but I'm not entirely sure, nor am I sure of how to fix it.
Any suggestions?
EDIT: Turns out I'm just really bad with Android stuff. I ended up flashing the original Xperia software, unlocking the bootloader (according to this tutorial's instructions), then I downgraded to 4.1.2, rooted my tablet (forum.xda-developers.com/showpost.php?p=53063218&postcount=14) and installed the PhilZ and TWRP custom recoveries. I didn't get to use them in the end. For some reason CWM kept coming up no matter what combination of buttons I pressed while rebooting. After downgrading and rebooting, I followed the rest of the instructions on this tutorial (from step 7). This time I got no errors while cleaning the disk, cache and delvik cache. Flashed the zip files, rebooted the device and voila, Cyanogenmod11!
Again, I'll leave this edit here in case someone runs into a similar problem. I couldn't get any version of CM until I rooted first.
I followed this guide and bricked my device. If anyone has any tips - PLEASE HELP!
I tried to flash CM11, all seemed to be going great until CM11 and Gapps where installed any I hit "Reboot system now" in CVM. The device never booted again (I which I knew why!), and is now pretty much dead. I can however:
- Enter Flashmode
- Enter Fastboot mode
- Relock/Unlock bootloader
- Emma recognizes my device just fine in flashmode.
So I still think there is some hope, right?
I have tried installing the firmware that Emma suggests, doesn't work.
I have tried flashing a firmware I found on the internet with Flashtool, doesn't work.
I have tried relocking the bootloader and trying to repair the device through SUS, doesn't work.
So, PLEASE, help my sort this out! I would be forever greatful!
tp_88 said:
I followed this guide and bricked my device. If anyone has any tips - PLEASE HELP!
I tried to flash CM11, all seemed to be going great until CM11 and Gapps where installed any I hit "Reboot system now" in CVM. The device never booted again (I which I knew why!), and is now pretty much dead. I can however:
- Enter Flashmode
- Enter Fastboot mode
- Relock/Unlock bootloader
- Emma recognizes my device just fine in flashmode.
So I still think there is some hope, right?
I have tried installing the firmware that Emma suggests, doesn't work.
I have tried flashing a firmware I found on the internet with Flashtool, doesn't work.
I have tried relocking the bootloader and trying to repair the device through SUS, doesn't work.
So, PLEASE, help my sort this out! I would be forever greatful!
Click to expand...
Click to collapse
download a proper stock (not bricked) firmware for your device and flash with flashtool.
Rootk1t said:
download a proper stock (not bricked) firmware for your device and flash with flashtool.
Click to expand...
Click to collapse
What makes you think that the stock firmwares I've tried are bricked? I've since my post tried one which I downloaded through Flashtool - same result.

Categories

Resources