Related
Hi Folks
Well, here it is, ported from what I did for the Polaris basically... I find it's a nice solution as it works by flashing your device with a patched radio and changing stuff properly, anyway...
download and run the EXE, follow the instructions.
bear in mind if you already have Hard-SPL on your device you can skip *straight* to Step 2.
and remember the golden rule:
YOUR DEVICE MUST BE IN CE AND SYNCED BEFORE RUNNING EACH STEP.
Download Here or Download Here
UPDATE: now version v2.0 - Model ID error fixed, it WORKS.
if and when you get success, POST!
PS: If you try to sell this, I will find you, kill you, and sell your ****ing testicles on eBay
Yes, apologies, my error, new version uploaded
So what is the status now?
I found this solution does not work on all of devices. But my solution is as follows.
Run KaiserUnlocker.exe
1. I started with the Step 1. The upper button of total 3.
2. Go through the menus and accept everything.
3. You get TRI-COLOR screen on your device and a few seconds later you get the USB label.
4. After some time you get a communication error Message. DON'T RESET YOUR MOBILE DEVICE. DON'T TOUCH IT.
5. Press Exit to quit KaiserUnlocker.exe on your Desktop machine.
6. Unplug and replug the USB cable.
7. Start the KaiserUnlocker.exe again and wait a little bit.
8. Your mobile device (AT&T Tilt) suddenly alive again. The progressbar shows up and you're from 0% to 100% in a few seconds. Wait a little bit and then you get the message the process is finished.
Now I don't know what to do with step 2 and 3. Should I perform them or not. Hmm?
What I would like to do is just to update from AT&T Tilt ROM to original HTC TyTN II ROM
AS I said before.
REDOWNLOAD IT.
I just tested the flash on my Kaiser, it's fine, no pissing Model ID error at all.
however, to avoid any confusion, download AGAIN and this time you'll find that the version in the debug output is changed to v2.0
so if you don't see v2.0, you don't have the new one
Oh I see you changed the version now. At the time I downloaded it and wrote my first message it was just V1. There was no V2. But I can't test it now because I already have the ROM patched.
And I didn't get the ModelID error. It was a connection error 260.
I think it's just some guys of you are lucky to have a device that doesn't get the white screen when using hardspl and it doesn't stop on tri-colors or the progressbar at 0%.
actually, it's steps 2 and 3 that I care about, having a patched ROM is irrelevant.
step 2 and 3 allow you to sim/CID unlock
Mirror:
Kaiser Unlocker v2.0
FTP Problems!
Hi everybody,
Our provider has notified us of the fact that our ftp server has appeared in a list of compromised FTP servers which are known to host malware associated with attacks on banks and banking infrastructure. We have been requested to secure our systems. Since we realize it would cause serious problems to some if not most of our users if we we're to close it down immediately or change the password in the next 5 minutes we hope you can all live with the following arrangement:
We will close down the ftp server Monday the 9th of march on 09.00 CET. You have until then to download anything from our ftp server you (urgently) need, especially if you host software of which you don't have a back-up on our ftp it's important to download it asap. After closing down our server upcoming Monday we will remove all malware and start restructuring our server, implementing a new user structure, this does mean our server will be offline for a while and we cannot assure you no data will be lost.
If you have space available to host your own software please do so, if you have space available for those who do not have their own space please let it be known by posting a reply to this post. Our apologies for any inconvenience this will cause, but we hope to be able to serve you with a better ftp server as soon as possible.
Best regards,
Flar
Site admin.
Click to expand...
Click to collapse
Just to be safe!
Thanx Olipro
Sorry for asking, what do you mean by "your device must be in CE"?
Olipro said:
AS I said before.
REDOWNLOAD IT.
I just tested the flash on my Kaiser, it's fine, no pissing Model ID error at all.
however, to avoid any confusion, download AGAIN and this time you'll find that the version in the debug output is changed to v2.0
so if you don't see v2.0, you don't have the new one
Click to expand...
Click to collapse
I did re-download after you said it didn't work. I must have downloaded it before it was fully uploaded. I did see the V2.0 NOw...this time no errors.
Thanks again Works perfect now. Thank again.
It Works!
This is awesome. I was trying with Jocky's unlocker for couple of hours. No luck.
Gave a try to this tool. Unlocked first time. Now, I got to check my phone with a different provider SIM.
Thank you so much!
Done, but I saw that you have change the radio version to 1.70.xxx. What radio is this?
Does this mean that the unklocker installs Hard SPL permanently - so future rom flashes are possible? what does device in CE mode mean?
Penske MB said:
Done, but I saw that you have change the radio version to 1.70.xxx. What radio is this?
Click to expand...
Click to collapse
it's 1.58.something, i forget the rest
FTP will close today.!!!!!!!!!!!!!!!!
I try to download and uploade to mediafire
Midget Edit: Mirror removed, new version.
doesn't matter, I'm updating the FTP link in a second or two with the new one
Active sysnc
Hi Olipro,
Thanks for all the hard work.
When I try to run the step 1, it keeps on disconneting the active sysnc. Am I doing something incorrectly?
Cheers
Shan
elmoono said:
Does this mean that the unklocker installs Hard SPL permanently - so future rom flashes are possible? what does device in CE mode mean?
Click to expand...
Click to collapse
These were my steps,
1. Identified my AT&T radio ROM & downloaded that from XDA website as a backup. Pick from here
2. Ran Pof's HardSPL Link
3. Ran Jocky's SuperCID & Security Unlocker Link
4. Installed Dutty's Official WM6.1.2.19199 Full Version Link
5. Installed Radio ROM 1.64.06.04 Download
6. Installed .NET Framework 2.0 on my Windows XP SP2 from Microsoft website.
7. Ran OliPro's Kaiser SIM/CID Unlocker. Followed just step 2 & 3 since I had already installed HardSPL.
8. Installed Radio ROM 1.64.06.04 to get my ringtone & HSDPA connection.
May be my steps 3 ~ 5 were over kill but that was just me. If you would like to skip 3 ~5 make sure you have WM 6.1 installed also remember to patch your original radio on step 8.
All the above steps does not need a strange SIM. I am yet to pop in a different carrier SIM to confirm about my Tilt Unlock Status. However, after the above steps, I found "Kaiser Unlock.exe" under my Tilt root folder. I ran that from phone, clicked on check SIM Status, came up as "You are already SIM Unlocked"
Hope this helps.
when you run step 3, just query what simlocks are active
Worked on my AT&T Tilt!
Not sure about step one already had SPL done with Whitescreen Fix
I will try it monday when my friend brings his tilt over to get it unlocked.
I did have to install a 6.1 ROM (I used Dutty's Official) between steps 2 and 3, had a blank screen, using the att rom -bloatware.
Attached you find all you need to flash cooked ROMs on your Ozone (Cedar).
The sspl/hardspl are confirmed to work fine on the HTC Cedar platform (Ozone).
It will not work on the HTC Maple platform (Dash3G). Running this sspl on a Dash3G will definitely brick it. Also the HTC Willow platform (SNAP S511, Sprint) is not supported. For the Dash3G I have already developed a sspl/hardspl. Users of the S511 have to wait until I feel motivated ..
The packages contains a SSPL, HardSPL, patched ROM updater and the original Ozone SPL. The package is based on SPL v0.39
Instructions:
1. remove SD and SIM cards (don't forget otherwise the sspl is likely not to work!!)
2. connect your device to your pc with a USB cable and wait until it is synced
3. extract the file "Ozone HardSPL by JockyW.zip" and execute "auto.bat"
4. follow all instructions given on screen: first the sspl is copied to the device and executed. You must confirm running JumpSPL on the device: first time you must click Yes to allow it to run, you also must click the trackball to continue execution of JumpSPL. The device display will turn dark and after that the romupdate tool will install the hardspl on your device. (the identification string in the tri-color bootloader screen is "0.39.Hard")
5. to test the sspl and the hardspl you can flash the attached splash.nbh
Once the HardSPL is installed on your device you can flash any Ozone cooked or original ROM.
Have fun,
JockyW
PS: Moderators please make this a sticky. Thanks.
Awesome work JockyW.
Awesome, thanks for your hard work.
Now all we need are some 6.5 roms!
4. follow all instructions given on screen: first the sspl is copied to the device and executed. You must confirm running JumpSPL on the device: first time you must click Yes to allow it to run, you also must click the trackball to continue execution of JumpSPL. The device display will turn dark and after that the romupdate tool will install the hardspl on your device. (the identification string in the tri-color bootloader screen is "0.39.Hard")
Click to expand...
Click to collapse
Um... so most of this worked fine, and the screen is dark, and a generic htc driver got auto installed... and the Rom Utility popped up on my screen... But how do I get it to connect to activesync like this?
After my phone rebooted completely (following the ROM utility completing), I just re-enabled Allow USB connections and it seems to work fine.
No, so the rom update tool doesnt complete because ActiveSync doesnt work after the screen turns black...
Edit: and Im using XP (noticed ur not from the thumbnail...) idk if that matters or anything
I'm having some difficulties of my own. I'm running Windows 7 RC x64 with WMDC 6.1.6965.
I started by running the sspl.bat (with USB enabled in WMDC); the SPL app came up on my device's screen, I tapped ok, and the device screen went black w/ solid black pixels. The only way of rebooting it is yanking the battery. The OS loads fine after that.
Later I thought it had run sucessfully so I ran auto.bat. The JumpSPL steps ran fine (with USB enabled still) but it failed at step 4 when the ROM tried to flash (obv. because USB was still enabled).
Strange thing is, when USB is disabled and I run auto.bat, the device is unable to connect in steps 1-3. I canceled all those steps and then the ROM flasher starts, makes a connection, and starts the flash but won't go past 0%. The screen is still black because after step 3 the SPL flashes (or attempts to.)
I later put the device in bootloader manually (with the colorful bars) and ran the ROM flasher by itself. It runs but again, gets stuck at 0% on both the device and the PC. After a while a 262: update error pops up. This must be because the SPL is still locked? The OS boots fine after a battery pull.
Strange. Any advice would be welcome.
forgot to remove my SIM card! Gonna try again, give me a few minutes
no, same problems. :sigh:
The bootloader is still locked in 0.39.0000, confirmed.
EDIT: I'm pretty sure all my problems are coming from x64 drivers. I'm going to try this again in Windows XP Mode. Congrads everyone who's succesfully flashed! Good work guys!
businesschild said:
forgot to remove my SIM card! Gonna try again, give me a few minutes
Click to expand...
Click to collapse
businesschild said:
I'm having some difficulties of my own. I'm running Windows 7 RC x64 with WMDC 6.1.6965.
I started by running the sspl.bat (with USB enabled in WMDC); the SPL app came up on my device's screen, I tapped ok, and the device screen went black w/ solid black pixels. The only way of rebooting it is yanking the battery. The OS loads fine after that.
Later I thought it had run sucessfully so I ran auto.bat. The JumpSPL steps ran fine (with USB enabled still) but it failed at step 4 when the ROM tried to flash (obv. because USB was still enabled).
Strange thing is, when USB is disabled and I run auto.bat, the device is unable to connect in steps 1-3. I canceled all those steps and then the ROM flasher starts, makes a connection, and starts the flash but won't go past 0%. The screen is still black because after step 3 the SPL flashes (or attempts to.)
I later put the device in bootloader manually (with the colorful bars) and ran the ROM flasher by itself. It runs but again, gets stuck at 0% on both the device and the PC. After a while a 262: update error pops up. This must be because the SPL is still locked? The OS boots fine after a battery pull.
Strange. Any advice would be welcome.
Click to expand...
Click to collapse
businesschild said:
no, same problems. :sigh:
Click to expand...
Click to collapse
businesschild said:
The bootloader is still locked in 0.39.0000, confirmed.
Click to expand...
Click to collapse
Instead of replying to yourself, please use the edit button next time.
Anyways, if you run auto.bat, disable USB Connections after the screen turns black via ActiveSync. In your device manager (with the screen still black) look at your USB Devices. You should see a entry called HTC USB Sync. If you see that continue to flash. Seeing HTC USB Sync is a key step in this whole process.
Please read the testing/development thread for some good solid help. A bunch of us ran into the same issue you did. If you read all 4 pages you should be able to troubleshoot your problem: http://forum.xda-developers.com/showthread.php?t=550628
computerpro3 said:
Awesome, thanks for your hard work.
Now all we need are some 6.5 roms!
Click to expand...
Click to collapse
Working on it! Lots of work! Gonna grab my Ozone later today and cook you guys up some treats to taste test! Haha. Ready??
ookba said:
Working on it! Lots of work! Gonna grab my Ozone later today and cook you guys up some treats to taste test! Haha. Ready??
Click to expand...
Click to collapse
I'm a new member here and I can't believe how much hard work you guys put in for free. I am pretty broke right now but at some point in the next week or so I'm going send a small donation to both you and jockyw....won't be much as I really can't afford it but should buy you some decent beer at least...
computerpro3 said:
I'm a new member here and I can't believe how much hard work you guys put in for free. I am pretty broke right now but at some point in the next week or so I'm going send a small donation to both you and jockyw....won't be much as I really can't afford it but should buy you some decent beer at least...
Click to expand...
Click to collapse
HERE HERE!
The stock ozone rom is crap, I would love to cook my own ROM!
BTW hardspl successfully flashed first try on my device. Totally painless. Excellent job.
Anyone with a Telus SNAP try this?
ariesq said:
Anyone with a Telus SNAP try this?
Click to expand...
Click to collapse
I think the Telus SNAP is a CEDAR as well. Uses the same CDMA network as Verizon. Dump your SPL and post it for JockyW to examine and give the tumbs up.
Also, dump your RAW files, upload and post in this thread if you can.
http://forum.xda-developers.com/showthread.php?t=540586
Also guys, we gotta hook up JockyW with some donations. He worked his ASS off to build this and we have to show some gratitude. If you want him to continue to support us, we have to show him some love.
ookba said:
Also guys, we gotta hook up JockyW with some donations. He worked his ASS off to build this and we have to show some gratitude. If you want him to continue to support us, we have to show him some love.
Click to expand...
Click to collapse
I agree. Just sent him a small donation. You're next ookba, but will have to wait until next paycheck.
Update: Small donation sent to you as well ookba. I'll just have to skip lunch tomorrow
P
How sure are you that Ozone is Cedar?
RUU_Chief_W_WM65_VERIZON_WWE_2.10.605.1T_Radio_612522_1.71.00WV_NV_MFG_VZW
looks like a chief to me, but I could be wrong, I would like to release a 6.5 kernal, but dont want to have wrong device.
First of all please be gentle! I am a complete novice and this is my first post. I have a Touch Pro on a Vodafone contract. I downloaded the recent ROM software upgrade from the Vodafone web site and began the transfer to my phone having followed all the advice. However, the download got stuck at 12% and no matter how many times I start over again it will not go past that point. Worst still the phone is now locked on a red/green/blue/white screen with the message "Upgrade ROM code error Please try again". the error message on the Vodafone software download is No 302. I have tried Vodafone technical help but as I was due for a new phone anyway they have sent me a Touch Pro 2 but don't seem to want to help me resolving the problem with my "old" phone. It is only 5 months old (replacement insurance phone) and in good condition but useless if it can't be made to work.
Can anyone help with simple instructions on how to download a ROM that will work. If not does anyone want to make me an offer for the phone? Currently locked on Vodafone but I am sure you guys out there have the skill to resolve that one.
Many thanks,
Hollybeau
So, they aren't asking you to send it back, I take it? If that's the case, then the first thing I would try would be to flash with the stock rom, if you can find it (not the upgrade that quit on you). If that doesn't work, then just try to flash hard spl. If hard spl goes through ok, you're golden and can flash any raphael rom you want. If it doesn't, the phone is probably toast. You got a new one, so just use the old one as artwork.
Thanks Farmer Ted,
Unfortunately I do not know the orginal stock ROM. It is not on the Vodafone web site and the HTC site keeps telling me that all the likely candidates are "not suitable" ( I assume this is beacuse it is some sort of Vodafone variant). I am afraid that "flash hardspl" means nothing to me - I told you I was a novice! Can you direct me to what and where please.
What bugs me is that here is a phone worth £200? but for a problem caused by Vodafone's buggy software upgrade.
Hollybeau
Start Here.
Best way to find everything you want to know about flashing ROMs.
Lol.
Hard SPL is a bootloader that allows you to flash any rom you want (not just vodaphone). It also has over-write protection, so if you get into the situation you're currently in, the phone won't be bricked. If you can flash it (make sure you flash the gsm version in the raph rom forum), you are fine and dandy.
If you can't find the stock rom online, you may be able to flash the upgraded rom off of your sd card (I believe this will work with a stock rom and stock spl, but am not 100% sure). Re-name the .nbh image file to RAPHIMG.nbh. Format your sd card (1-2 gb works best) to FAT32, and put the image on the root of the card. Go into bootloader (well, you're already there, you may not need to) by holding volume down and soft resetting. Hold vol. down until the tri-color screen appears. At the prompt, press the power button, and let the flash run its course. Soft reset when it says that the update was a success. Let the phone boot up until it gets to the the alignment screen, the hard reset and boot it up.
If you don't have an .nbh file, and instead have a .exe file from vodaphone/htc, then you should be able to extract the contents with either winrar or 7-zip (google) to get at the .nbh image file. I've done this before, and it works fine.
Many thanks to all who have replied. I have fixed the problem. It turns out that it was the download to my PC that was at fault. I downloaded the Vodafone software to my lap top and ran it from there and it has recovered the phone. I now have a spare, and working, Touch Pro. I may try the HardSPL and other ROMS just to use the phone as a test bed. Alternatively, anyone out there want to make me an offer?
Hollybeau
Hollybeau said:
Alternatively, anyone out there want to make me an offer?
Click to expand...
Click to collapse
Ask in market place and you will probably get some takers
Ok, I'm kind of at my wits end. I've already bricked a Sprint Snap, and I'm trying to get HARD to display on my tri-color instead of 0000 before I try ookba's rom again.
But I can't. I've done everything correct. SDA application unlocker - auto.bat from the JockyW thread, JumpSPL and boot Rom Update Utility. Every time it goes to a 100%, but once I reboot and then hold volume down I still get
CEDA200
SPL-0.34.0000
MicroP-Willow#C (LED) v58B.
No luck. I've tried hard resetting my phone with brand new factory settings (my old 6.1 was heavily modded). I've tried XP and Vista. No luck. When I confirm jumpSPL my screen goes black. Then I run RomUpdateUtility while the screen is black. Is that right? Please advise me, I'd love to have 6.5 on my snap.
Please use the correct version of Hard SPL, suitable for your phone!(S 511). Above all use Jump SPL (depending on your SPL version) and follow the prompts in the DOS window. Just press space bar. On your phone, screen will turn black this is NORMAL!Then free to interact in any way with the phone and without disconnecting the phone from the PC will need to run Hard SPL.Again attention, according to your platform (S511).After all this if all is well you should install the favorite ROM .
Good Luck!!!
i have followed these steps
I have started the romupdateutility with the black screen and it completes to a 100 percent. however my tricolor splash screen doesn't change.
Strange ...Something is wrong there.Try on another PC, make sure Active Sync or Windows Mobile Device Center is working properly.But most importantly try another JumpSPL and HardSPL, those you have now may have errors or can be corrupt file.Had happened to me with my old Diamond.
what is supposed to happen?
The .0000 should say .HARD if the flash was successful right? If a phone is HARDSPL then it won't change after a hard reset right? I really can't get this to work... is there a newer jumpspl I should try? Everytime RomUpdateUtility completes with the black screen my phone reboots and nothing has changed
DAMN
I just bricked my second snap by trying a different version of JumpSPL, really really upsetting. I can't believe I did that again, all I wanted was my device to be HardSPL and now its a paperweight. UGHHHH no phone certainly isn't better than stock 6.1... I'm probably done trying to 6.5 this damn thing. I'm going to replace it and never mess with it again. Thank you for trying to help.
Sorry man, really sorry. And I agree with you, 6.5 is nothing better than 6.1 and I think so.I have 6.5 and do not see an obvious improvement or an addition to performance.Perhaps a higher consumption of resources.I think it depends on preference.In your case maybe not everything is lost.Read this very very very carefully: "Flashing and Unbricking your Maple" by Ookba.Even if they refer to Maple, can help you.Good luck!
yay!
After getting a new s511, I attempted this for the third time
Well, It worked like magic. .Hard is now visible on my tri-color screen. SO!
Now I can flash the ROM? Do I just turn my phone on to its homescreen and plug it in to run RomUpdateUtility? Any other precautions I should take?
@Johny, thanks so much man for all of your help i appreciate it.
Yes, theoretically should work without problems now.Turn on the phone then start running RomUpdateUtility. If Hard is visible, you are insured in case of failure to update the ROM. In my case...I did not succeed the first time this.Even if I did HardSPL, I could not install 6.5, an error occurs...All they have resolved JumpSPL.If you have problems post here. Good luck!
Johnny_BV said:
Yes, theoretically should work without problems now.Turn on the phone then start running RomUpdateUtility. If Hard is visible, you are insured in case of failure to update the ROM. In my case...I did not succeed the first time this.Even if I did HardSPL, I could not install 6.5, an error occurs...All they have resolved JumpSPL.If you have problems post here. Good luck!
Click to expand...
Click to collapse
salut Johnny . putem vorbi de telefon?
drc38 said:
salut Johnny . putem vorbi de telefon?
Click to expand...
Click to collapse
Please provide an english translation, since this is a english forum
Device Help
I have a HTC Snap 511 from a Wireless Carrier in Puerto Rico it works just as fine as Sprint's. Actually its the same phone under another carrier. I tried Updating the rom i got lucky it boots 6.5 but i downloaded the wrong rom because its for a GSM phone not CDMA now its asking me for SIM and i can't updated to the one it goes ( that i downloaded sometime later )... Tri-Color Says:
CEDA200
SPL-0.39.0000
MicroP-Willow#C (LED) v 58B
i tried putting the s511 Sprint ROM but says at upgrade communication error.
I think its because im downgrading roms?
CEDA is 2.00.XXXX
WILL is 1.50.XXX
Any comments are aprreciated.
PS-
SIM Failure
The SIM card is missing or is not valid.You can still make emergency calls if your service providers supports it.
--##_- 240x320 Fun! -_##--
Which Un RAR arhivator complete work on this device (Snap S511) ???
I`m test all and not working nothing. WM 6.5 and WM 6.1
Not description for Icons in the SYSTEM(WM 6.5) menu... Baaaaad.
Hello friends, I need your help, to be trying
P4351 upgrade my cable took off from there, it is
nailed to the first screen (not the system starts
OS), just let me enter the Tricolor screen,
I tried many roms (both P4350, P4351 as)
with officials, as cooked, and give me error, with
the original Sell tells me Invalid ID, and the
The rom cooked tells me is corrupted, being that before
allow me to update with any rom.
My IPL is 4.24.0002
My SPL is 4.14.0000
For more information: my phone was bought in Paraguay.
I've tested with the official rom T-Mobile.
Anyone can help me?
thanks.
matuzalen said:
Hello friends, I need your help, to be trying
P4351 upgrade my cable took off from there, it is
nailed to the first screen (not the system starts
OS), just let me enter the Tricolor screen,
I tried many roms (both P4350, P4351 as)
with officials, as cooked, and give me error, with
the original Sell tells me Invalid ID, and the
The rom cooked tells me is corrupted, being that before
allow me to update with any rom.
My IPL is 4.24.0002
My SPL is 4.14.0000
For more information: my phone was bought in Paraguay.
I've tested with the official rom T-Mobile.
Anyone can help me?
thanks.
Click to expand...
Click to collapse
Oki, maybe i can help you.
Did your DROP your phone recently?
cause that's what happened to me, and it broke my camera button. so my device was forced to go to the bootloader screen (aka RGB screen).
mrbayn said:
Oki, maybe i can help you.
Did your DROP your phone recently?
cause that's what happened to me, and it broke my camera button. so my device was forced to go to the bootloader screen (aka RGB screen).
Click to expand...
Click to collapse
No, not been dropped, the problem arose because I took the
cable during the update.
Okay. On the RGB screen plug in your usb and run then run this:
http://www.mediafire.com/?yj1oz2m3mzm
Let me know how it does from here. If this works then i'll guide you the rest of the way.
I have tried with the file that I've been, but still
jumping the same error, ERROR [294] invalid vender ID, the update runs to the 1% and the phone is restarted and returned to the initial state.
Also thank you very much for your help!
First thing - Is your phone a Herald?
Because my last bit of advice was for the Wing..
Try to find your original ROM for your device.
The service provider that you have your cell pone through should have that stock ROM/Update.
Then make sure you're at the RGB screen when running the stock ROM.
Tribulattifather said:
First thing - Is your phone a Herald?
Because my last bit of advice was for the Wing..
Try to find your original ROM for your device.
The service provider that you have your cell pone through should have that stock ROM/Update.
Then make sure you're at the RGB screen when running the stock ROM.
Click to expand...
Click to collapse
Hi friend, my phone is Herald (HERA110), and it's runing on the screen RGB
1) Download THIS.
2) Flash with the above while on the RGB screen.
3) Run the HardSPL package.
4) Get back to RGB screen.
5) Flash any custom ROM for your device
^>^
I tried and nothing happened, I digue giving the same error, and
Phone will not start, and do not know what else to do, because I
the steps you give me the bottom of the letter or even so
does not work. You may no longer serve?