On Fire HD 2014 I started looking at md5sum for partitions for different OS versions, and it seems that on Fire 2015 one can figure out which partition gets screwed up by 5.1.1 bootloaders, and perhaps restore it to pre-5.1.1 state. If this fails, the warranty should kick in (all of the Fire 2015s are still under warranty !!!)
Please see this link for some details :
http://forum.xda-developers.com/fire-hd/help/trying-to-undo-bricking-5-2-2u2-t3301374
Basically, the idea is simple. First one captures all the partitions while running 5.0.1 bootloaders. Then the bootloaders are updated to 5.1.1 version. At this point the partitions are captured again. This is the code to capture partitions to be run on PC via adb:
Code:
adb shell
su
mkdir /sdcard/tmp/
dd if=/dev/block/mmcblk0p1 of=/sdcard/tmp/01_kb.img
dd if=/dev/block/mmcblk0p2 of=/sdcard/tmp/02_dkb.img
dd if=/dev/block/mmcblk0p3 of=/sdcard/tmp/03_expdb.img
dd if=/dev/block/mmcblk0p7 of=/sdcard/tmp/07_misc.img
dd if=/dev/block/mmcblk0p8 of=/sdcard/tmp/08_logo.img
cd /sdcard/tmp
md5 *.img
Then one can simply exit, and do "adb pull /sdcard/tmp/" to get all these *.img files off the device.
Then those partitions that changed (KB,DKB,EXPDB,MISC) are dd'ed back under 5.1.1, and bootloaders are dd'ed back to 5.0.1 versions. If it reboots OK, this means that the device is effectively restored to pre-5.1.1 state. If failure, warranty return.
The next step to try would be to transplant this offending partition from a different Fire to a device with 5.1.1, along with 5.0.1 bootloaders.
Here is the list of partitions for reference:
http://forum.xda-developers.com/amazon-fire/development/partitions-list-t3236213
When one tires to downgrade to 5.0.1, it's the preloader stage which the Fire keeps cycling at. We have already tried flashing the 5.0.1 bootloader & preloader onto a 5.1.1 Fire.
blueberry.sky said:
When one tires to downgrade to 5.0.1, it's the preloader stage which the Fire keeps cycling at. We have already tried flashing the 5.0.1 bootloader & preloader onto a 5.1.1 Fire.
Click to expand...
Click to collapse
But this would not make sense. Are you saying that the preloader does not even try to call the 5.0.1 bootloaders ? But then why ?
Since the preloader stays the same, the only difference is that 5.0.1 bootloaders are trying to run after 5.1.1 bootloaders already ran on the device. At this stage 5.0.1 cannot proceed normally, which must be due to some changes sitting on some of the partitions that the bootloaders are reading early on.
We have no indication that 5.0.1 bootloaders do not run at all, they may run a bit, and then crash, and the device is back at the preloader stage.
So restoring additional partitions together with 5.0.1 bootloaders may enable 5.0.1 to function again after 5.1.1, as per my original post.
bibikalka said:
Since the preloader stays the same, the only difference is that 5.0.1 bootloaders are trying to run after 5.1.1 bootloaders already ran on the device.
Click to expand...
Click to collapse
Have you verified that the 5.0.1 and 5.1.1 preloaders are the same?
bibikalka said:
Are you saying that the preloader does not even try to call the 5.0.1 bootloaders ?
Click to expand...
Click to collapse
Just know that when plugged into a pc you will see the preloader cycle endlessly. Connect, disconnect, repeat. And someone did try to flash the both the bootloader & preloader extracted from 5.0.1.
It could be that 5.1.1 is blowing a fuse which tell older versions to refuse to boot.
bibikalka said:
On Fire HD 2014 I started looking at md5sum for partitions for different OS versions, and it seems that on Fire 2015 one can figure out which partition gets screwed up by 5.1.1 bootloaders, and perhaps restore it to pre-5.1.1 state. If this fails, the warranty should kick in (all of the Fire 2015s are still under warranty !!!)
Please see this link for some details :
http://forum.xda-developers.com/fire-hd/help/trying-to-undo-bricking-5-2-2u2-t3301374
Basically, the idea is simple. First one captures all the partitions while running 5.0.1 bootloaders. Then the bootloaders are updated to 5.1.1 version. At this point the partitions are captured again. This is the code to capture partitions to be run on PC via adb:
Code:
adb shell
su
mkdir /sdcard/tmp/
dd if=/dev/block/mmcblk0p1 of=/sdcard/tmp/01_kb.img
dd if=/dev/block/mmcblk0p2 of=/sdcard/tmp/02_dkb.img
dd if=/dev/block/mmcblk0p3 of=/sdcard/tmp/03_expdb.img
dd if=/dev/block/mmcblk0p7 of=/sdcard/tmp/07_misc.img
dd if=/dev/block/mmcblk0p8 of=/sdcard/tmp/08_logo.img
cd /sdcard/tmp
md5 *.img
Then one can simply exit, and do "adb pull /sdcard/tmp/" to get all these *.img files off the device.
Then those partitions that changed (KB,DKB,EXPDB,MISC) are dd'ed back under 5.1.1, and bootloaders are dd'ed back to 5.0.1 versions. If it reboots OK, this means that the device is effectively restored to pre-5.1.1 state. If failure, warranty return.
The next step to try would be to transplant this offending partition from a different Fire to a device with 5.1.1, along with 5.0.1 bootloaders.
Here is the list of partitions for reference:
http://forum.xda-developers.com/amazon-fire/development/partitions-list-t3236213
Click to expand...
Click to collapse
Thanks Bibikalpa. The problem is, to try your solution we have to be able to use adb. We are stuck at fastboot. :crying:
rongweiss said:
Thanks Bibikalpa. The problem is, to try your solution we have to be able to use adb. We are stuck at fastboot. :crying:
Click to expand...
Click to collapse
What he is proposing is not a solution for people who are bricked. Rather it would help prevent people on 5.1.1 from getting bricked in the first place. It would allow downgrading to 5.0.1, restoring the ability to load twrp recovery from fastboot.
---------- Post added at 09:53 PM ---------- Previous post was at 09:11 PM ----------
Here are the md5 checksums from my 5.0.1 Fire
Code:
e1c2e27a6dae694cbf14594b6d963f11 ./01_kb.img
175ec1eea0b65b15ea6ee455531f154d ./02_dkb.img
1d837a219b515afae6c19d9126168f5c ./03_expdb.img
00ff461906b45fc4af74f81839a30069 ./07_misc.img
c414b0be43b26efb5009639be06a74e2 ./08_logo.img
926c891ba8bc265d5dfeabe1ba3838c8 ./09_tee1.img
926c891ba8bc265d5dfeabe1ba3838c8 ./10_tee2.img
Perhaps some of them are the same even between different Fires.
I've already had to get a warranty replacement for my Fire due to a cluster of stuck pixels. Don't want to try upgrading to 5.1.1, risk having to try for a 2nd replacement.
Here are my md5 checksums from 5.1.1 (with 5.1,0 bootloaders, so may not help much, but you didn't ask for bootloaders)
Code:
d47ae72b30dd03c08d0c41883ac219f4 01_kb.img
8b50c460e75aef889840a9077b12c20a 02_dkb.img
4af5655b4a4f2b36ffb81b20605bb75d 03_expdb.img
00ff461906b45fc4af74f81839a30069 07_misc.img
c414b0be43b26efb5009639be06a74e2 08_logo.img
926c891ba8bc265d5dfeabe1ba3838c8 09_tee1.img
926c891ba8bc265d5dfeabe1ba3838c8 10_tee2.img
83b74c9782b889e246bc7b7cfa184d64 04_uboot.img
I'm OK with testing, starting from scratch and rooting my unadultered 5.1.0.
DoLooper said:
Here are my md5 checksums from 5.1.1 (with 5.1,0 bootloaders, so may not help much, but you didn't ask for bootloaders)
Code:
I'm OK with testing, starting from scratch and rooting my unadultered 5.1.0.
Click to expand...
Click to collapse
These look like 5.0.1 checksums for TEE1/TEE2, the same as @blueberry.sky post.
Only the 1st 3 partitions seem to differ. If you run "adb shell; idme print" with root, it actually prints the first few lines of KB & DKB, at least on Fire HD 2014. Does this work on Fire 2015 ?
bibikalka said:
These look like 5.0.1 checksums for TEE1/TEE2, the same as @blueberry.sky post. Only the 1st 3 partitions seem to differ.
Click to expand...
Click to collapse
As said, I'm running 5.0.1 bootloaders.
If you run "adb shell; idme print" with root, it actually prints the first few lines of KB & DKB, at least on Fire HD 2014. Does this work on Fire 2015 ?
Click to expand...
Click to collapse
I get no output with either "idme print /dev/block/kb.img" or "idme print /dev/block/dkb.img" while in su. I assume this is correct syntax.
DoLooper said:
As said, I'm running 5.0.1 bootloaders.
I get no output with either "idme print /dev/block/kb.img" or "idme print /dev/block/dkb.img" while in su. I assume this is correct syntax.
Click to expand...
Click to collapse
It's just straight "idme print", nothing else after that.
bibikalka said:
It's just straight "idme print", nothing else after that.
Click to expand...
Click to collapse
Cool!
Code:
[email protected]:/ # idme print
. . .
KB:
4b 42 50 46 18 0e 00 00 28 0e
00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00
DKB:
30 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00
. . .
Have you tried to connect your device to a computer running SP Flash Tool? If that works, and you manage to get data from the Fire (using the readback window), you may be able to unbrick your tablet.
Related
Hi,
I intend to flash a cooked ROM (ITsPapa20748) to my Herald. From reading some sticky posts here I learned that at first I have to install a hacked bootloader - so I downloaded HardSpl_WM6.rar
My procedure was as follows:
1. install canonyang, ASerg_Policies and Disable_Security (in this order)
2. softreset
3. start RUU
My mobile then enters bootloader mode and ends up with error message "Error [270]: Update Error" (progress bar freezes at 3pct)
My config is as follows:
PC: is running WindowsXP (with SP2), ActiveSync v4.5 is in Guest Mode
Mobile: Model-Nr. Hera100
ROM version 4.17.402.102 GER
IPL 4.17.0001
SPL 4.17.0000
I had to UNcheck the start/system/advanced_networking-box in order to establish USB-connection.
After spending some hours going through existing threads I'm pretty sure that this is a common situation. But I didn't find any hint that helped me to flash successfully.
So any comments and suggestions are welcome.
thx!
1aladdin1
it works now
sorry for posting too early - now it worked.
I basically performed the same steps as listed in my previous post. Two differences:
1. softreset between installation of canonyang/aserpolicy/disable_security
2. while performing the RUU I had FILEMON running (a great tool from mark russinovich)
Finally I don't know, which step was the decisive one - bot anyhow it works now.
Hope this helps other guys in a similar situation.
please guys help me
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
Wwwwwweeeellllllll....YOU HAVE AN ELF, NOT A HERALD. Seriously, if you tried to HardSPL your Elf with the Herald HardSPL...I don't even know. These are the Herald forums, NOT the Elf forums, as such, more than likely no one that frequents here will know what to do to help you.
use for rewrite ESN and flash ROMs. good luck.
rename it to .rar, its a winrar file.
MOD EDIT - Removed file. PM me if you disagree and provide me with more history/evidence
Leave it. He has 1 post and the SPL hasn't been cracked yet. Probably a scam.
I have re-opened this thread.
@ ls1024 - Feel free to modify first post again and provide more info including what you showed me in PM
Rick
Thanks Spartan for looking at this. Hopefully once he posts more info it will be what we Imagio users are desperate for, or a step in that direction.
Narcotichobo said:
The linked thread reads as following:
Only 6975's with spl already unlocked can be flashed, before you flash please make sure your spl is unlocked.
Currently all chinese phones come unlocked.
To confirm, go into the three color screen (hold down the volume button and the device on button), spl should be 0.40.0000
After flashing check to see if the radio number is 2.05ESNWVL
The operation below is identical to the 6875 (TP2), if you have a problem refer to posts on 6875 (TP2) ESN post
Use any version of CDMA Work Shop
On the terminal page, commands section
27 97 07 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
After you press send the MEID should be cleared
Afterward you can write whatever ESN
When you finish you can flash any radio and won't lose the ESN
Reference: Tutorial on writing the 6875
http://www.diypda.com/viewthread.php?tid=92838&extra=page=1
Alright, I don't know how to do any of that stuff, but i'm 95% sure on the translation so I hope that helps someone who does know what they are doing!
Also there seems to be an attachment to the post in that thread but i can't access it because I am not a forum member, and registration requires an invitation number.
Click to expand...
Click to collapse
The 0.40 SPL comes on the Chinese version of the Imagio and it allows writing of the ESN and flashing.
All being chatted in this thread:
http://www.forum.ppcgeeks.com/showthread.php?t=97542
Cmonex is working on the HSPL ATM and I do believe it will be based off of the 0.40 SPL
Americanmetal said:
The 0.40 SPL comes on the Chinese version of the Imagio and it allows writing of the ESN and flashing.
All being chatted in this thread:
http://www.forum.ppcgeeks.com/showthread.php?t=97542
Cmonex is working on the HSPL ATM and I do believe it will be based off of the 0.40 SPL
Click to expand...
Click to collapse
Woot I got quoted here.
\/
||
||
\/
And this helps us .38 how?
I think I read this over at PPCG but no instructions on how to do it on a .38 SPL so basically this is for the .40 Imagio only correct?
I posted both modified radios for TP2 and Imagio on PPCG and also a utility to write MEID/ESN (all 3 files from diypda china)
narcotichobo said:
Woot I got quoted here.
Click to expand...
Click to collapse
I had to get this thread unlocked rofl
Still, how can we upgrade to .40? That's what's holding us from at least changing radios to chinese ones hehehe
ls1024 said:
use for rewrite ESN and flash ROMs. good luck.
rename it to .rar, its a winrar file.
MOD EDIT - Removed file. PM me if you disagree and provide me with more history/evidence
Click to expand...
Click to collapse
i have pm...tks.
Ignore this
Here is a couple of files I got from chinese DIYPDA forum. One is a modified radio and the other one a program to simplify the esn repair.
Click to expand...
Click to collapse
Here is the modified radio and DFS, a program that does let you change MEID and/or ESN for when we can do it. Only .40 can change to this radio
Code:
http://www.mediafire.com/?bxjnytljdid
http://www.mediafire.com/?zmtjymhzcjf
we upgrade to 0.40? is the focus of
At least if we can do the .40 upgrade then we can also upgrade to an HSPL that allows unsigned ROMs. Has anybody had any luck with .40? I would like .40 on my phone... And also a way to go back to .38 if possible!
Well, easiest way to go .40 is to buy an Imagio that's .40 already.
taobao(dot)com as specified by our friends at diypda(dot)com has them for 3150 = $461 usd. The question is... If we get this phone and we flash the Imagio shipped rom, will it flash .38 spl or leave it at .40 spl?
It will replace to .38 ,
u must delete SPL from the ruu_signed.nbh
m4f1050 said:
Well, easiest way to go .40 is to buy an Imagio that's .40 already.
taobao(dot)com as specified by our friends at diypda(dot)com has them for 3150 = $461 usd. The question is... If we get this phone and we flash the Imagio shipped rom, will it flash .38 spl or leave it at .40 spl?
Click to expand...
Click to collapse
Hmmm, well, at least the .40 can flash it after you remove .38 spl (will be unsigned afterwards) so how do you remove it? I've cooked ROMs with kitchens before but I have no clue how to remove the SPL from the .nbh
htcRIE_0.5.0.12
m4f1050 said:
Hmmm, well, at least the .40 can flash it after you remove .38 spl (will be unsigned afterwards) so how do you remove it? I've cooked ROMs with kitchens before but I have no clue how to remove the SPL from the .nbh
Click to expand...
Click to collapse
I'll give it a test drive to see how it works. Link here: http://forum.xda-developers.com/showthread.php?t=377514
I tested program, it does work, I managed to remove SPL from the Verizon .nbh but Whitestone is not on the list of selected phones, not sure what that list/dropdown menu is for, is that for signing the ROM?
Imagio ROM Test
I have an Imagio, I am willing to use as Genie Pig if anyone can point me to promising ROM to test out. I'm willing to chance bricking the phone. It has been replaced by a new phone from Verizon.
After fighting versus the Tattoo for 2 hours I have finally flashed the device successfully.
Since there is not a proper thread containing the exact procedure for this device I'm going to explain it a little bit in detail, specially based on this device different things that doesn't have other android phones:
1. First we need to find a micro SD, normally this device comes with a 2gb Sandisk micro SD, this will be fine.
2. We need to format the microSD to FAT32, so remember to save your files before going on.
3. After the format, we need to create a GoldCard with this SD Card. Basically this is a "transformation procedure". You can find the method here: http://forum.xda-developers.com/showthread.php?t=572683 but I'm going to explain it based on Tattoo
Creating the Gold Card:
4. We need the android-sdk tools, we can find them here: http://developer.android.com/sdk/index.html download them, and unzip in a folder maybe in C:\androidtools
5. Go the the Command line (Start->Execute->write cmd and OK), and there you should find where you unzip the android-sdk tools, example cd c:\androidtools\tools
6. Run this command "adb shell cat /sys/class/mmc_host/mmc1/mmc1:*/cid" if you had the microSD in the drive you will find a long number like:
532600bd227d9c0347329407514d5402
7. Go to this page to reverse it: http://hexrev.soaa.me/ and copy the code reversed:
In our example it will be: 00544d5107943247039c7d22bd002653
8. Go to this page to generate your GoldCard image: http://psas.revskills.de/?q=goldcard
And put your reversed number and you email. You will receive an email with a file called "goldcard.img"
9. Now you need an Hex editor like HXD. Download it from: http://download.cnet.com/HxD-Hex-Editor/3000-2352_4-10891068.html?tag=mncol
10. Exactly the same as the instructions I pasted above:
11. Install and launch HxD Hex Editor program. (make sure you use "Run as Administrator" under Vista and win 7)
12. Go to Extra tab > Open Disk. Under Physical disk, select Removable Disk (Must be your SD card), uncheck “Open as Readonly), click OK. (BEWARE, MUST BE UNDER PHYSICAL DISK NOT LOGICAL DISK, THIS MISTAKE MADE ME BIG PROBLEMS)
13. Go to Extra again, Open Disk Image, open up goldcard.img which you’ve saved/unzipped earlier.
Now, you should have two tabs, one is your removable disk, the other is goldcard.img. Press OK when prompted for “Sector Size” 512 (Hard disks/Floppy disks), click OK.
14. Click on goldcard.img tab. Go to Edit tab > Select All, edit tab again > copy.
15. Click on the “removable disk” tab. Select offset (line) 00000000 till offset (line) 00000170 (including the 00000170 line), click on Edit tab and then Paste Write.
16. Click on File > Save. now you can exit the program.
------------
17. Now with the gold card created (the microSD transformed) we must reboot the HTC Tattoo. When we press the "reboot" button we must press nearly at the same time the POWER OFF and VOLUME DOWN buttons at the SAME TIME!!!! He will enter a new menu called HBOOT
18. We press back button to go to fastboot USB mode
19. Now we have to start the flashing utility for example: http://rapidshare.com/files/292517090/RUU_Click_HTC_WWE_1.67.405.6_WWE_release_signed_NoDriver.exe
This is done the 19th Decembre 2009, but maybe on the future there will be newer flash releases so this file will be replaced for the newer one.
19.1 If we get either Error 170 or 171 in the flashing process follow this other guide to solve this issue: http://forum.xda-developers.com/showthread.php?t=646663
20. The Flash will start we must wait, its better to do this process with 100% battery left
21. After 10 minutes, the flash will be done, and the HTC will reboot automatically with the Flashing done and everything OK!
-----------------------
Latest Official WWE Flashes for HTC Tattoo:
19.12.2009: http://rapidshare.com/files/292517090/RUU_Click_HTC_WWE_1.67.405.6_WWE_release_signed_NoDriver.exe
This is for all brand of HTC Tattoo? or only Orange?
can get root?
I have successfully flashed my tattoo with your tutorial but still can't use my Wind (italian) sim. At every roboot it ask me the unlock code, says "network succesful unlocked" and after it continue to say "unlocking sim card", but it never stops!!
The data of my phone are those:
HBOOT-0.52.0001
MICROP-0203
RADIO-3.35.07.20
What can I do??
Tony2k do you have your simlock unlock code? Or did you just flash your rom hoping for the simlock to go away?
I have bought the unlock code but the problem it's that I can enter another code, like 12345678, and have always the message "network unlocked successful" and after it continue to say "unlocking sim card", exactly like with code that I have bought.
Well Tony I am sorry but I cant help you here. I dont know whats wrong. I know that you have few trials to enter the simlock unlock code and that after exceeding these attempts you will have to remove the simlock via USB cable (I dont know which software to use). What you can try is using a turbo sim that you can get off ebay. I dont give you my word that it will work, but I have seen one or two people saying that it worked with the tattoo locked to orange uk. If ever you decide to try using the turbo sim, let me know if it bypasses the simlock on the tattoo.
Good luck man.
Great work MiSSigNNo.... u managed to carry out this impossible work as of now with success....
i have few questions to ask you. what made you flash your tattoo???
what advantage do you have at present over the previous ROM???
have u got into superuser mode with this procedure???
i am sure we all would like to know answers for these from you.... please be kind enough to reply to my post....
Manuvaidya:
1. To remove simlock successfully on orange uk htc tattoo, you are forced to flash the rom
2. If you were on orange uk, you will have an android with all the software that orange removed and it will be debranded. And knowing that it can be flashed this will encourage ppl to cook roms.
3. Unfortunately there is no way yet to get root access on the tattoo
Hope this helps you out mate
manuvaidya said:
Great work MiSSigNNo.... u managed to carry out this impossible work as of now with success....
i have few questions to ask you. what made you flash your tattoo???
what advantage do you have at present over the previous ROM???
have u got into superuser mode with this procedure???
i am sure we all would like to know answers for these from you.... please be kind enough to reply to my post....
Click to expand...
Click to collapse
No advantages actually, simply I hate much the mobile-branded roms. Also I tried my sim before I flashed to enter the unlock code and nothing happened, but after, I tried and then it asked me for the unlock code and I could manage to make it successfully.
I don't have the root-superuser mode. I'm sure there are plenty of opportunities with that, but we must look forward on finding the method to make it.
By the way In my "experience" with past branded-roms, they used to be slower since they had plenty of ****ty apps of the brand to make you spend money, and waste unnecesarily memory from the device, this is why the first two things I do everytime I buy an HTC is to flash to default rom and unlock them Since it was more difficult than other times with WM I decided to make this mini-guide, to help others make it easier.
Hi Guys,
I got to the last stage of this walkthrough and when i run the exe for the ROM i get an error 170 on the USB cable. Do you have any ideas what this could be?
Thanks
James
apie2004 said:
Hi Guys,
I got to the last stage of this walkthrough and when i run the exe for the ROM i get an error 170 on the USB cable. Do you have any ideas what this could be?
Thanks
James
Click to expand...
Click to collapse
You didn't make the goldcard correctly. start from the beginning on the goldcard creation. to know if gold card is well created when entering hboot, press the unlock button (call button if i can remember) and there you will se a green message like "key is OK" if not well made there will be a message in red saying "key error" or something like that
Thanks for that guys, still no luck though . I think I might be doing something wrong so here are the results i get as i go along.
adb shell =035344535530324780010f90d4009868
reverse code=009800d4900f01804732305553445303
goldcard.img=
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 53 41 30 30 00 00 00 00 00 00 00 2C 00 00 00 00 00 00 00 00 00 00 06 00 00 23 00 00 00 00 00 00 00 00 00 68 00 00 00 00 00 00 00 13 00 00 00 84 00 00 00 00 00 00 00 00 00 00 00 00 24 00 00 00 00 00 00 00 18 00 00 29 00 00 00 00 00 FA 00 00 BE 00 00 00 00 19 00 00 00 00 00 00 43 2B BA AA 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 06 00 00 21 FF FF FF FF FF FF FF FF 00 00 00 00 53 41 30 30 00 00 00 EF 00 83 80 00 00 3B 00 00 52 00 00 71 00 00 00 00 00 00 04 00 00 09 00 00 38 00 00 00 00 B4 83 00 00 5E 00 00 00 00 00 00 00 07 00 00 00 00 D2 00 00 00 00 20 00 45 3B 00 00 00 81 00 00 00 00 00 DD 00 98 06 00 00 00 00 00 00 DE 00 00 00 00 00 3B 00 3C 00 82 53 5A 82 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
I keep getting the same results over and over again so I think I might be going wrong somewhere... Any more ideas?
I'm afraid I'm stuck near the very beginning.
When I navigate to the sdk tools folder and run the command, I get the following:
Code:
C:\android-sdk-windows\tools>adb shell cat /sys/class/mmc_host/mmc1/mmc1:*/cid
adb server is out of date. killing...
* daemon started successfully *
error: device not found
Is there something I'm doing wrong? I'm running Win 7 x64 and trying to flash a Vodafone branded HTC (build number is apparently "1.67.161.5 CL#74011 release-keys").
Edit: I did format the card to FAT32 like you said.
I found that you need the andriod drivers installed for adb shell to work, if you run SDK setup in the andriod sdk folder and install the driver component, then point the device in device manager towards the new downloaded folder, should be called usb_driver. Hope that helps
Well I tried opening SDK Setup but all that happened was a command prompt window just appeared and then disappeared almost instantly (with Windows then complaining that the program might not have installed correctly). I also tried running it as administrator but got the same result. And nothing happens when I try opening it with cmd.
apie2004 said:
Thanks for that guys, still no luck though . I think I might be doing something wrong so here are the results i get as i go along.
adb shell =035344535530324780010f90d4009868
reverse code=009800d4900f01804732305553445303
goldcard.img=
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 53 41 30 30 00 00 00 00 00 00 00 2C 00 00 00 00 00 00 00 00 00 00 06 00 00 23 00 00 00 00 00 00 00 00 00 68 00 00 00 00 00 00 00 13 00 00 00 84 00 00 00 00 00 00 00 00 00 00 00 00 24 00 00 00 00 00 00 00 18 00 00 29 00 00 00 00 00 FA 00 00 BE 00 00 00 00 19 00 00 00 00 00 00 43 2B BA AA 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 06 00 00 21 FF FF FF FF FF FF FF FF 00 00 00 00 53 41 30 30 00 00 00 EF 00 83 80 00 00 3B 00 00 52 00 00 71 00 00 00 00 00 00 04 00 00 09 00 00 38 00 00 00 00 B4 83 00 00 5E 00 00 00 00 00 00 00 07 00 00 00 00 D2 00 00 00 00 20 00 45 3B 00 00 00 81 00 00 00 00 00 DD 00 98 06 00 00 00 00 00 00 DE 00 00 00 00 00 3B 00 3C 00 82 53 5A 82 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
I keep getting the same results over and over again so I think I might be going wrong somewhere... Any more ideas?
Click to expand...
Click to collapse
I also tried a couple of other cards, one broke the card and hboot was really unresponsive. The first card did the same sort of thing, CID error or similar
Success!
I read through this guide about getting adb to work, replaced the current driver with the one linked to there and then also realised that you couldn't get adb to work while the phone was in 'Disk Drive' mode (what a n00b I am). The only way I could get into 'USB Debugging' was by choosing 'HTC Sync' on the phone (but not actually have HTC Sync open on my PC). Once I did that, adb worked properly.
I'm guessing my mistake was just not having the phone in 'USB Debugging', so the old driver would probably have worked as well but at this point I don't really care.
Anyway, I managed to follow the rest of your guide just fine, MiSSigNNo, and it worked! Though I think maybe you should rewrite point number 17 in your original post; from the way you worded it, I thought there was an actual reboot button, different from the power button. A better wording would be something like: "Switch the phone off. Press the Power button to switch it back on but immediately hold down the Volume Down button after pressing the Power button until the HBoot menu appears (at which point you can let go of Volume Down)"
Otherwise I have no complaints, and I cannot thank you enough for posting the guide. It's so nice to be able to get rid of network branding (even if it was only slight in the case of Vodafone), and have a newer version of the system!
Do you know where we can keep track of the WWE Flash releases? It'd be nice to stay up to date I guess.
Edit: lol silly me, wasn't actually checking the rest of the forum so didn't see the thread on WWE ROM links.
what brand of sd card did you use? It's just that i've read somewhere that sandisk (the one i have) doesnt work as a goldcard. Tried it with one that didnt have a brand on it and that didnt work either
I used a SanDisk (it's the 2GB card that came with the phone) so it can't be true that all SanDisk cards don't work. Not that I know much about these things.
I AM NEW HERE.
I use MTTY to change diamond's macadress.
enter"emapiWlanMac 00 00 00 00 00 00"
but it returns "command error!!!".
it said that different SPL have different commands.
my spl is spl1.93
someone may tell a right commond having the same effect of "emapiWlanMac 00 00 00 00 00 00".
thanks.
CYHTCY said:
I AM NEW HERE.
I use MTTY to change diamond's macadress.
enter"emapiWlanMac 00 00 00 00 00 00"
but it returns "command error!!!".
it said that different SPL have different commands.
my spl is spl1.93
someone may tell a right commond having the same effect of "emapiWlanMac 00 00 00 00 00 00".
thanks.
Click to expand...
Click to collapse
Why do you want to change it?
I have an LG G4 with no warranty as it was bought refurbished in Abu Dhabi. The phone was a really good one until I installed the OTA update on 5th April 2017. I had absolutely no probelms before. The next day the boot looping started and it is still there. I tried Factory Reset, Wipe Cache , they didn't work, the boot looping ensued. Then I learnt about Flashing Stock Firmware using LG Flash Tools . Downloaded all needed files and felt this would solve the problem but an error shows up during downloading Stockware Via USB.
the process of LG Flash Tool stops at 9%, 18 seconds saying
_prepareAfterDload download
00000064
:: Error ::
DoDownload Error!!!
The log txt file of the Flash Tool shows at last after recognition of device
[02:28:78] [Model Name] Binary(LGLS991), Target(LGLS991)
[02:28:94] [T000032] 4F 50 45 4E 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 8E 36 00 00 B0 AF BA B1 OPEN.....................6......
[02:28:453] [R000032] 46 41 49 4C 0A 01 00 80 00 00 00 00 00 00 00 00 00 00 00 00 20 00 00 00 00 00 00 00 B9 BE B6 B3 FAIL............................
[02:28:453] Invalid command response[02:33:484] [T000032] 45 58 45 43 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 12 00 00 00 E8 D3 00 00 BA A7 BA BC EXEC............................
[02:33:500] [R000032] 46 41 49 4C 0A 01 00 80 00 00 00 00 00 00 00 00 00 00 00 00 20 00 00 00 00 00 00 00 B9 BE B6 B3 FAIL............................
[02:33:500] Invalid command response[02:33:500] ErrorType : 0x2000
[02:33:500] Port Close
[02:33:500] Error Code = 0x2000, Invalid command response[02:33:500] DoDownload() Exception
[02:33:500] Port is already closed
and this happened many times.... tried different Stock Firmwares (LS991VZ5 (base version), LS991VZ9 (marshmellow OS)) from this website "storage cow"
.
.
I had no issues with the phone whatsoever before the firmware update. Few Reports have been surfacing. How do I install the stock firmware?
Please help, big financial investment , From Developing Country
.
anishkhadgi4xda said:
I have an LG G4 with no warranty as it was bought refurbished in Abu Dhabi. The phone was a really good one until I installed the OTA update on 5th April 2017. I had absolutely no probelms before. The next day the boot looping started and it is still there. I tried Factory Reset, Wipe Cache , they didn't work, the boot looping ensued. Then I learnt about Flashing Stock Firmware using LG Flash Tools . Downloaded all needed files and felt this would solve the problem but an error shows up during downloading Stockware Via USB.
the process of LG Flash Tool stops at 9%, 18 seconds saying
_prepareAfterDload download
00000064
:: Error ::
DoDownload Error!!!
The log txt file of the Flash Tool shows at last after recognition of device
[02:28:78] [Model Name] Binary(LGLS991), Target(LGLS991)
[02:28:94] [T000032] 4F 50 45 4E 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 8E 36 00 00 B0 AF BA B1 OPEN.....................6......
[02:28:453] [R000032] 46 41 49 4C 0A 01 00 80 00 00 00 00 00 00 00 00 00 00 00 00 20 00 00 00 00 00 00 00 B9 BE B6 B3 FAIL............................
[02:28:453] Invalid command response[02:33:484] [T000032] 45 58 45 43 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 12 00 00 00 E8 D3 00 00 BA A7 BA BC EXEC............................
[02:33:500] [R000032] 46 41 49 4C 0A 01 00 80 00 00 00 00 00 00 00 00 00 00 00 00 20 00 00 00 00 00 00 00 B9 BE B6 B3 FAIL............................
[02:33:500] Invalid command response[02:33:500] ErrorType : 0x2000
[02:33:500] Port Close
[02:33:500] Error Code = 0x2000, Invalid command response[02:33:500] DoDownload() Exception
[02:33:500] Port is already closed
and this happened many times.... tried different Stock Firmwares (LS991VZ5 (base version), LS991VZ9 (marshmellow OS)) from this website "storage cow"
.
.
I had no issues with the phone whatsoever before the firmware update. Few Reports have been surfacing. How do I install the stock firmware?
Please help, big financial investment , From Developing Country
.
Click to expand...
Click to collapse
Because u can't use any firmware other than zvf u can hard brick your device. Man read please.
There's a chance of no solution for a while as there is no zvd zve or zvf .tots out yet.
Kinda out of luck
Download the update again and save to sd. recovery
Apply update from sd
Thanks
But then which version would be at least required? D , E or F?
If I apply from sdcard which version should I try?
I didnt know about the issue...... one "ok" and you can lose your phone!!!!!!
anishkhadgi4xda said:
Thanks
But then which version would be at least required? D , E or F?
If I apply from sdcard which version should I try?
I didnt know about the issue...... one "ok" and you can lose your phone!!!!!!
Click to expand...
Click to collapse
I dont know the qfuse versions of d e or f so i would start with f cause some downgrades did hard brick.
TheMadScientist said:
Because u can't use any firmware other than zvf u can hard brick your device. Man read please.
There's a chance of no solution for a while as there is no zvd zve or zvf .tots out yet.
Kinda out of luck
Download the update again and save to sd. recovery
Apply update from sd
Click to expand...
Click to collapse
is there any update about this . How can I know if it is released?
leoimg.nbh said:
is there any update about this . How can I know if it is released?
Click to expand...
Click to collapse
I dont know. I know there is a zvi now from what i understand. Look in the general section maybe a .tot or kdz for it
What is your exact case so I have an idea of whats up.
There is a zvi tot in the gen section u can use to restore stock. But once u use it u will probly never be able to downgrade again. But its there
I have a bootloop and my lg is zvf ....
Can I use zvi.tot in my lg..
Also I can't find zvi in general section:crying::crying:
leoimg.nbh said:
I have a bootloop and my lg is zvf ....
Can I use zvi.tot in my lg..
Also I can't find zvi in general section:crying::crying:
Click to expand...
Click to collapse
Yes. Lgup zvi
https://forum.xda-developers.com/sprint-g4/general/zvi-tot-available-t3683618
Just remember no dowgrade after. Zvi thats it....
TheMadScientist said:
Yes. Lgup zvi
https://forum.xda-developers.com/sprint-g4/general/zvi-tot-available-t3683618
Just remember no dowgrade after. Zvi thats it....
Click to expand...
Click to collapse
any help please
message Error --failed previousload () ----
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
leoimg.nbh said:
any help please
message Error --failed previousload () ----
Click to expand...
Click to collapse
Did u follow the lgup guide on the main g5 threads setup with uppercut and all?