Related
I know apparently this isnt the best way to flash your HD2, but im stuck without any access to windows. (mac user)
i cant seem to find step by step instructions on how to do this properly....
is there a link somewhere i can get to so i can figure this out? isnt it as simple as copying the custom.nbh file to the root of my memory card, and entering the bootloader screen?
Sorry for all the noob questions.
take ruu_signed.nbh, copy it to sdcard formatted fat32 (2gb cards seen to work best) rename it leoimg.nbh, boot to bootloader and it should detect the image and ask if you want to flash.
it still requires hspl, unless you have a goldcard(easier to borrow a pc for two minutes to apply hspl than make a goldcard)
the phones already been flashed with hspl.
i just want to change the rom!
Thanks for the tips im going to go for it right now
newnoise1024 said:
the phones already been flashed with hspl.
i just want to change the rom!
Thanks for the tips im going to go for it right now
Click to expand...
Click to collapse
Hi
One advice you have to remember is DO NOT flash any official rom with this method. If you do it will replace the hspl and you will be stuck.
Good luck
sabes143 said:
Hi
One advice you have to remember is DO NOT flash any official rom with this method. If you do it will replace the hspl and you will be stuck.
Good luck
Click to expand...
Click to collapse
True, flashing a stock rom via sd card will overwrite hspl with the new stock spl, but you will not necessarily be stuck. That used to be the case before hspl2, as the original hspl only worked with spl 1.42.0000. HSPL2 now works with 1.42.0000, 1.66.0000 or 2.08.0000 spl's.
or just throw your mac away and buy a PC
What many forget is that you actually need an SD card and not SDHC, as those will not work.
understand u already flash hspl,
microSD / microSDHC will work as long it is formatted with FAT32 fs.
just copy the *.nbh to SD root & rename it to LEOIMG.nbh.
enter bootloader, follow on-screen.
if bootloader cant find any rom image, run scandisk & try again.
gd luck.
I just flashed this rom.
It seemed to be fine. It installed and looked a-ok.
I had a look around and every thing looked as it should.
I added "26.4 column Start menu.cab" and now the phone won't reboot at all.
It gets to the HTC white screen, and then hangs.
Any ideas?
Is it a conflict between the 4 columns app and the ROM?
url_paul said:
I just flashed this rom.
It seemed to be fine. It installed and looked a-ok.
I had a look around and every thing looked as it should.
I added "26.4 column Start menu.cab" and now the phone won't reboot at all.
It gets to the HTC white screen, and then hangs.
Any ideas?
Is it a conflict between the 4 columns app and the ROM?
Click to expand...
Click to collapse
when you say "just flashed this rom", what rom?
also, did you read ALL the first few posts in the chefs thread? chances are it requires a specific radio version
either that or you didn't do a hard reset after you flashed.
apologies, I replied in here when I thought I was in the HTC Energy thread.
The device rebooted after the flash.
Does that not count as a hard reset?
samsamuel said:
Is it T Mobile usa? if so, then you have flashed an incompatible rom.
tmous (T Mo US) phones will opnly take roms based on 2.10, the rom you have installed is 1.66 (D 1. 66. Kumar)
Kumar has a rom in the Tmo US section based on 2.10, you should use that, not the one in teh normal hd2 section.
With power off, press and hold "volume down", tap the power key and continue to hold vol down until you get the three coloured screen, connect to usb, wait for word 'serial' to become 'usb' and flash a compatible rom.
Click to expand...
Click to collapse
I've just been digging through and saw this, I have the 3 colours and USB.
Gonna try and reflash and see what happens.
These forums own!
edit: re-flashing it went the same way, would hang on boot.
I've gona back to using:
_HTC HD2_RUU_Leo_HTC_WWE_1.66.405.2_Radio_Signed_15.30.50.07U_2.06.51.07_Ship
for the moment.
I'll look and see what it is I missed that stopped the energy rom from working as advertised.
Try installing the recommended Radio
url_paul said:
I've just been digging through and saw this, I have the 3 colours and USB.
Gonna try and reflash and see what happens.
These forums own!
edit: re-flashing it went the same way, would hang on boot.
I've gona back to using:
_HTC HD2_RUU_Leo_HTC_WWE_1.66.405.2_Radio_Signed_15.30.50.07U_2.06.51.07_Ship
for the moment.
I'll look and see what it is I missed that stopped the energy rom from working as advertised.
Click to expand...
Click to collapse
I ran into the same problem and all I had to do was to get the phone into Bootloader and then flash the radio recommended by ROM Cook.
also the same problem
I have also this problem, but I think it's in the rom, when I installed the rom, everything seems ok, but after a reset, the screenthat I get is the white HTC screen.
After a hard reset it is ok, but after a reset it is the same problem.
Then I thought, i take an older rom, but when I've installed the rom he is automatic installing the cab file's at the end of the installation, and he's going to automatic reset the HD2. After the reset I have the same problem as with the new rom.
So the biggest problem is that I can't install another rom or radio because the rom don't start for 100%, and when I do a hard reset, after the reset at the end of the installation I get the white HTC screen.
What can I do, can I fix this problem?
groot321 said:
I have also this problem, but I think it's in the rom, when I installed the rom, everything seems ok, but after a reset, the screenthat I get is the white HTC screen.
After a hard reset it is ok, but after a reset it is the same problem.
Then I thought, i take an older rom, but when I've installed the rom he is automatic installing the cab file's at the end of the installation, and he's going to automatic reset the HD2. After the reset I have the same problem as with the new rom.
So the biggest problem is that I can't install another rom or radio because the rom don't start for 100%, and when I do a hard reset, after the reset at the end of the installation I get the white HTC screen.
What can I do, can I fix this problem?
Click to expand...
Click to collapse
RTFM. These constant posts about white screen hangs are really getting frustrating. Does nobody follow the forum rules of searching any longer? There's nothing wrong with the rom, the user on the other hand I'm not so sure of.
YOUR RADIO VERSION IS WRONG
url_paul said:
I've just been digging through and saw this, I have the 3 colours and USB.
Gonna try and reflash and see what happens.
These forums own!
edit: re-flashing it went the same way, would hang on boot.
I've gona back to using:
_HTC HD2_RUU_Leo_HTC_WWE_1.66.405.2_Radio_Signed_15.30.50.07U_2.06.51.07_Ship
for the moment.
I'll look and see what it is I missed that stopped the energy rom from working as advertised.
Click to expand...
Click to collapse
If you bothered to read even just the last 5 pages of the Energy thread you would have seen probably 20 mentions of the problem. Energy rom won't work with a x.xx.51.xx radio.
It’s bad day for me.
When I flashed Jackos Oldschool ROM(WM6.1_21048_M2.1) last week I used the Task29 tool to format the device, Jackos Oldschool ROM ran fine.
Then yesterday I flashed WM6.5_21903_M2.5 by Ark666 [Rhodium_AF],there was problem, the ok button on the up-right corner of the screen is not working,when you click it,the notifications window comes up,it's like you click on the midddle of the top screen. what's wrong? And it freezes whenever you click on Contacts(People) and HTC Calendar.Cannot use this rom.
Then I flashed WM6.5_21901 Valkyrie FireStorm tr2.5 by agent_47[v6.5],Settings are not working,for example,you click on today setting,it doesn’t response.
These two roms are recent releases,I don’t see anybody post complaint about similar problem,therefore I suspect Task29 is the CAUSE because I formatted device before flashing these two roms.
I even tried flashing a official stock rom,then flashed WM6.5_21901 Valkyrie FireStorm tr2.5 again,the problem still exists.
Do you think Task29 might have damaged my device memory? I have not seen anyone gave a warning about Task29’s potential harm.
I just flashed old rom WM6.5_21889_M2.5 by dotcompt [DeepShining v12 RC] which I used before, thank god,have not seen problem.
I am worried my device memory has been damaged,gurus and everyone, pls have an assessment on my situation, I don’t hope it’s Task29 that bring this.
Thanks
Before flashed WM6.5, have u done task29 again? Every changing ROM u should do task29. Mine is just fine.
Personally I never had any issues with Task29. The forum is full of people who have used it with success. Try flashing Task29 again and then flash a Stock ROM to see if that will get you back on track. Good luck.
Sergio76 took Task29 apart and determined that it can cause NO DAMAGE to your phone. All the application does is write a 'dummy' ROM to memory setting all memory addresses to 0 (zero). It is not a true format as it doesn't set memory maps or similar, it just sets everything to Zero.
Russ
TASK 29 Does NOT harm the device its jusk like flashing a black. some of the issues you descrived could of been due to a bad download/ downloads maybe on the task29 or ROMs or maybe something else.. but if you feel Task29 is no working for you just flash the stock ROM before flashing a custom ROM
Russ741 said:
Sergio76 took Task29 apart and determined that it can cause NO DAMAGE to your phone. All the application does is write a 'dummy' ROM to memory setting all memory addresses to 0 (zero). It is not a true format as it doesn't set memory maps or similar, it just sets everything to Zero.
Russ
Click to expand...
Click to collapse
Hi Segio,Russ,thank you taking time to investigate this. if Task29 is not the cause,then there must be something wrong with these two roms,I am wondering anyone tried the following two roms:
WM6.5_21903_M2.5 by Ark666 [Rhodium_AF]
http://htcpedia.com/Rhodium-AF-manila-2-5-VX3/soft/htc-rhodium-rom.html?page=1
WM6.5_21901 Valkyrie FireStorm tr2.5 by agent_47[v6.5]
http://forum.xda-developers.com/showthread.php?t=569507
I have posted the problem in rom makers' threads,hope they can give some thought.
WM6.5_21903_M2.5 by Ark666 [Rhodium_AF]:
http://htcpedia.com/Rhodium-AF-manila-2-5-VX3/soft/htc-rhodium-rom.html?c_page=11#comments
WM6.5_21901 Valkyrie FireStorm tr2.5 by agent_47[v6.5]:
http://forum.xda-developers.com/showthread.php?p=6439578&posted=1#post6439578
bmw2320 said:
Before flashed WM6.5, have u done task29 again? Every changing ROM u should do task29. Mine is just fine.
Click to expand...
Click to collapse
what do you mean? do you mean we cannot do Task29 twice before flashing a rom?
No No I didnt format twice.
I formatted the device once then flashed Jackos Oldschool ROM(WM6.1_21048_M2.1),it's fine.
I formatted the device once then flashed WM6.5_21903_M2.5 by Ark666 [Rhodium_AF],it's NOT fine.
I formatted the device once then flashed WM6.5_21901 Valkyrie FireStorm tr2.5 by agent_47[v6.5],it's NOT fine.
Now i think my experience is clear to you.
Dunno it did for me...
I don't know if it is true that it will do harm or if my issue is repeatable...
I have been flashing ROMs for years on my Titan and Rhodium and never had any reason to do something like Task29...
One of my regular ROMs is MightyROM. I do not understand the reasoning but in January Mike recommended flashing back to stock then to his newest ROM. So I did it because he said to. Mine is not to question Chef.
So again flashing through ROMs and last month Mike said to run Task29 and completely empty the ROM before installing his new one. So I did...
All I could get was the black screen that says "TouchPro 2" in white.
I tried everything. Posted in forums. Research. Finally I called Verizon Support. Nothing could get me into the bootloader... So fortunately Verizon sent me out a "like new" handset.
Since getting the new handset I have flashed MightyROM, Energy, BharS, Mr.X, and others looking for the best ROM for me for this time. I have had no issues ever in flashing ROMs on multiple devices that I don't know why Task29 would ever be necessary.
nokiadashi, i would assume since your using recent roms that your falling in to the trap of early adopters, buggy roms.
MHatter469, thats what its supposed to do, you use the cdma version for verizon. after you task29 connect your phone to your computer hold the volume down button while pressing the reset button at the same time. after you press the reset button keep holding the volume down until a red,blue green, white screen shows up. thats the boot loader. From there flash your rom like you always have
ive used task29 once to flash a rom to my device and thats when i flashed it from the stock rom
after that i have never used it before flashing. Am i taking a risk by not doing it?
i usually flash straight from my device because i download the rom through my phone and extract and flash making use of my computer unecessary instead of fighting with windows7
a similar question has probably already been posted
i have a tmobile hd2
i successfully hardspl to it
i flashed the energy reference rom
then i realized that i needed to use the task29 tool before
i flash any rom... did that, hard resetted, and then tried flashing again (energy referecne) using the sd card method
and i just get stuck on the "NRG" screen
tried the other custom ruu method getting the same results
using the radio 2.07.50.27
i put back the regular spl to flash a stock rom but still no luck
i know the phone isn't bricked i can get to boot loader, hard reset
any help would be much appreciated
Thanks in advance!
Thanks!
lilguy227 said:
a similar question has probably already been posted
i have a tmobile hd2
i successfully hardspl to it
i flashed the energy reference rom
then i realized that i needed to use the task29 tool before
i flash any rom... did that, hard resetted, and then tried flashing again (energy referecne) using the sd card method
and i just get stuck on the "NRG" screen
tried the other custom ruu method getting the same results
using the radio 2.07.50.27
i put back the regular spl to flash a stock rom but still no luck
i know the phone isn't bricked i can get to boot loader, hard reset
any help would be much appreciated
Thanks in advance!
Thanks!
Click to expand...
Click to collapse
ok as from my knowledge you dont necessarily need to do task29 if its ur first time flashing (cuz i didnt and i got very good results) so i think u messed up in tht part.. but its ok, now you prolly want to first --> do a task29 again... second ---> get the nrg rom and flash it.... third -->get a radio of 2.10 or higher and flash tht....and just to play safe flash everything using custom ruu (i got better results using them...just saying)... also when u do each flash and its suspenseful dont boot up the phone, just take out the battery and back into bootloader.
hope this helps... report back lol
^thanks man
Okay so heres how it goes, my phone is def not bricked
custom ruu has only worked once for me
now whenever i try to use it it always gets stuck at 8%
i found that if i flash it at night and hard reset. wait til morning and turn on the phone
then it loads past the nrg screen and into the OS.
i'm currently trying to get it back to stock and i downloaded the tmobile update
but it doesnt seem to work, it also keeps stopping at 8%
i disable the anti virus stuff and i plug it in to the back of my computer
sounds like a defect
sorry to bust your bubble bro but it sounds like you got a classic case of a defective leo, i too did the same steps you did and it turns out my main board wasn't any good and the phone kept overheating, turns out when flashing custom roms they tend to put more pressure on the snapdragon then a regular stock t mobile rom. i know this sounds crazy but i believe it to be true, so with that said you got two options, one get back to t mobile customer care and get a replacement. or do what i did and find a repair shop and let them know that your leo either needs a new mainbaord or a new heatskin like mines did, it cost me 80 dollars which wasnt bad since my leo was a gift and i couldnt give it back to t mobile... hope that helps in some way
p.s. sorry for the edit but if you cant do either of those of what i suggested, try this get yourself a nice icepack nthe size of your phone and mount the leo on top of it whenever your using it, so that sucker wont overheat. once again i hope i helped
I have a Tmobile LEO1024 flashed with Coutella's release of Android right when it came out. Also, I have SPL-2.08.HSPL on it and MAGDLR 1.11 on it. So far, I used this verison of Android for a while and I had really not any quarrels except the fact that it freezes on charging when the phone is off meaning that it will not turn off its red charging light when I unplug it from the wall. Anyways, I am just wondering could someone tell me what a good stable, relatively non-battery hog verison of Android Gingerbread for NAND would be?
Also, could someone explain what is CWM? Is this another way of flashing the phone instead of using the DTF flasher?
I apologize if this thread repetitive to other threads but I've been away for some time from flashing my phone and I'd like to know what changed.
CWM is essentially a way to flash or upgrade to new software, without the need for a computer. You simply download the zip of the build onto your sd card, and flash it through CWM. They have guides on how to so i shall not go in depth.
I wouldn't know of any gingerbread builds that are good. However all of them are probably good/liked. Else users wouldn't use them, no? Or post feedback.
The freezing whilst charging when the phone is off is a bug of MAGLDR. v1.1. You shoudl upgrade to MAGLDR v1.13, which whilst doesn't freeze when the phone is off, it will turn your phone on. Also try not to pull out your battery to restart your phone, for it might mess up the pins, and to never let your phone run out of battery or you might end up having to buy a new battery.
Note upgrading MAGLDR does not erase your android build, but installing CWM will erase your android build.
try magldr 113 and flash dft's gingerbread. i rocked that for a month with no problems at all except wfi tethering now working but for me thats not a problem
Thanks guys I'll update my MAGDLR for now. I really don't see much of a incentive to really update at the moment other than MAGDLR. Thanks again guys. I think i'll wait it out a little more for the Gingerbread builds to become optimizied and more stable.
All of the gingerbread rom's I've tried have been stable. Try a CM7 one. You're bound to love it.
You mean CyangenMod right? I was thinking about trying that but I really did not know what it was just knew that it was cool. Got perhaps a favorite that I could try that features CM7? Also, how's the battery life especially in standby?
More trouble in paradise. I updated to MAGDLR 1.13 as people said would solve my charging freeze issues but now it turned into when I wanna charge the phone while it is off it just turns on when I plug in my charger. =/
Unfortunately it is normal behaviour of magdlr 1.13.
Ah geez, I forgot to read that part. That kinda sucks.
Am using 1.13, but this issue is still happening... Maybe a future release will fix it?
I'm sorry i know it's against the rules to be starting a new thread but it's been a week i've been asking for help and no one noticed. This is just a try to come noticed.
I installed task 29 on my blackstone. I had olinex 1.56 installed and later did the task29 with radio 1.13, 1.14 and 1.17 After successfully doing it i went on step 2 that is installing a clean rom. I tried these roms
blackSTONEhengeHyPerSlim_4_1
RUU_TOUCH_HD_MARYONE_23148_WWE_191110
WWE_1.56.405.1_Radio_52.62.25.Shipped ROm
RUU_BlackStone_HTC_WWE_1.56.405.1_Radio_52.62.25.34_1.13.25.24_Ship(3)
They get installed but after i store the contacts and everything it gets stuck if kept for like half an hr. The screen doesn't respond but power button and the volume button works.
I took my phone to a repair center and they couldn't fix it. So please help me i've just got only one phone.
I don't mean to offend any moderators by this but i'm just asking for your help. Thank You
Try reinstalling stock ROM after Task 29.
Restore ONLY contacts, and then try using device for several days.
DO NOT install any other software!!!
If it works, then problem is in some data or software you're restoring.
If not, restore original SPL and original ROM and try again.
If it does not work... and service can not help you... then sorry...
Hello i did reinstall the stock rom after task 29 and i was using pimbackup for restoring but that freezed my phone so i installed the stock rom again and thought of not using it. Did that but nothing much helped.
I hope believe these are the correct shipped roms
WWE_1.56.405.1_Radio_52.62.25.Shipped ROm
RUU_BlackStone_HTC_WWE_1.56.405.1_Radio_52.62.25.3 4_1.13.25.24_Ship(3)
Everything on xda has worked like wonders for me. Be it android on any other rom but right after task29 nothing seems to be working on my phone.
One thing i've noticed after installing any rom after task29 is if i get to the bootloader it gets me to a 1 sec white screen saying no image found. I hope what's causing a problem.
Do you understand WHAT Task 29 is?
It formats the partition drive of your device where the ROM resides. Meaning, it wipes any data regarding ROM.
So of course it would say "No image found".
I don't know which ROM is stock for your device. Try to update ROM via HTC site.
If lucky, it will suggest / let you find adequate ROM.
For my device it's 1.56.407.2 (German)!
If unlucky, it will say "Not supported" or something like that - then go for Orange 1.59.61.2 ROM.
And you might try one 1.5x ROM flash WITHOUT Task 29...
Just try installing stock ROM by stock RUU with USB cable. It will format data for you so you do not need any task 29 before flashing. If it doesn't work, try NOT restoring your contacts.
Thanks will do it and keep yu updated with it..
simplistian said:
Just try installing stock ROM by stock RUU with USB cable. It will format data for you so you do not need any task 29 before flashing. If it doesn't work, try NOT restoring your contacts.
Click to expand...
Click to collapse
Thanks i tried installing the stock rom like you told me but then got stuck on the screen alignment screen. I later installed blackSTONEhengeHyPerSlim_4_1 and now it's responding to every touch. Thanks alot. I hope this stays like this and yes instead of restoring i forwarded all the contacts through bluetooth. Owe you a BiiiiiiiiiiiiG thanks..
Too soon to be happy as same again..I don't think there should be a problem with touch as it works fine for first 1hr but right after something gets stored by something i mean contacts it stops reponding after sometime. The volume and power button work all fine. I can't make out the problem. Any ideas or suggestions. Shall i make a video and post ??
FIRST you have to make it work with factory settings - stock SPL and stock ROM.
After that flash what you like...
I think you have to follow Bodisson's suggestion, do everything as stock and retest without restoring anything. If it still failed...... you should have it repaired
Good luck!!
I had a very bad flash when I first tried Cloudy 0.7.
Unstable and freezing clock in TouchFLO (but NOT system clock!), crashing programs, very slow satelite lock with radio 1.17 on, sudden autolocking/unlocking...
So I did Task29, put on stock ROM (latest German 6.1), after that latest Orange to get newer radio, and after that Cloudy's 0.7.
Now I'm happy so far...
And I'll stick with radio 1.14 for now since it uses a bit less battery than 1.17...
Bodisson said:
I had a very bad flash when I first tried Cloudy 0.7.
Unstable and freezing clock in TouchFLO (but NOT system clock!), crashing programs, very slow satelite lock with radio 1.17 on, sudden autolocking/unlocking...
So I did Task29, put on stock ROM (latest German 6.1), after that latest Orange to get newer radio, and after that Cloudy's 0.7.
Now I'm happy so far...
And I'll stick with radio 1.14 for now since it uses a bit less battery than 1.17...
Click to expand...
Click to collapse
Glad to see somebody researching things out and settling on a radio he prefers due to performance rather than those just going for latest
I totally agree with spartan on this one. It's better to stick with old one's for performance rather than having problems with the latest one's. My device is working better than before but it does get stuck. I'm using stock rom with 6.1 and want to switch to 6.5 so looking for some compatible 6.5 rom with radio 1.14 maybe
Bodisson can you tell me all what you're using bro so that i can tr it on with my device.
kulwant said:
I totally agree with spartan on this one. It's better to stick with old one's for performance rather than having problems with the latest one's. My device is working better than before but it does get stuck. I'm using stock rom with 6.1 and want to switch to 6.5 so looking for some compatible 6.5 rom with radio 1.14 maybe
Bodisson can you tell me all what you're using bro so that i can tr it on with my device.
Click to expand...
Click to collapse
All rom's should work with each radio to be honest. Glad your device is working better, though still a little baffled why you're still having difficulties
EDIT - You are on a wm6.1 rom. Is the rom based on 1.56+, if not you may need to revert to HSPL 1.14
I know it got me bedazzled as well as i've flashed couple of times before but never faced any such difficulties. I even tried android on my phone and everything worked like charm. RUU_BlackStone_HTC_WWE_1.56.405.1_Radio_52.62.25.34_1.13.25.24_Ship is what i'm using at the moment. I did try to flash it again with a 6.5 version rom but still gets stuck. The phone does get stuck once in a while if it is kept unused for a while so don't exactly know how to go on about it.
P.S: I know how hard it is to control things as an admin as i myself run a group. Photography in my case. Cheers
kulwant said:
I know it got me bedazzled as well as i've flashed couple of times before but never faced any such difficulties. I even tried android on my phone and everything worked like charm. RUU_BlackStone_HTC_WWE_1.56.405.1_Radio_52.62.25.34_1.13.25.24_Ship is what i'm using at the moment. I did try to flash it again with a 6.5 version rom but still gets stuck. The phone does get stuck once in a while if it is kept unused for a while so don't exactly know how to go on about it.
P.S: I know how hard it is to control things as an admin as i myself run a group. Photography in my case. Cheers
Click to expand...
Click to collapse
I'm baffled but still want to get to the bottom of your issue and would appreciate any help from other members who may have idea's on how to solve your issue. From what I've read everything you have done is correct, but I don't like being stumped!!
If we start from the start, we may get to the bottom of this........
Ok it all started when i tried installing task 29. I flashed my blackSTONEhengeHyPerSlim_4_1 rom thinking task 29 will work awesomely fast with some newer version as it'll get installed as the default rom.
My phone started freezing like anything right after i flashed it with task 29. Right now my device is running on 1.56.405.1(43972) WWE and 1.13.25.24 rom and freezes again once in a while.
Just waiting for some miracle to make it work fine again.
kulwant said:
Ok it all started when i tried installing task 29. I flashed my blackSTONEhengeHyPerSlim_4_1 rom thinking task 29 will work awesomely fast with some newer version as it'll get installed as the default rom.
My phone started freezing like anything right after i flashed it with task 29. Right now my device is running on 1.56.405.1(43972) WWE and 1.13.25.24 rom and freezes again once in a while.
Just waiting for some miracle to make it work fine again.
Click to expand...
Click to collapse
Well as you know a T29 formats device so you need to flash a rom or you'll be stuck at boot screen. Before you do a T29 it states you must have HSPL on your device first. Now from what I've read you did have HSPL on first and your T29 worked as you where stuck at boot screen afterwards.
I'm assuming you turned device off, booted into bootloader then flashed youir rom (blackSTONEhengeHyPerSlim_4_1) which is based on 1.56+ as was your HSPL.
This all seems correct so I'm not sure what went wrong.
Is above all correct?
Did you try a T29 again and flash different rom or did you just flash different rom over existing?
I did task 29 on blackSTONEhengeHyPerSlim_4_1 and tried installing RUU_TOUCH_HD_MARYONE_23148_WWE_191110 in this process i started task 29 first and flashed it with radio 1.14 by placing the radio and task29 in same folder. Once done it got stuck with windows mobility. After that i restarted on bootloader once again and flashed it with RUU_TOUCH_HD_MARYONE_23148_WWE_191110 . It does get installed but then freezes on configuring device for first time use and then freezes big time on the screen for alignment. I had 1.56 installed before flashing with task 29. If the whole thing bypasses the align screen the rom will keep freezing big time.
That's been the whole issue.
kulwant said:
I did task 29 on blackSTONEhengeHyPerSlim_4_1 and tried installing RUU_TOUCH_HD_MARYONE_23148_WWE_191110 in this process i started task 29 first and flashed it with radio 1.14 by placing the radio and task29 in same folder. Once done it got stuck with windows mobility. After that i restarted on bootloader once again and flashed it with RUU_TOUCH_HD_MARYONE_23148_WWE_191110 . It does get installed but then freezes on configuring device for first time use and then freezes big time on the screen for alignment. I had 1.56 installed before flashing with task 29. If the whole thing bypasses the align screen the rom will keep freezing big time.
That's been the whole issue.
Click to expand...
Click to collapse
Right, I never put any files in same folder as it only confuses flashing process and can cause issues. I.e. put T29 in its own folder, radio 1.14 in its own folder and then rom in another folder.
Do a T29 and when its complete, I.e. stuck in smart mobility screen. Then you take out battery to turn phone off. After this put phone into bootloader and flash rom. Then flash radio after it as a lot of roms have a radio file included
...........................
Sent from the improved version of Tapatalk, better known as Forum Runner