I was flashing my tytn with the new rom with bootloader 1.09 after 8% the usb cord came out and now my tytn is dead its stuck in bootloader mode..spl 1.09...please help
I am also in this boat, except my usb cord didn't fall off, it just stopped updating at 6%.
Connect to the device using mtty and type info 2. If you're CID is corrupt, then you're out of luck just like me.
It seems that the only way to fix this problem is to send the unit back to a service center and get the main board replaced. Unless anyone else has any other ideas. In BL 1.04 you could bypass the CID check but in 1.06 and 1.09 that bug has been fixed.
Great job HTC, you really messed everyone up now, I hope you're ready to start replacing some board on account of your ignorance to create a sufficient backup routine. I guess this means less money of new development and less devices from HTC in the near future.
Because you're in bootloader mode, you might be able to flash the 1.04 bootloader downgrader in; which would then allow you to re-flash any firmware.
Nope, even in boot loader mode I can't go back to 1.04. It doesn't recognize the CID and keeps saying invalid vendor id.
The only possible fix I can see is if someone hacks the hermes and finds a way to cook a rom and not check the CID. Otherwise, it's a full board replacement.
Somehow there has got to be a way to "Bypass" the CID check.
What I was trying to say, if you use the IMEI-CHECK downgrader it will bypass the CID checking enough to get you back down to 1.04?
Yes. Imei-check downgrades your bootloader to 1.04
sn00x said:
Yes. Imei-check downgrades your bootloader to 1.04
Click to expand...
Click to collapse
But to run imei-check unlocker you need a running OS (it needs to transfer files via activesync to the device) and your IMEI should be not screewed while checking it from bootloader. Otherwise it will not work.
I've tried everything possible to get out of bootloader mtty says my cid is corrupt.does anyone know a number for the service center
depends on your country, go into htc website and look at it:
http://www.htc.com
Pof you are correct. The CID is completely corrupt, the radio sectors have a bad record, and the phone can't boot past the windows mobile splash screen. So the only way we can fix this problem, is to hack the flashing of the rom to not check the CID at all. If this can be done, then we're in business.
On another note, I've been seen 1 of these problems arise every day now. Someone either pulls the usb cord or the flashing just crashes.
I think there is a serious enough priority to hack the hermes rom flashing now aside from crossbow. We really need some resources on this so that we don't ever have to go through these problems again.
In the words of Russel Peters (a famous Canadian comedian)... Pof, be a man, do the right thing. Hehehe.
pof said:
But to run imei-check unlocker you need a running OS (it needs to transfer files via activesync to the device) and your IMEI should be not screewed while checking it from bootloader. Otherwise it will not work.
Click to expand...
Click to collapse
But does that "other solution" which can't be posted here anymore bypass that requirement, as it runs through the bootloader and not activesync?
no it doesn't. The update still checks the CID before updating.
And it also needs activesync to transfer the fake bootloader to the device... remember it starts with M3100v3cUnlock.exe too....
Ooh, forgot about that bit .
Related
Please help me!
I screwed my MDA Vario II. I used HTC universal sim unlocker and I haven’t got radio. I know I was a craze.
No GSM, no cid and no imei. The pda is working good.
I vas very happy when I find this site :
http://wiki.xda-developers.com/index.php?pagename=Hermes_UpgradeProblems.
I made this:
USB>
USB>password 0000000000000000
HTCSPass1.CMˆËHTCEUSB>set 1e1
USB>erase a0040000 c80000
HTCST ÚČŇHTCEUSB>erase a0cc0000 c80000
HTCST ÚČŇHTCEUSB>erase a1940000 640000
HTCST ÚČŇHTCEUSB>set 1e 0
USB>
The radio doesn’t work , no GSM, no cid and no imei. The pda is working good.
Please help me
Please can a expert check this!?
I found this with the search option.... can someone check this....
Its written for the Tytn and not for the Vario II, i'm not sure but i thought that the english Vario II has a 1.06 bootloader!! Then you are stuck, beacause the file who degrade your bootloader to 1.04 isnt availleble anymore. Maybe one of the guys here can share it with you?!
======================================================
- Take the battery out of your TyTN and leave it out several minutes
- Disable USB-connection in Active-Sync
- Reboot your Computer
- Replace the battery and put your TyTN in the bootloader
- Try to load the ROM found here:
ftp://xda:[email protected]/RUU120_172125_Qtek_WWE_R11400_Shipping.exe
- Keep trying till you get just past the erasing part, then you will get an error-message and are asked to reset your device with the stylus
- Reset your phone and put it back in the bootloader mode
- Install any Hermes ROM you like, no matter what CID if you have bootloader 1.04
lacika said:
The radio doesn’t work , no GSM, no cid and no imei. The pda is working good.
Click to expand...
Click to collapse
Can you attach a USB monitor capture of what happens when you try to:
a) flash a rom
b) flash a radio rom
Do both things starting from bootloader and with activesync disabled.
Same Problem
I have the same problem
My PDA keeps comming back in the bootloader screen.
When 1 try to update (its a unlockes pda), the upload stops at 1%
Is there a way to erease the PDA ?
Thanks
pimmmm said:
I have the same problem
Click to expand...
Click to collapse
I have the same questions.
Can't do anyithing if you don't attach a USB capture of the process. See this page for instructions: common upgrade problems
smarty77 said:
I found this with the search option.... can someone check this....
Its written for the Tytn and not for the Vario II, i'm not sure but i thought that the english Vario II has a 1.06 bootloader!! Then you are stuck, beacause the file who degrade your bootloader to 1.04 isnt availleble anymore. Maybe one of the guys here can share it with you?!
======================================================
Click to expand...
Click to collapse
HI!
Thank You for your answer. I made yours tip, but not was good.
First I to try smarty77 tip. I used RUU120_172125_Qtek_WWE_R11400_Shipping. Its function. After I’d like rom upgrade. This doesn’t was good (invalid vendor).
Second I to try clearing with mtty.exe.
The situation same, the phone doesn’t work.
Sorry my bad English.
pof said:
Can you attach a USB monitor capture of what happens when you try to:
a) flash a rom
b) flash a radio rom
Do both things starting from bootloader and with activesync disabled.
Click to expand...
Click to collapse
HI!
Thank You for your answer. I made yours tip, but not was good.
First I to try smarty77 tip. I used RUU120_172125_Qtek_WWE_R11400_Shipping. Its function. After I’d like rom upgrade. This doesn’t was good (invalid vendor).
Second I to try clearing with mtty.exe.
The situation same, the phone doesn’t work.
Sorry my bad English.
Just seen your capture but it's not good.. you made a "basic" capture which shows nothing important, please repeat the process again, but this time read point 6:
In the upper part there are two tabs: basic and complete. Click on "Complete".
I cannot help unless I have a complete capture to see the problem.
pof said:
Just seen your capture but it's not good.. you made a "basic" capture which shows nothing important, please repeat the process again, but this time read point 6:
In the upper part there are two tabs: basic and complete. Click on "Complete".
I cannot help unless I have a complete capture to see the problem.
Click to expand...
Click to collapse
HI POF!
Thank you four your help.
It is a new captured files.
Please help me. You are a last chance, for my phones.
Lacika
@lacika:
When checking the seclevel (task 32 bootloader command) your phone replies:
Code:
CID: Wait interpreter timeout.
Level=FF
After that when checking the CID with 'info 2' your phone replies:
Code:
HTCS...?\0.?f..|HTCE
This should be something like T-MOB001 if you have a Vario II from UK, so the CID is screwed.
I can see from the output of 'info 3' that you're running bootloader 1.06.
Then you try to flash the 1.18.255.3 ROM from HTC, which has CID "QTEK_001", you won't be able to flash this image in your device with bootloader 1.06, even if the CID was not screwed you will always get an error (you need bootloader 1.04 to bypass CID checking, and you are in 1.06), the error you're getting from bootloader is:
Code:
CID not allow (255)
As you said you can use the PDA (WinCE boots) what I suggest is buying imei-check unlocker (you need activesync working too for running the imei-check unlocker), because it will downgrade your bootloader to 1.04 and patch your radio... probably it can fix your device, at least it will downgrade your bootloader to 1.04. If after running the unlocker your device doesn't work I suggest that you try to flash a radio ROM, you can find them here:
http://wiki.xda-developers.com/index.php?pagename=Hermes_ExtractedRadioRoms
Let me know how it goes
pof said:
As you said you can use the PDA (WinCE boots) what I suggest is buying imei-check unlocker (you need activesync working too for running the imei-check unlocker), because it will downgrade your bootloader to 1.04 and patch your radio... probably it can fix your device, at least it will downgrade your bootloader to 1.04.
Click to expand...
Click to collapse
Err... I forgot that your IMEI is also screewed, probably imei-check unlocker will not work on your Hermes even if you provide them the right IMEI, because it will not be able to read the IMEI from your phone (will get the wait interpreter timeout too...). anyway... it costs 20GBP, give it a try!
pof said:
@lacika:
As you said you can use the PDA (WinCE boots) what I suggest is buying imei-check unlocker (you need activesync working too for running the imei-check unlocker), because it will downgrade your bootloader to 1.04 and patch your radio... probably it can fix your device, at least it will downgrade your bootloader to 1.04. If after running the unlocker your device doesn't work I suggest that you try to flash a radio ROM, you can find them here:
http://wiki.xda-developers.com/index.php?pagename=Hermes_ExtractedRadioRoms
Let me know how it goes
Click to expand...
Click to collapse
Hi and thanks!
I’ve got one question. I use imei-check unlocker after I’ll got 1.04 bootloader?
Lacika
I tried that with my device before it got sent to service, I brought imei-check unlocker but as my imei was also corrupt it will not work, so I would not waste GDP 20 if you have corrupt imei.
They will not refund either becuase its your problem the imei is corrupt.
lacika said:
I use imei-check unlocker after I’ll got 1.04 bootloader?
Click to expand...
Click to collapse
No, imei-check unlocker will downgrade your bootloader, BUT as shark1 says, it will not work because your IMEI is corrupted and it will not be able to read it.
I guess the best would be to send the unit to the repair centre then...
pof said:
@lacika:
As you said you can use the PDA (WinCE boots) what I suggest is buying imei-check unlocker (you need activesync working too for running the imei-check unlocker), because it will downgrade your bootloader to 1.04 and patch your radio... probably it can fix your device, at least it will downgrade your bootloader to 1.04. If after running the unlocker your device doesn't work I suggest that you try to flash a radio ROM, you can find them here:
http://wiki.xda-developers.com/index.php?pagename=Hermes_ExtractedRadioRoms
Let me know how it goes
Click to expand...
Click to collapse
Hi!
I’ve got a new problem.
I used a M3100v3cUnlock.exe program. This doesen’t read my imei number.
I don’t know how can I flash my bootloader.
Lacika
pof said:
No, imei-check unlocker will downgrade your bootloader, BUT as shark1 says, it will not work because your IMEI is corrupted and it will not be able to read it.
I guess the best would be to send the unit to the repair centre then...
Click to expand...
Click to collapse
I had the same problem! Send it to orange assistance.
lacika said:
I used a M3100v3cUnlock.exe program. This doesen’t read my imei number. I don’t know how can I flash my bootloader.
Click to expand...
Click to collapse
You can't, and your imei is screwed, the unlocker can't check it... so you should better send the unit to the repair centre as suggested.
pof said:
You can't, and your imei is screwed, the unlocker can't check it... so you should better send the unit to the repair centre as suggested.
Click to expand...
Click to collapse
HI!
I’ve got a last question.
It will a new procedure, program, with I can flashing my bootloader.
Lacika
Hi,
I recently had a power cut (yes, a lights off power cut!) that killed my PC half wat through installing the Cingular English CWS__001 1.34.502.1 09/21/06 ?? 1.16.00.00 32.53.7018.01H 14955.2.3.0 ROM onto my SPV 3100.
Now SPV 3100 will boot to the ROM I was running prior to the upgrade but I can't use the telephone. I'm also not able to rerun the upgrade as it got far enough through the process to upgrade my bootloader to 1.06 - therefor rendering me unable to load another ROM.
Before the crash I was using the Imate ROM as below and M3100 was sim unlocked and running on o2 3G
i-mate English CDL__001 1.20.305.3 07/21/06 1.20.305.104 1.07.03.10 32.41.7010.02H 14955.2.3.0 1.04
Please help.
Thanks
If your device is still working ok as a PDA then hopefully it just screwed up the radio update of your device.
Try reflashing the Radio only
Look Here
http://wiki.xda-developers.com/index.php?pagename=Hermes_ExtractedRadioRoms
Post back with results
Regards
S.K
EDIT: Sorry only works on 1.04 bootloader only. Afraid your gonna have to wait for Pof to come up with a 1.06-1.04 workaround
Hi S.K,
Thanks for the info. I have now tried installing the HERM_1.20.31.10_type2_radio_fixed upgrade but unfortunately the radio upgarde crashes also. It all seams to go well, (after using MaUpgradeUt_noID.exe twice) the phone says "Upgrade Radio Stack Please wait" and the progress bar appears on the PC but then after 10 mins I get an ERROR 114: RADIO ROM UPDATE ERROR.
Do you think this might be becuase the last upgarde partly installed bootloader 1.06?
Any other suggestions - I'm desperate to get the hpone on M3100 working again.
Thanks
Read here:
http://wiki.xda-developers.com/index.php?pagename=Hermes_UpgradeProblems
Please post USB monitor capture, otherwise can't help u.
Hi Pof,
Thanks for the offer, I will sort out the usb software on Monday. Are there specific actions that I should try, obvioosly I will usb monior everthing I do but I want to keep it to the point and not waist yr time trailing through huge log files.
Cheers
BTW - I have tried all options of recovery, such as attempting to install the latest radio and trying to install the new rom from an sd card, trying several roms and using imei unlocker - all without any joy.
I think the problem is that I have partially installed radio and bootloader 1.06 so I can't fix the problem.
Thanks again.
@wotthefok:
For me is faster to look at the usb log file, then I exactly know why the upgrade fails, otherwise I have to decode it from your feedback and I can't be really sure. Check the "upgrading problems" page on the wiki, if none of the steps there seems to fix your problem, post USB monitor log please.
Log Files as requested
Hi,
I have captured information using usb monitor and attached the zipped log files for your attention.
The first is called USB_monitor_log_Herm_120Radio_twice. This log details attempting to install the HERM_1.20.31.10_type2_radio_fixed upgrade, and running it twice - just in case.
The USB_monitor_log_runing_Cingular_1.34.502_11_uprgrade_twice.zip details attempting to install the RUU_HER_Cingular_1.34.502.1_1.16.00.00_wwe_cws_ship upgrade, simply using the standard ROMUpgradeUt.exe method. This generates the expected Vendor ID error.
My primary focus is to install the radio upgare or download my bootloader to 1.04. The PDA part of my m3100 does now freeze occasionally but at least functions whereas the phone is completely dead.
Thanks in advance.
Please attach capture in *ANSI TEXT FORMAT*, the .lgs file you zipped is totally unuseful
Edit -> Export and Save as type "ANSI Text files".
Also make sure you export in "COMPLETE" view, see the wiki for more details.
OK, Spot the novice.... I have now created a txt log file that captures activity of me running the 120 Radio upgarde - but only once this time. I still had to zip the file due to it's size. Hope this is OK.
I'll send the other logs within the next couple of hours. Please let me know if the output I have sent so far is acceptable?
Thanks
wotthefok said:
Please let me know if the output I have sent so far is acceptable?
Click to expand...
Click to collapse
No, it's a "basic" capture, you have to export a "complete" capture:
Start USBMonitor.
File -> New session -> USB Monitor -> Select USB device where your phone is connected -> Check "request view" -> Finish
In the upper part there are two tabs: basic and complete. Click on "Complete".
Right, Try again (duh!) OK, I've tried to keep the log files names as self-explanitory as possible... USB_monitor_log_Herm_120Radio_run1.zip is the r20 radio upgrade, 1st run and USB_monitor_log_Herm_120Radio_run2.zip the second run - without disconneting or resetting the device.
USB_monitor_log_runing_Cingular_1.34.502_11_uprgrade_ran_twice.zip is the Cingular upgrade run via the ROMUpgradeUt.exe, again run twice without disconneting the device.
Hope I got it right this time.....Please let me know if there is anything else I can do.
Thanks.
This time you got the captures right
- You're on bootloader 1.06: You don't have 'rtask' command, you won't be able to do any radio upgrade only.
- Your device is not CID unlocked (Security level=FF, unprivileged)
- The bad flash caused the CID area to corrupt (CID: Wait interpreter timeout)
- When flashing a full ROM you get a CID not allow (255) this is because your corrupted CID doesn't match the CID on the ROM.
The radio part is screwed, you could have fixed this if you where in bootloader 1.04 by flashing a full ROM, but as you are in 1.06 you can't because of CID checking. But you're lucky because the OS ROM is intact and you can boot the OS, you should be able to downgrade to bootloader 1.04 from OS and flash a full ROM after, which will hopefully fix your radio.
Just wait until a solution to downgrade bootloader is available (I'm working on it).
Hi,
As I suspected.... Suppose it's not all bad news though - just means that I have to be patient and use my communicator once more. Do you know if the guys at IMEI-CHECK have a downgrade solution? Even if it's a pay for option??
I have already got a IMEI-CHECK sim unlock from where I originally got the M3100 unlocked from Orange to work on o2. That said, I have run either unlocker 2 or 3 with the .unl that I know worked I now get
HTC HERMES v3c unlock
Starting communication.........
Checking device..............ERROR
The device you try to unlock is not supported.
Please contact your supplier site.
Device is rebooting
Press any key to quit this application.
I'm currently chatting to the guys at IMEI-CHECK re this problem.
Anything else I can do to assist you in anyway??
Cheers
wotthefok said:
Do you know if the guys at IMEI-CHECK have a downgrade solution? Even if it's a pay for option??
Click to expand...
Click to collapse
They have it (M3100v3cUnlock.exe), but it will not work on your device because your IMEI is corrupted and their unlocker will not be able to read it and to check/compare with the .unl key file.
Hi,
Just a quick update. The guys at MIGsofT LTD have VERY VERY generously said they'll have a look at the problem for me so my phone will be winging it's way to them today.
Thanks for your assistance and helping me be certain of the problem and to better understand the root cause.
Hope this information will prove useful to others.
Another quick update...
The guys at IMEI-CHECK (MIGsofT LTD) have rectified problems with my handset and managing to reinstall bootloader 1.04 in the process!!
They also turned my phone around in under three days and only charged me the cost of postage! I had previously been a customer of theirs but it was still a very generous and helpful offer and I would certainly pay for the service than have a duff handset - after all £250 + for a paperweight is rather excessive....
If you're experiencing a problem like mine why not get in touch with them and offer them money to have a look at your handset? No Guarantees but it seemed like my last chance, for a while anyway.
Praise to IMEI-CHECK for a brilliant service - they are King of the day !!
I've seen a few posts now with people having issues with the 1.09 SPL and info 2 returning CID timeout followed eventually by HTCSF kEØ>HTCEUSB.
My M3100 sits at the Windows mobile screen, and doesnt progress. Also get the NO GSM message in the bootloader.
Trying to upgrade (any version) using an activesync connection always fails with device not found errors.
Trying to upgrade (any version) using a bootloader connection usually fails with an invalid country id (244 error?).
Using the japanese downgrade method also gives a country id error.
Using POFs radio only upgrade has no effect (as expected as ipl >1.04).
Using imea-check's tools always gets an invalid device message - apparently due to the required commands not being available.
Incidently - I'm sure that I've only had this problem since running imea-check unlock, however they insist that their software could not do this and are blaming a harware fault... hmm, doubtful to say the least.
Has anyone had any success with reviving the device from this state - I'd be interested if POF's (forthcomming?!) unlock tool will work.......
Any suggestions... it sounds like there's enough "bricks" out there to build a wall.......
Oh, and also tried troubleshooting stuck at Windows Mobile screen as in Wiki, no effect.
I have the same problems....
I take a hard decision. i take it to assistance support, because I was loosing too much time in following all the instructions.
i just hope they can solve my problems in 15/20 days (as they told me) in the cheaper way possible.
ibanyard said:
Has anyone had any success with reviving the device from this state - I'd be interested if POF's (forthcomming?!) unlock tool will work.......
Click to expand...
Click to collapse
It will only work if you are able to boot into WinCE, if you are stuck on wince splash screen it will not
Thought as much.....
Going to send back to htc or orange for "repair".....
Hey,
So, I've got a strange problem. I've bought my HTC TyTn a few weeks ago and I've allready used the HTC_Hermes_SIM_CID_Unlock_v3 to SIM unlock my phone. Everything went fine and I was very happy until the day of releasing WM06 for my device. I've downloaded again the HTC_Hermes_SIM_CID_Unlock_v3 and tried to remove CID to make my device superCID. But now it seems it just doesn't work properly or maybe I'm doing something wrong. Each time the RUU starts ( after softreset, because of confirming 'yes' for sspl, it starts in bootloader ) it can't connect to the device... I don't know what to do, it seems that I do something wrong, but I don't have any idea what
I thougt that maybe just don't need to change the radio, and everything I need to do is to copy the Herm_Unlock_v3, run it and select to remove CID lock. Tried that way but don't have any idea how to check if it's superCID already. Anyway I tried to upgrade to WM6 after that, and It has same problem. RUU just can't connect to my device when it's in bootloader.
Am I doing something wrong ? Somehow it just can't connect to the device now, but at the first time it was perfect. If anyone knows the answer, please report me
sry for my english
I would be happy if someone could help me
Which RUU are you using? Which SPL is on your phone. You may not need to connect in bootloader. If you are using the custom RUU and a "Hard" SPL - then try connecting with the phone up in regular mode.
Found the solution. I think that my USB port in PC is corrupted. Changed the port and everything went fine
Hello all,
I got a friend of mine who came to me with a device-password locked Hermes, which password he cannot recall (actually his girlfriend...). I said I would be willing to give him a hand to unbrick the device. The problem is that I cannot install any ROM on the device, coz I got an error connection right after the screen goes white and the percentage count should normally start.
So I put the Herm in Bootloader (spl-1.06) and try to flash the OliPro Bootloader. The procedure goes correctly until the step where the upgrade itself should begin, counting from 0%... here, I got:
ERROR [262]: Update error: communication error.
I also tried to flash a ROM directly, but since my Bootloader is 1.06, I didn't find a CID match ROM, so it also failed. The Herm is now not bricked, but it stays at the password input screen, so cannot enter windows properly.
Any help on this?
Thanks,
Ionutz
Interesting since you are trying to go around something HTC probably did not want for people to go around due to security....
agovinoveritas said:
Interesting since you are trying to go around something HTC probably did not want for people to go around due to security....
Click to expand...
Click to collapse
yes, i grih you,and normally i wouldnt even try to do such thing, if it hadnt been for a friend of mine which i know.
besides i would like to learn more stuff about my Herm and this is one thing I havent seen discussed here, although i keep reading xda forums for such info.
just found the solution: i flashed another ROM with same CID since my BL was 1.06, but with BL 1.04. After that, I managed to flash any other ROM and automatically upgrade the SPL to 1.10 or 2.10 Oli accordingly.
If any of you interested and dont get the short explanation, PM me.
cheers,
Io, owner of 2 kicking TyTn's
BL 1.06 didnt allow devices with a different CID to be flashed,
eg: my TyTN had the CID: QTEK001 so i couldnt flash a ROM destined for a device with CID: VODAP001
But BL 1.04 had a bug where you COULD flash any ROM to the device regardless of the CID, the first attempt shows a vendor ID error, then try again and it will flash no problem.
The simplest way I would have got past the device security problem would have been a hard reset.
mrvanx said:
BL 1.06 didnt allow devices with a different CID to be flashed,
eg: my TyTN had the CID: QTEK001 so i couldnt flash a ROM destined for a device with CID: VODAP001
But BL 1.04 had a bug where you COULD flash any ROM to the device regardless of the CID, the first attempt shows a vendor ID error, then try again and it will flash no problem.
The simplest way I would have got past the device security problem would have been a hard reset.
Click to expand...
Click to collapse
I know the details about BL 1.04 vs 1.06, thats why I flashed a BL 1.04 ROM, but with the same CID QTEK_001, or smth.
I have to admit though that I never ever thought about doing a simple hard-reset. I guess it would have been to easy, I jumped to more complicate scenarios. Thanks for the help anyway, i gotta learn that.
Thanks mrvanx, glad I read down the whole thread to the part about a simple hard reset working. I lent my 8525 to a friend, thinking he might be interested in buying it, then he didn't have the money, and after I listed it on ebay today, I charged it up to flash to ATT stock, found it password locked, called my friend a few times just getting his voicemail, so tried flashing, and it said the Hermes wasn't connected to the PC...
I figured there would be a solution here at XDA..and POOF, like magic here it is!
So yes, all I had to do was a hard reset, tested and it works, and it was simple, so thanks again mrvanx, although this thread is very old, glad I found it LOL!