SOLVED - htc could have done a slightly better job of clarifying how to complete each step, however, successfully completed, on to rooting
hello, i am trying to unlock my boot loader for my htc amaze
however, after running the sdk manager.exe I am not sure which android api's to select to proceed past step 5
can anyone help?
thanks
Related
Hi
I've just tried to flash my phone to run Android but I think I've made a bit of a bodge of it.
I got it to SPL-1.66.0000 then it was showing that it was running that HSPL on the Bootloader now it's just showing SPL-1.66.0000.
I cannot start the phone I get a purple circle that's it like I always did just before starting the phone and it usually goes past that and into Windows.
I can get into Bootloader but I've no idea what to flash, what to flash it to and how to do it.
If there is anymore information you want to know then please do ask It'd be very greatful if someone can lend us a hand getting this running.
Thanks
I've now actually read the instructions and found out that it wipes the phone, however I've got Magldr installed but I cannot open it I'm running SPL-2.08.HSPL
However, again I get the Purple Circle, I've tried pressing the "Phone" button to get into Magldr as I was told, I've found another one which told me to press both UP/DOWN Volume which sent me to another Recovery place.
Any help would be great.
What exactly is your target?
What ROM was originally on your device (branded or non-branded)?
I bought the HTC HD2 today - It WAS locked to T-Mobile now unlocked, however unlike other T-Mobile HD2's I've seen it hasn't got branding on the top BUT did have Branding on the boot up.
So
Non-Branded Casing
Branded Software
My Target
To run Android 2.3
I think a good start for you is here: Klick!
You will have to decide if you want to run Android from SD card or NAND.
Running Android from SD card means you don´t have to delete the Windows Mobile ROM, many people like the "dual boot" option. In this case, you should read the instructions of the ROM chef how to install.
In short, if you want to install Android in NAND memory, you must do this:
1) Install HSPL (if not already done)
2) Install Radio ROM 2.15.50.04
3) Install MAGLDR 1.3
4) Install your Android ROM
If you follow the link, you´ll find more links to step-by-step instructions.
Hey everyone,
I'm pretty new to this scene and I'm looking to get a semi-technical understanding of the boot process that an Android device takes. I've done the searches and found the articles, threads, blogs and this is what I've found so far. I appreciate any answers at all that anyone can give
Here is my understanding:
1. Power-on Device
2. Boot ROM is executed from known location in System ROM and loads the First Stage Loader into RAM.
However, RAM has yet to be initialized, right?
Also, am I correct in assuming the Boot ROM and First Stage Loader are two separate things?
3. First Stage Loader (aka "Radio" which contains baseband firmware) is executed and initializes radio hardware (Cell, GPS, Bluetooth, WiFi, etc)
4. First Stage Loader loads Second Stage Loader into RAM
Second Stage Loader is also known as the SPL, correct?
Is HBOOT a Second Stage Bootloader? I have seen conflicting/contradicting information on this.
How similar is Second Stage Bootloader to GRUB?
5. Second Stage Loader will either boot to the "System" partition by default, but also has an option to boot to the "Recovery" partition should the user decide to.
(To be continued...)
How accurate is all this information?
Thank you guys very much, I really appreciate your help.
Geddup said:
Hey everyone,
I'm pretty new to this scene and I'm looking to get a semi-technical understanding of the boot process that an Android device takes. I've done the searches and found the articles, threads, blogs and this is what I've found so far. I appreciate any answers at all that anyone can give
Here is my understanding:
1. Power-on Device
2. Boot ROM is executed from known location in System ROM and loads the First Stage Loader into RAM.
However, RAM has yet to be initialized, right?
Also, am I correct in assuming the Boot ROM and First Stage Loader are two separate things?
3. First Stage Loader (aka "Radio" which contains baseband firmware) is executed and initializes radio hardware (Cell, GPS, Bluetooth, WiFi, etc)
4. First Stage Loader loads Second Stage Loader into RAM
Second Stage Loader is also known as the SPL, correct?
Is HBOOT a Second Stage Bootloader? I have seen conflicting/contradicting information on this.
How similar is Second Stage Bootloader to GRUB?
5. Second Stage Loader will either boot to the "System" partition by default, but also has an option to boot to the "Recovery" partition should the user decide to.
(To be continued...)
How accurate is all this information?
Thank you guys very much, I really appreciate your help.
Click to expand...
Click to collapse
Those are exactly my questions.....its surprising that no one has replied
http://javigon.com/2012/08/24/from-poweron-to-android-the-boot-sequence/
and
http://www.androidenea.com/2009/06/android-boot-process-from-power-on.html
Thanks I was interested too
Do you know of a way to decrease the time it takes AT&T's TITAN to start-up?
When powering up, I go through three splash (a.k.a. boot) screens:
1) HTC 2) AT&T rethink possible 3)Windows Phone
I would like to speed up how long each of these screens are displayed (or eliminate one or more of them) to say time going from Off to the Lock Screen.
FYI: I'm not a developer and don't have access to Developer Tools
Thanks for Your Time!
Phone: HTC Titan PI39100
OS: Windows Phone 7.5 v. 7.10.7720.68
Firmware Revision No. 1600.2200.11004.502
Hardware Revision No. 0002
Bootloader v. 1.10.160015.3(132409)
Modifications: NONE
Unfortunately we can't do that without having an unlock (I don't know what level of unlock, but certainly higher than a developer unlock). The HTC logo can be overwritten with a flashing tool (but don't try it yet, I don't think any compatible flashing tool has been made yet).
Sit tight! If/when custom ROMs start popping up, the ability to flash over the HTC logo will soon follow.
Hello, well I recently got this HTC evo 3D from a friend, he bought it extemely cheap since it was not working, and he tried to fix with no success so he gave it to me to try. The thing is that I have some experience fixing samsung phones but HTC seems like a really new thing to me. Anyway the first thing I would like to ask its about the real state of the phone. The phone only turns on and shows a black screen, the htc logo in white letters at the center, and one triangle in each corner, all of the triangles have an exclamation mark.
Thats all it shows, I tried the volume down + power button to enter the recovery screen but it doesnt work. We dont really know what happened to the phone or how this device was bricked, and since I dont really know htc I cannot really guess. Not sure either if this device is either S/On or OFF, rooted or etc.
I read the HTC Unbricking Project and thought "I might as well try that", but I dont really understand what they are saying, not about using linux, its about the tools they say you need:
the appropriate package for the device
the latest RUU for your device
a device bricked by writing security flag 3 with an unsigned hboot, or caused by a damaged hboot via interrupted OTA update/RUU flash on a S-ON device
We dont use any of this on samsung phones so I dont really understand what they mean, could anyone offer an overall advice of what should I do or where to read about this stuff.
Thanks in advance
Update: I managed to get this white screen when I unplugged the usb cable, hope it helps
Robert1989 said:
Hello, well I recently got this HTC evo 3D from a friend, he bought it extemely cheap since it was not working, and he tried to fix with no success so he gave it to me to try. The thing is that I have some experience fixing samsung phones but HTC seems like a really new thing to me. Anyway the first thing I would like to ask its about the real state of the phone. The phone only turns on and shows a black screen, the htc logo in white letters at the center, and one triangle in each corner, all of the triangles have an exclamation mark.
Thats all it shows, I tried the volume down + power button to enter the recovery screen but it doesnt work. We dont really know what happened to the phone or how this device was bricked, and since I dont really know htc I cannot really guess. Not sure either if this device is either S/On or OFF, rooted or etc.
I read the HTC Unbricking Project and thought "I might as well try that", but I dont really understand what they are saying, not about using linux, its about the tools they say you need:
the appropriate package for the device
the latest RUU for your device
a device bricked by writing security flag 3 with an unsigned hboot, or caused by a damaged hboot via interrupted OTA update/RUU flash on a S-ON device
We dont use any of this on samsung phones so I dont really understand what they mean, could anyone offer an overall advice of what should I do or where to read about this stuff.
Thanks in advance
Update: I managed to get this white screen when I unplugged the usb cable, hope it helps
Click to expand...
Click to collapse
I can't make out what all that says on your white screen(that's bootloader by the way.) I need you to tell me a few things first.
1.Is the device s-on or s-off? To find out go to the top line and read across to see if it is s-on or s-off
2. Is the bootloader locked, relocked or unlocked? You can see the status at the very top highlighted in purple.
3. What's the hboot version
4. Also, what's the radio band number?
Now the thing is, with HTC devices there are two different s-off's
S-on bootloader unlocked and true s-off. S-on bootloader only gives you access to some of most of the name memory unlocked. You can't downgrade firmware. You can only flash your current one or upgrades. If you upgrade your firmware, your stuck. S-off gives full access to the whole nand memory. The idea is to gain s-off as it is much easier to flash things, more access to software, can upgrade or downgrade your hboot and firmware.
Edit: I got good news for you. Since your able to access your bootloader screen, your phone is not bricked. As a matter of fact, as long as it can boot up to something, its not bricked. Now keep in mind, you will need to download an ruu file and run it to restore that phone.
Robert1989 said:
Update: I managed to get this white screen when I unplugged the usb cable, hope it helps
Click to expand...
Click to collapse
I've never seen that orange "RUU" flag on the bootloader screen before. I'm not sure what it means but it may need to have the 2.89.651.2 RUU (the build it currently has) re-flashed so I would try running that version of the RUU (similar to Kies) after connecting it via USB to a Windows PC.
You can get the RUU here.
ramjet73
Your bootloader indicates you're S-ON and Re-Locked, which means that it was once HTC unlocked (The manufacturer's poor substitute for unlocking a bootloader)
The device is definitely not Bricked by any definition of the term. A true brick doesn't power on. This is just "soft bricked" meaning it's functional, but has a corrupt partition or partitions that are preventing it from reaching the android subsystem.
You need to use the RUU EXE when you're at that white screen. It should recognize it and re-flash most of the partitions on the device. You might also need to run it twice possibly.
So the story is I got this phone from a friend for free and it's not working. Next is some info I have found.
First is the forever bootscreen.
*** LOCKED ***
*** SECURITY WARNING ***
SHOOTER_U PVT SHIP S-ON RL
HBOOT-1.49.0018
RADIO-10.14.9020.06_M
eMMC-boot
Oct 3 2011, 15:03:01
....................
Some phone info.
HTC 3D EVO FCC ID: NM8PG86300
Model: PG86300
IMEI: 35871044661787
S/N: HT1CYV211753
P/N: 99HNJ004-00
a token example from fastboot, at htcdev returns error 150 - doesn't allow me to proceed with unlock of the bootloader.
<<<< Identifier Token Start >>>>
47B3145FF96274E03070C998F66FF7BD
C7245D1F8DF602901AAD442C71F4EB5C
B9B4081EA26F6A82B3EABDC8544686F1
1AC27EA1394FF8AEDA634395FA0A8FBE
6288792606968C46841EE9B7670F20C9
5D1B1C1295D3882C81BCA01AE0E3A179
11673423F363A34C1797CDA128371DAE
9DB4C0B7500FE097C43CCBFB50377180
F56738F0C03BA925749693A2FCEF1E9A
AAAEFE9EFDD676CB56E9787B9D42F3BA
D87FBEAD3B4F8D0A283D2C2E376A1779
36C5EA4FF479C7B811BB3B273E4DEF8A
066110BCDEB9AF842DC2588DAB982383
73A0E6825419B45B5CF37CA6A011DBF0
CDCFF3D8EE40F36DE4223A70272CE7E4
4D16C6CB24E5CD3FC0D03BFDACBC7F4F
<<<<< Identifier Token End >>>>>
I hope that's enough data.
To sum up it is locked with S-ON. Selecting recovery/factory reset reboots it in 1 sec to bootloader. Phone does respond to some fastboot commands, most useful was fastboot oem rebootRUU that takes me to a black screen with an HTC logo and if I disconnect a usb cable I'm stack in bootloader like menu with the only choice 'RUU' that is not click able at all. I have tried enormous number of .img files through fastboot flash (loads, throws: remote: signature verify fail) and using an sd card(loads, verifies, goes back to main menu). I'm in process of trying out RUU exe files from website url androidruu with provider shooter (I can't post urls) First run I thought was going to be a success, it found the phone said that the current version is something like &20, started doing something - restarted the phone and phone got stuck at black screen when the program exited with code 155, while waiting for the phone to get to bootloader I assume. Please your suggestions, maybe deeper knowledge of fastboot protocols would help. Device is not showing up under adb. I was trying all of that using windowsXP/ubuntu computer. please help reinstalling, reviving, flashing this half alive HTC EVO 3D. I believe it is called roger as well. And I assume the previous owner is an idiot.
Some more to say
Ive spent 24 hours with google, HTC EVO 3D (GSM i believe), usb cable and an SD card, i'm lost and despair.
first of all make sure your bootloader is locked .you can lock it via fastboot : Type the following in the command prompt window:
fastboot devices
This is to ensure that your device is detected, if nothing appears on screen with this command, then it means you don’t have the proper drivers installed on your PC. And if that’s the case you should download and install/re-install the HTC Sync software given in Step 1.1Now type the following command to re-lock your HTC bootloader
fastboot oem lock then download and run this and follow the instructions http://www.androidruu.com/getdownlo...00U_11.25.3504.06_M_release_262714_signed.exe
Sent from my Panasonic printer Buy me a beer cause i'm alcoholic and i need more and more https://www.paypal.com/cgi-bin/webscr?cmd=_s-xclick&hosted_button_id=HN6YQLDZT76EE
Hi i have a same problem,,,after install the RUU its says everithing is ok and fine your phone is now reboot,,,and after reboot it stuck at the white screen with a HTC logo,,,i dont know what can i do,,,can you help me please ? my bootloader is locked and i think i dont do anything wrong,,,,and my second problem is i cant go into recovery mod,,,if i press the power button to open the recovery mode in bootloader the phone will reboot as normall and stuck at the white screen with a HTC logo,,, :/ i looking for a soution 3 days,,, but noting happened,,, i really dont know what can i do ,,, any ideas ? plss.. :/
Informations :
Shooter_U (ics) S-on
Radio : 11.25.3504.06_m
and the Ruu what i used is ( RUU_SHOOTER_U_ICS_35_S_HTC_Europe_3.28.401.1_Radio_11.77.3504.00U_11.25.3504.06_M_release_262714_signed .exe)... im very depressed about it... (( please help me to get back to life my evo... :/,,and sorry for my bad english :/
first of all you cant get to recovery cauese the ruu erased your custom recovery.if the ruu was succesful and you can not boot your phone it can be a hardware damage...
edit: what is the result after running ruu? its succesful or what?
Sent from my Panasonic printer Buy me a beer cause i'm alcoholic and i need more and more https://www.paypal.com/cgi-bin/webscr?cmd=_s-xclick&hosted_button_id=HN6YQLDZT76EE
yes,,,its says succesful,,,you are succesfuli installed the stock rom now your android phone will reboot and ready to use.. ,,or something like that,,,but after reboot its stuck on white screeen...
Any solution? plss help me .. :/