Related
Hi All!
Before crash my Orbit(UK) has:
IPL: 1.25.0001
SPL: 1.25.0000
GSM: 02.67.90
OS: 1.25.00
In About was: OS 5.1.342 (Build 15096.3.0.0)
I have try to flash this ROM:
PDAVIET from PhamQuang
http://www.pdaviet.net/showpost.php?p=124633&postcount=313
(pass PDAVIET)
and made an mistake: I dont flash Artemis Update SPL (USPL) v.01 ( http://forum.xda-developers.com/showthread.php?t=311403 ) before PDAVIET from PhamQuang
Now my Orbit is freese after start on bootscreen.
But I CAN ENTER to Bootloader.
Help me to ident official ROM (and give link to file, please) or say what can I do in this situation.
I've try this ROM's:
O2 XDA Orbit 3.4.207 GER - say: FEHLER [244] : UNGULTIGE MODELL ID
T-mobile UK 1.13.110 - say: ERROR [294] : INVALID VENDER ID
English Dopod 1.25.707 - say: ERROR [244] : INVALID MODEL ID
ART_HTCFRA_11240601_026790_FRA_SHIP.exe -say: ERROR [244] : INVALID MODEL ID
ART_HTCWWE_11140501_024990_WWE_Test_R.exe -say: ERROR [244] : INVALID MODEL ID
ART_HTCWWE_11240501_026790_WWE_Test.exe -say: ERROR [244] : INVALID MODEL ID
DVG said:
Hi All!
Before crash my Orbit(UK) has:
IPL: 1.25.0001
SPL: 1.25.0000
GSM: 02.67.90
OS: 1.25.00
In About was: OS 5.1.342 (Build 15096.3.0.0)
I have try to flash this ROM:
PDAVIET from PhamQuang
http://www.pdaviet.net/showpost.php?p=124633&postcount=313
(pass PDAVIET)
and made an mistake: I dont flash Artemis Update SPL (USPL) v.01 ( http://forum.xda-developers.com/showthread.php?t=311403 ) before PDAVIET from PhamQuang
Now my Orbit is freese after start on bootscreen.
But I CAN ENTER to Bootloader.
Help me to ident official ROM (and give link to file, please) or say what can I do in this situation.
I've try this ROM's:
O2 XDA Orbit 3.4.207 GER - say: FEHLER [244] : UNGULTIGE MODELL ID
T-mobile UK 1.13.110 - say: ERROR [294] : INVALID VENDER ID
English Dopod 1.25.707 - say: ERROR [244] : INVALID MODEL ID
ART_HTCFRA_11240601_026790_FRA_SHIP.exe -say: ERROR [244] : INVALID MODEL ID
ART_HTCWWE_11140501_024990_WWE_Test_R.exe -say: ERROR [244] : INVALID MODEL ID
ART_HTCWWE_11240501_026790_WWE_Test.exe -say: ERROR [244] : INVALID MODEL ID
Click to expand...
Click to collapse
Try this with the file:
Attempt - start the device in mode bootloader. Disconnect AS and start mtty. Choose USB.
Take on one commands ( not copy/paste).
set 32
password BsaD5SeoA
ruurun 0
ResetDevice
An other thing you can try is this provided by stewd:
WARNING THIS WORKED FOR ME THERE IS NO GUARANTEE IT WILL WORK FOR YOU BUT I DON'T SEE WHY NOT TO BE HONEST (SORRY FOR THE CAPS)
Having succesfully bricked my orbit like several others, I spent the morning scratching my head....
I think it was caused by rebooting after running USPL, and then runnig the ROM upgrade....anyway........
My Orbit was stuck on the initial boot O2 screen with red writing on it
IPL 1.25.0001
SPL 1.25.0000
GSM 02.67.90
OS 3.4.0.0
Oh bollocks says I.....
What I did
Download german rom update from german site
http://www.o2online.de/nw/support/do...bit/index.html
Using WinRAR
http://www.win-rar.com/index.php?id=160&dl=wrar370.exe
Extract/Remove files from executable update file to folder on desktop or somewhere handy.
Locate nbh file from blue and black ROM or any ROM for that matter
Place in german update folder using same name as german file
ie. RUU_signed.nbh
Start Orbit in bootloader mode,
Press and hold record button and soft reset,
Plug in USB to PC,
Navigate to your extracted update folder, run ROMupdateUtility.exe, Instructions are in German,
But basically.........
Wieter = next
Abbrechen = Cancel
aktualisieren = update
The update completes succesfully and you have WM6 and an unbricked Orbit......
WOOHOO !
pvdhelm said:
Try this with the file:
Attempt - start the device in mode bootloader. Disconnect AS and start mtty. Choose USB.
Take on one commands ( not copy/paste).
set 32
password BsaD5SeoA
ruurun 0
ResetDevice
Click to expand...
Click to collapse
After that, Orbit is restart..
...and freeze on bootscreen.
On screen is only HTC wallpaper and this text:
IPL: 1.12.0001
SPL: 1.12.0000
GSM: 02.67.90
OS: 3.4.0.0
Click to expand...
Click to collapse
pvdhelm said:
What I did
Download german rom update from german site
http://www.o2online.de/nw/support/do...bit/index.html
Using WinRAR
http://www.win-rar.com/index.php?id=160&dl=wrar370.exe
Extract/Remove files from executable update file to folder on desktop or somewhere handy.
Locate nbh file from blue and black ROM or any ROM for that matter
Place in german update folder using same name as german file
ie. RUU_signed.nbh
Start Orbit in bootloader mode,
Press and hold record button and soft reset,
Plug in USB to PC,
Navigate to your extracted update folder, run ROMupdateUtility.exe, Instructions are in German,
Click to expand...
Click to collapse
In this case:
My Orbit is start's upgrade, but in 3% - reboot and:
On screen is only HTC wallpaper and this text:
IPL: 1.12.0001
SPL: 1.12.0000
GSM: 02.67.90
OS: 3.4.0.0
Click to expand...
Click to collapse
In this time on PC - FEHLER [270]: UPDATE-FEHLER
Any other ideas?
imei-check
you will have to send it to a repair center..i had the same issue
you can also send it to the guys at imei-check.co.uk but they accept only EU shipments..the repair will cost you 40£ + 7£
zipper9 said:
you will have to send it to a repair center..i had the same issue
you can also send it to the guys at imei-check.co.uk but they accept only EU shipments..the repair will cost you 40£ + 7£
Click to expand...
Click to collapse
Only this way?
I'm not from UK.
Anybody else?
Still actually.
The fourth day without phone.
pvdhelm
You see that give ????
Your file SPL from Hermes !!!
If you load this on artemis -brick!
My "getdevinfo" is:
41 52 54 45 32 30 30 30 30 00 00 00 00 00 00 00 ARTE20000.......
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
4F 32 5F 5F 5F 30 30 31 00 00 00 00 00 00 00 00 O2___001........
00 00 00 00 00 00 00 00 00 00 00 00 00 00 ..............
Click to expand...
Click to collapse
DVG said:
My "getdevinfo" is:
Click to expand...
Click to collapse
Your Orbit is actually from O2 UK (CID: O2___001). You have to find a ROM for O2 Orbit UK then. Unfortunately, no one has it at the moment, and O2 UK does not seem to release the update soon. You have to wait then, I guess!
One thing I wonder: This code was returned by "getdevinfo" command from within mtty or from nbh file that you tried to flash? Usually "getdevinfo" in mtty returns only ARTE10000, ARTE20000 or ARTE30000
Use USB sniffer and see command getdevinfo
my device ARTE10000 and CID 11111111 (SuperCID )
Code:
Cmd>
67 g
67 g
65 e
65 e
74 t
74 t
64 d
64 d
65 e
65 e
76 v
76 v
69 i
69 i
6e n
6e n
66 f
66 f
6f o
6f o
0d .
0d 0a ..
48 54 43 53 HTCS
41 52 54 45 31 30 30 30 30 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ARTE10000.......
31 31 31 31 31 31 31 31 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 11111111........
00 00 ..
e3 a4 ef 19 ....
48 54 43 45 HTCE
0d 0a ..
43 6d 64 3e Cmd>
YEAH!!! I've succesfully unbrik my Artemis!!! I'm too happy!!!
fabbio87 said:
YEAH!!! I've succesfully unbrik my Artemis!!! I'm too happy!!!
Click to expand...
Click to collapse
By what method?
Whit this method (posteb by PVDHELM)
Download german rom update from german site
http://www.o2online.de/nw/support/do...bit/index.html
Using WinRAR
http://www.win-rar.com/index.php?id=160&dl=wrar370.exe
Extract/Remove files from executable update file to folder on desktop or somewhere handy.
Locate nbh file from blue and black ROM or any ROM for that matter
Place in german update folder using same name as german file
ie. RUU_signed.nbh
Start Orbit in bootloader mode,
Press and hold record button and soft reset,
Plug in USB to PC,
Navigate to your extracted update folder, run ROMupdateUtility.exe, Instructions are in German,
But basically.........
Wieter = next
Abbrechen = Cancel
aktualisieren = update
For me this method work! I've an Italian No Brand Artemis (HTC P3300) with CID Lock and without Sim Lock.
fabbio87 said:
Whit this method (posteb by PVDHELM)
Click to expand...
Click to collapse
It means that you have a German Artemis device, but my Orbit - had UK firmware basically. And now I can't find it.
No, my phone is Italian, not german!
fabbio87 said:
No, my phone is Italian, not german!
Click to expand...
Click to collapse
You are lucky! I am sure your device is CID UNLOCKED (may be you did not know) so you could flash Black and Blue ROM. This ROM was made by HTC ROM tool and signed with SuperCID. Congratulations! You can now flash any ROM you build by HTCRT.
I don't know if my HTC is CID unlock, how can i do to know if it is? I've never try to unlock it, i only flash the USPL...
fabbio87 said:
how can i do to know if it is?
Click to expand...
Click to collapse
Turn off USB connection in ActiveSync.
Take mtty and any USB sniffer.
In mtty chose USB connection.
And then TYPE:
set 32
password BsaD5SeoA
getdevinfo
ruurun 0
ResetDevice
After getdevinfo command see what in USB sniffer. If there CID 11111111 - you are lucky - it Super CID - your device is CID Unlocked.
My problem is still actually.
Hi, Weather Database Editor doesnt work with my Girlfriends Touch 3G (german).
Is there any Solution to manually add Cities?
Thanks. =)
Same problem here
Try this one..
http://forum.xda-developers.com/showpost.php?p=2488224&postcount=73
Thanks but it does no show any cities...
yepp, seems that the database has another filename...
i try investigating this...
Ok, found the Database. =)
Its HH_0407_WeatherCities.xml (for German Users i think).
Bad news:
Its hidden/system/in rom
Any ideas how to rename it?
I copied it to the PC and edited the Cities in but i cant copy it back to the phone...
You can easily overwrite the file with resco explorer after disabling touchflo from the today screen but I have yet to find a way to copy the file to the pc. Could you share your xml please?
Ok I am getting nearer.
Disable touchflo
Copy HH_0407_WeatherCities.xml from the /windows folder to your pc.
Edit the xml to include your new city.
Copy it back to the phone into somewhere like "My Documents" then use resco explorer to move it to /windows and overwrite the original file.
Copy manil2d.exe from windows to your pc,
download XVI32 from http://www.chmaas.handshake.de/delphi/freeware/xvi32/xvi32.htm
download sign code from N2A's site http://weather.not2advanced.com/files/SignCode.zip
Open manila2d.exe in XVI32 and do a search for "weather.manila1.htc.com" ( make sure Unicode check box is checked )
You will see the update URL in unicode , which means that if you want to replace it , there has to be a hex 00 between every letter !
It needs to be changed to something like weather.not2advanced.com/htcweather/forecastdata.php?locCode=%s%s%s
save manila2d.exe and sign it using N2A's batch file
Copy it back to the phone into somewhere like "My Documents" then use resco explorer to move it to /windows and overwrite the original file.
Now I have the new city listed but when I update, all the temperatures = 0
I'm not sure what I have done wrong but I think the URL is wrong.
Any ideas?
Ok, the URL was different for me.
Done that but without the %s%s%s.
Still not working.
I can select the cities but i cant see them in the tab.
Update says that it cannot get updates for the selected city.
Hi Vibez
I reply here instead of the PM , so the others can read it aswell
I don't have a touch 3G so I cannot experiment for you , but 1 thing is sure ,
people had the same issue on the Diamond ( cities not updating after hex-edit ) when the hex-edit was not done 100% correctly ...
So 2 questions :
1) Did any of you try the reigistry hack from the diamond ?
In stock ROM, the URL used to update the weather is a specific Accuweather URL. WDE change it to point to N2A'website ( http://weather.not2advanced.com/ ).
Registry key=HKEY_CURRENT_USER\Software\HTC\Manila
String value Name=Weather.ServerURLOverride
Click to expand...
Click to collapse
2) when u tried patching , did the replacement weather string have EXACTLY the same length as the original ? On the diamond , it was an absolute no-go when the length was different
Open manila exe in XVI32 and do a search for "weather.manila1.htc.com" ( make sure Unicode check box is checked )
You will see the update URL in unicode , which means that if you want to replace it , there has to be a hex 00 between every letter !
I then replaced : http://weather.manila1.htc.com/widget/htc/forecast-data_v3.asp?locCode=%1s&?ac=TR2cra9U
with : http://weather.not2advanced.com/htcweather/forecastdata.php?locCode=%1s&ac=XDADevs1234
Those two lines have exactely the same length upto there ( That's why i added 1234 to the XDAdevs , thankfully that's ok with N2A's site ) so the rest of the URL ( &device=innovation etc.. ) can remain unchanged !
Click to expand...
Click to collapse
If that fails to work , send me a copy of the manila app ( modded and original maybe so I can see what u did ) , I'll look at it , patch it & send it back for you to try ...
I can't promise anything of course , but I'm on holidays this week , so I've got a little time to spare ;-)
cheers,
Claude
Thanks for the info!
Unicode-Strings should be NULL-terminated to, so all i've done was to zero out the remaining chars.
I give it a try and answer here asap.
//edit:
Ok, works but Temps are at 0°C.
Seems that the XML-Format has been changed.
BTW: String used for Patching Mainila2D.exe was:
000D8858 68 00 74 00 74 00 70 00 3A 00 2F 00 2F 00 77 00 65 00 61 00 74 00 68 00 h.t.t.p.:././.w.e.a.t.h.
000D8870 65 00 72 00 2E 00 6E 00 6F 00 74 00 32 00 61 00 64 00 76 00 61 00 6E 00 e.r...n.o.t.2.a.d.v.a.n.
000D8888 63 00 65 00 64 00 2E 00 63 00 6F 00 6D 00 2F 00 68 00 74 00 63 00 77 00 c.e.d...c.o.m./.h.t.c.w.
000D88A0 65 00 61 00 74 00 68 00 65 00 72 00 2F 00 66 00 6F 00 72 00 65 00 63 00 e.a.t.h.e.r./.f.o.r.e.c.
000D88B8 61 00 73 00 74 00 64 00 61 00 74 00 61 00 2E 00 70 00 68 00 70 00 3F 00 a.s.t.d.a.t.a...p.h.p.?.
000D88D0 6C 00 6F 00 63 00 43 00 6F 00 64 00 65 00 3D 00 25 00 31 00 73 00 00 00 l.o.c.C.o.d.e.=.%.1.s...
Ahw F...!
Tested the original URL:
first, city in original database:
http://htc.accuweather.com/widget/htc/forecast-data.asp?ac=TR2cra9U&locCode=EUR|DE|GM011|AACHEN
second, city manually added:
http://htc.accuweather.com/widget/h...ac=TR2cra9U&locCode=EUR|DE|GM017|SCHMALKALDEN
second URL does NOT give any information back in the XML...
Seems that the database is also online and it trys to find the city there...
OK, tried the not2advanced URL, XML Format has changed heavily...
*sniff*
Garfield1970,
Thanks for helping out.
The registry trick did not work.
I did find a patched version of manila2d.exe from another rom that works perfect on our phone, but ideally I would like to see how to patch the original version that our phone ships with. The hex surrounding the URL string in our manilla2d.exe looks a little different. I'm not 100% there is enough room to fit the full N2A url in!
I will post all 3 versions later for you to play with.
Weltherrscher said:
Ahw F...!
Tested the original URL:
first, city in original database:
http://htc.accuweather.com/widget/htc/forecast-data.asp?ac=TR2cra9U&locCode=EUR|DE|GM011|AACHEN
Click to expand...
Click to collapse
Ok
second, city manually added:
http://htc.accuweather.com/widget/h...ac=TR2cra9U&locCode=EUR|DE|GM017|SCHMALKALDEN
second URL does NOT give any information back in the XML...
Seems that the database is also online and it trys to find the city there...
Click to expand...
Click to collapse
That's normal as that city is unknown to the HTC Server
OK, tried the not2advanced URL, XML Format has changed heavily...
*sniff*
Click to expand...
Click to collapse
Indeed , I just compared the XML Outputs for Aachen from HTC & N2A , they changed the format .... But if you ask N2A very very nicely and if he has some time to spare , he might eventually adapt a version of his script to reflect the other XML format
You can clearly see the differences between the following two outputs :
http://weather.not2advanced.com/htc...hp?locCode=EUR|DE|GM011|AACHEN&ac=XDADevs1234
is the Diamond compatible format
http://htc.accuweather.com/widget/htc/forecast-data.asp?ac=TR2cra9U&locCode=EUR|DE|GM011|AACHEN
is the format the touch 3g seems to need ....
I'll crosspost the URL's to N2A's main thread so he can maybe have a look
Claude
Just for info the XML format that ships with our ROM works fine with N2A.
To me it seems N2A provides extra elements which I assume is for compatibility with HTC home.
So no need as far as I can tell to ask him to change anything.
Unless i'm getting confused in what you are saying?
vibez said:
Just for info the XML format that ships with our ROM works fine with N2A.
To me it seems N2A provides extra elements which I assume is for compatibility with HTC home.
So no need as far as I can tell to ask him to change anything.
Unless i'm getting confused in what you are saying?
Click to expand...
Click to collapse
Are you sure that the N2A output works for you ?
Because if you look at the XML's , what your device expects is to see includes blocks titled :
Today
Tonight
Tomorrow
and then the following weekdays
whereas on my Diamond it's just current and the different Weekdays being reported
Claude
I'm 100% sure it works with this version of manila2d.exe that i'm using. Now it may be that this version I have uses the old format.
We don't have
Today
Tonight
Tomorrow
we just have current temp, and hi, lo for each day
You mean using the patched manila from the other rom that you mentionned earlier ?
Might be that the format switch has happened between differen Rom versions ?
Claude
Garfield1970 said:
You mean using the patched manila from the other rom that you mentionned earlier ?
Might be that the format switch has happened between differen Rom versions ?
Claude
Click to expand...
Click to collapse
Yes it could be that. Although the end result is the same. The original version only showed Current and hi/lo temps
Ok i've attached the files
Manila2D_original.exe
This is the original unpatched file
Manila2D_original_patched_not_working.exe
This the original file I tried to patch without success
Manila2D_patched_ok.exe
This is the patched file from another rom that works ok.
I recently just re-flashed the rom on my elf, it got to 100% and windows said it completed. I now try to turn the phone on and nothing happens? the battery isnt dead either, help please
tjeaton said:
I recently just re-flashed the rom on my elf, it got to 100% and windows said it completed. I now try to turn the phone on and nothing happens? the battery isnt dead either, help please
Click to expand...
Click to collapse
hmmm, not sure if this helps (coz i arrived at it through a different process). but my device couldn't be turned on. no light even as charger was plugged in. but i did the "hold Camera button and poke the reset hole" then i got into boot into bootloader
please help
my htc touch p3452 is dead becoz i flash but something is wrong and then it was dead now it will on on bootloder mode(red,green,blue) here is my detail please tell ,me what to do
it show..
IPL 3.07.0002
SPL 3.07.0000
DEVICE ID= ELF010050
CID= DOPOD001
45 4C 46 30 31 30 30 35 30 00 00 00 00 00 00 00 ELF010050.......
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
44 4F 50 4F 44 30 30 31 00 00 00 00 00 00 00 00 DOPOD001........
00 00 00 00 00 00 00 00 00 00 00 00 00 00 ..............
i also tryed to flash "DID-ELF010050_CID-DOPOD001_ROM-2.20.721.2B" but is not flashed it gave "error 270 update error" something please tell me where is the problem and how to solve please guys
You have to cid unlock first before flashing any rom...
vicky.9871 said:
my htc touch p3452 is dead becoz i flash but something is wrong and then it was dead now it will on on bootloder mode(red,green,blue) here is my detail please tell ,me what to do
it show..
IPL 3.07.0002
SPL 3.07.0000
DEVICE ID= ELF010050
CID= DOPOD001
45 4C 46 30 31 30 30 35 30 00 00 00 00 00 00 00 ELF010050.......
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
44 4F 50 4F 44 30 30 31 00 00 00 00 00 00 00 00 DOPOD001........
00 00 00 00 00 00 00 00 00 00 00 00 00 00 ..............
i also tryed to flash "DID-ELF010050_CID-DOPOD001_ROM-2.20.721.2B" but is not flashed it gave "error 270 update error" something please tell me where is the problem and how to solve please guys
Click to expand...
Click to collapse
ok.. maybe you should try this.. hope it helps..
tito12 said:
You have to cid unlock first before flashing any rom...
Click to expand...
Click to collapse
Yup by the prob its showin, the CID is definitely locked, so 1st unlock the CID & then flash the ROM of your choice..!!!
Do remember also upgrade the "IPL & HSPL"..!!!
Njoy the FLASHING..!!!
thankyou but tell me
how to downgrade or upgrade my ips and spl my device already in bootloder mode please tell me
to upgrade your SPL (or flash HardSPL) u first need to have your device "alive" again as flashing the HardSPL is done by using ActiveSync.. I would suggest you try a hard reset (by holding the Call & End buttons and reseting with the stylus).. if that didn't work and you still can't load into WinMo interface.. then you might want to try the method I mentioned above..
hope this helps..
Ok just some info about the phone:
I already CID unlocked it, so that couldnt have been the problem as i was running onyx rom
I have tried getting into the three colours screen and still nothing happens, the battery isn't dead
Led used to turn on when it was charging now it doesn't :/
On button doesn't seem to make the device do anything either
tjeaton said:
Ok just some info about the phone:
I already CID unlocked it, so that couldnt have been the problem as i was running onyx rom
I have tried getting into the three colours screen and still nothing happens, the battery isn't dead
Led used to turn on when it was charging now it doesn't :/
On button doesn't seem to make the device do anything either
Click to expand...
Click to collapse
Did you flash an original or shipped ROM?? sometimes that causes problems when used with HardSPL..
Yeah it was an original backup of the factory rom that was already on it, is their anyway of actually recovering my phone to a normal state again, at least the tri color or even led's when charging
tjeaton said:
Yeah it was an original backup of the factory rom that was already on it, is their anyway of actually recovering my phone to a normal state again, at least the tri color or even led's when charging
Click to expand...
Click to collapse
srry man.. but I can't help you.. flashing an original ROM over HardSPL can brick your phone.. and I don't want to disappoint you but I don't know how to recover it.. still I'm a not a pro.. :S:S
anyone else out there on xda can help, it would be great if you could thanks for the help so far people
i'm no sure that u have a software problem but if it is, then your only hope is jtag.
check this: http://forum.xda-developers.com/showthread.php?t=602233
too bad there is no more information anywhere, but at least those jtags are easy to solder!
g00d luck!
btw, have you tried the voodoo reset posted by aonellbicho in the jtag thread? any luck with it?
I've never seen it before, and u will probably need as many hands as Shiva has to do it...
guess i can give it a go, what else could go wrong lol
yeah the voodoo reset doesn't work, i think its a fake its pretty hard to press all of those things at once
Hi, I created simple tool that will be used for permanently wifi mac changes. Before you use this tool you must to understand that I will not be responsible for any damage you done by using this tool !!! You must agre that you using this tool on your own risk!
How to use this tool:
- you must be s-off and you need to have installed revolutionary hboot! If you do not have installed revolutionary, skip this tool!!!
- open command prompt and type hboot_mac ... you will get instructions!
- when you sucesfully generate patched hboot, reboot phone to fastboot mode
fastboot commands:
- fastboot oem eraseWifiFlash
- fastboot flash hboot hboot_mac_patched.img
- fastboot reboot-bootloader
verify if mac is changed:
- fastboot oem emapiWlanMac
Warning! This patched hboot have disabled hboot overwriting security so you need after next reboot to install hboot from attachment!!!
- fastboot flash hboot revolutionary_hboot.bin
- fastboot reboot
Done! Enjoy!
EDIT:
And do not install hboot 1.03.0000, its locked bull**** and you will not be able to back to hboot 1.02.0000 or any other!!!
Good contrib, however i have got htcdev.com hboot 1.03. Is possible come back to hboot 1.02?
Thanks
Hi, please give me hboot 1.03, I will test it and will report here!
hboot zip file contains nb0, not img file.
munjeni said:
Hi, please give me hboot 1.03, I will test it and will report here!
Click to expand...
Click to collapse
Is this htcdev.com hboot 1.03 ? My device is locked now with this hboot!
Yes, it is the hdev hboot !
munjeni said:
Is this htcdev.com hboot 1.03 ? My device is locked now with this hboot!
Click to expand...
Click to collapse
Ok but this is b.s. from htcdev... its say unlocked but its still locked and s-on... no way s-off
Is possible downgrade to hboot 1.02?
No way for now .
munjeni said:
Ok but this is b.s. from htcdev... its say unlocked but its still locked and s-on... no way s-off
Click to expand...
Click to collapse
It's not S-OFF, but it does allow you to flash custom recovery, install ROMs, and write to system partition while booted. Most people won't have any issues with it.
I think there is a way to downgrade from 1.03 to 1.02, but it's not for the faint of heart. Ask in #liberatedAria on Freenode.
drumist said:
Ask in #liberatedAria on Freenode.
Click to expand...
Click to collapse
Yes, I joined irc and when I said "hallo" Anthony1s gave me BAN , so why?
Try this
http://forum.xda-developers.com/showpost.php?p=21746420&postcount=14
It worked for me!
Anthony1s seems a little touchy, I asked for help and I was banned too.
munjeni said:
Yes, I joined irc and when I said "hallo" Anthony1s gave me BAN , so why?
Click to expand...
Click to collapse
---------- Post added at 07:55 PM ---------- Previous post was at 07:54 PM ----------
With revolutionary hboot fastboot oem emapiWlanMac 00 01 02 03 04 05 works fine, although thanks anyway
zeubea said:
Try this
http://forum.xda-developers.com/showpost.php?p=21746420&postcount=14
It worked for me!
Click to expand...
Click to collapse
Thanks, do you installed hboot 1.02 ower htcdev hboot 1.03 using this??
Indeed I installed 1.0.0 hboot RUU and then upgrading to 1.02, then revo for S-off , then unrevocked for cwm,.and finally restore. Crazy, but it worked for me.
munjeni said:
Thanks, do you installed hboot 1.02 ower htcdev hboot 1.03 using this??
Click to expand...
Click to collapse
Ok, but I think its not possible if have hboot 1.03... allready tried with gold card without luck
You must to patch misc partition as previous step. I modified a tool for it. I detail this step at http://forum.xda-developers.com/showpost.php?p=23381950&postcount=21
zeubea said:
for downgrade 1.03 to 1.02 and worked for me.
Click to expand...
Click to collapse
you had hboot 1.03 from htcdev -> http://htcdev.com/bootloader/ ? Are you sure?
EDIT:
I can confirm it not working while have hboot 1.03, tried now!
This is misc partition that is modified, and gold card is 100% gold card that I used before
Code:
Offset(h) 00 01 02 03 04 05 06 07 08 09 0A 0B 0C 0D 0E 0F
00000000 31 31 31 31 31 31 31 31 00 00 00 00 00 00 00 00 11111111........
00000010 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
00000020 44 65 76 69 63 65 57 61 72 6D 42 6F 6F 74 00 00 DeviceWarmBoot..
00000030 FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF ˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙
00000040 FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF ˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙˙
00000050 43 45 20 53 65 72 69 61 6C 20 49 6E 55 73 65 00 CE Serial InUse.
00000060 44 65 62 75 67 20 43 61 62 6C 65 20 45 6E 61 00 Debug Cable Ena.
00000070 43 45 20 20 20 55 53 42 20 20 49 6E 55 73 65 00 CE USB InUse.
00000080 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
00000090 43 6C 65 61 72 41 75 74 6F 49 6D 61 67 65 00 00 ClearAutoImage..
000000A0 31 2E 31 31 2E 31 31 31 2E 31 00 00 00 00 00 00 1.11.111.1......
Indeed I installed 1.0.0 hboot RUU and then upgrading to 1.02, then revo for S-off , then unrevocked for cwm,.and finally restore. Crazy, but it worked for me
Click to expand...
Click to collapse
from this mesage I did not see that you had hboot 1.03, do you want to confirm?
YES I had hboot 1.03 from htdev.
Did you do relock? fastboot oem lock
Yes, its working after relocking... thanks dude!
Ok, I gave the hboot 1.03, so problem solved
I recently acquired a Verizon-branded LG V20 (VS995) and I my eventual goal is to put TWRP and LineageOS on it like my last phone. The first step is to downgrade it to a vulnerable stock image using UPPERCUT. However, I'm finding that LGUP is unable to begin to perform the flash.
My setup/procedure is as such:
1. Fresh Windows 7 x64 installation in Virtualbox 5.2.16 on Arch Linux
1a. USB filter setup so that USB 1004:633a is always passed through to Windows 7
2. Installed drivers: LGMobileDriver_WHQL_Ver_4.2.0.exe
3. Installed LGUP 1.14: LGUP_Store_Frame_Ver_1_14_3.msi
4. Insert battery into LG V20 VS995
5. Insert USB into computer
6. Hold VOLUP while inserting USB-C into V20
7. Wait as "download mode" message appears and then changes to "Firmware Update" screen.
8. Wait for Windows to install all drivers, ensuring devmgmt.msc shows COM port
9. Launch UPPERCUT v1.0.0.0, granting admin permissions
10. Wait for LGUP to launch, initialize, and show a VS9951CA device
11. Select the December 2016 KDZ: VS99512A_06_1114_ARB00.kdz
12. Select UPGRADE and hit Start
After waiting for the 15 second initialization period, LGUP displays the error "Cannot decide device boot mode. set Unknown". If left in this state for several minutes, LGUP will eventually bring up a dialog saying "Error: 0x2000, Port open error (COMX)". LGUP sometimes says it is on a step which I have not transcribed correctly but resembles "_prepareAndDL" before showing the "Cannot decide device boot mode. set Unknown" error, but I've only seen this step once or twice.
SHA1 sums of the files I'm using:
eac54e3e0cfe6e8d7cd395e245170e13de4fcd67 lgmobiledriver_whql_ver_4.2.0.exe
f7b41f77047698bc8e030dddf4ef6fbdb5c3af41 lgup_store_frame_ver_1_14_3.msi
46c9a349d62287d81c94ce7148233c0922604273 uppercut_1.0.0.0.zip
3104b93b7243e3274932b2c56b8383cdecf7ede3 vs99512a_06_1114_arb00.kdz
Is UPPERCUT still the recommended tool to flash stock firmware for this model? Should I be installing it via fastboot instead (if so, is there a thread to follow)? Is the 1CA update no longer downgradable?
--------------------
I tried to use the patched LGUP tool instead of UPPERCUT to see if that helped at all. I did not try to flash the KDZ, but rather just tried to DUMP the existing partitions. I ran into the same error as the post title again.
Procedure:
0. In the LGUP program files directory:
1. Copy the original LGUP.exe to LGUP.original.exe
2. Copy the patched LGUP.exe into it's place
3. Copy in the 'model/common' directory from the patched LGUP zip
4. Steps 4->8 from above
9. Launch patched LGUP (no UPPERCUT)
10. Same as above
11. Select DUMP, hit start, select dump location
SHA1 sum of additional files:
242640ddb023308b9a103e0a767f27511c9a2db0 lgup_v20dll_patched.zip
I captured a trace of the USB communication with wireshark. I used the LG LAF protocol plugin (can't post links yet: github com/Lekensteyn/lglaf/blob/master/lglaf.lua) and it didn't find any USB frames that matched the protocol. I'm no USB wire protocol expert, but it looks like the phone is sending a response:
Code:
0000 1b 00 10 b0 62 03 80 fa ff ff 00 00 00 00 09 00 ...°b..úÿÿ......
0010 01 02 00 01 00 83 03 97 00 00 00 ef a0 00 00 00 ...........ï*...
0020 00 00 56 53 39 39 35 00 00 00 00 00 56 53 39 39 ..VS995.....VS99
0030 35 31 43 41 00 00 00 00 00 00 00 00 00 00 00 00 51CA............
0040 00 00 00 00 00 00 00 00 00 00 01 33 35 39 39 36 ...........35996
0050 38 30 37 32 39 39 39 30 37 36 00 00 00 00 00 60 8072999076.....`
0060 1e 41 6e 64 72 6f 69 64 00 00 00 37 2e 30 00 00 .Android...7.0..
0070 00 00 00 00 00 3X 3X 3X 3X 3X 3X 3X 3X 3X X9 00 .....XXXXXXXXXX.
0080 00 00 00 00 02 00 00 00 00 00 00 00 00 00 00 00 ................
0090 00 00 00 00 00 00 31 63 6f 6d 6d 6f 6e 00 00 00 ......1common...
00a0 56 5a 57 31 00 00 00 00 00 00 00 00 00 00 7d 5d VZW1..........}]
00b0 86 7e .~
There were five such frames, all essentially identical less a byte or two. I suspect if I had let the capture go they would have continued to arrive at an interval. So it's possible the LGUP tool just is not recognizing the ping that the phone is sending?
Install the VirtualBox extension pack and set your USB config for that VM to 2.0 or 3.1, and you should be good.
1CA is definitely downgradable. This is a USB communication problem.
-- Brian
I re-confirmed that I had the guest extensions installed (VM has no nic and all files were transferred in via shared folders, which requires guest extensions). But it turns out I did have the USB bus set to USB 2.0. After setting that to USB 3.0 and installing the Intel USB3 drivers for Windows, LGUP started the download without issue. This is still the patched LGUP (no UPPERCUT) and using the UPGRADE option with the KDZ mentioned in the OP. Oddly enough, it did not clear my data, as it asked for my encryption passphrase when it rebooted. It did successfully downgrade me, so I just did a factory reset to clear my old data and apps. As a reminder, the LG out-of-the-box experience starts checking for OTA updates as soon as the phone starts up, so remove your SIM before you start.
1. Remove SIM
2. Do one of the following:
CLI:
Code:
vboxmanage modifyvm $vmname --usbehci off && vboxmanage modifyvm $vmname --usbxhci on
UI: Right click VM > Settings > USB > USB 3.0 (XHCI) Controller