Related
Hi.
During upgrade to Crystal V3, I get this error at the end:
Please look at attached image...
Anyone knows what the fault is?
PS. This is the new Prophet that I got as a replacement for the old, bricked one...
Regards.
Try to move the install folder to C:/
I'm not sure if it is the same error message, but months ago I had the same prob and after this it worked.
Good luck
Tried, no luck...
hifiasylum said:
Tried, no luck...
Click to expand...
Click to collapse
reset phone and restart PC.. after that install aku 2.2 and retry..
Done, no luck...
Will try with another PC. Maybe this phone is locked?
Will go on a search in the forum later tonight.
Thanks for all help.
Will make it in the end!
Regards, Lars
hifiasylum said:
Done, no luck...
Will try with another PC. Maybe this phone is locked?
Will go on a search in the forum later tonight.
Thanks for all help.
Will make it in the end!
Regards, Lars
Click to expand...
Click to collapse
In the WM6 install folder ou will find 2 .cab files.
Bring them to the mobile and install them.
After that try again.
Should work.
Did you perform step1 before running Crystal upgrade?
I had the same problem... It worked successfully on a different computer.
panda88 said:
Did you perform step1 before running Crystal upgrade?
Click to expand...
Click to collapse
Yes, I allways downgrade before I upgrade.
Really, I do.
l3v5y said:
I had the same problem... It worked successfully on a different computer.
Click to expand...
Click to collapse
I have now tried 6 different computers, no luck. Believe that the fault is that I must unlock the phone or something. Donno, maybe the easiest thing is to sell the whole phone and get one a little more "programming friendly"?
dkleuven said:
In the WM6 install folder ou will find 2 .cab files.
Bring them to the mobile and install them.
After that try again.
Should work.
Click to expand...
Click to collapse
You dont think this will in some way or the other f_ _k up my Prophet?
hifiasylum said:
You dont think this will in some way or the other f_ _k up my Prophet?
Click to expand...
Click to collapse
It shouln't!
I saw from one of the thread, somebody also has the same exact problem, this is caused by the path is too long. It is suggested to put it in C:\, which you said you have done. The other person reported that it's working after he moved the installation file. I dun understand why it wouldn't work with yours.
Here is the post, finally found it:
http://forum.xda-developers.com/showthread.php?p=1549150#post1549150
User reported the problem was solved in #318
did u unlock CID yet?
Hi again. Found the problem. It seems that I was using a somewhat corrupt downloaded rom. The rom was ok, but it must have been destroyed during the downloadprocess.
Now the phone has Gullum Touch IX installed and works like a charm.
Thank for all your help, great forum!
Regards, Lars
818pro problem during upgrade to wm6
hai..
during upgrade my dopod 818pro to wm6, suddenly blackout and my upgrading was disrupted.. i reset back my dopod 818pro to continue back my upgrading..
but, I'm facing a problem which it's just hanging at start up screen..
i already try hard reset many time, but still can't to operate..
i just want to synchronize back to my pc to continue back my upgrading...
could somebody help me to this matter.. i don't know what to do now..
if it can enter bootloader, check the wiki for recovery, and follow it through.
Messed around and tried to root a AT&T Galaxy S 2. I'm rooted but now back and search keys do not work on the bottom on the phones. I guess i need the stock AT&T kernel to flash back to?
Any help would be great thanks.
Source for the kernel has been released.just a matter of time untill the devs create something wonderfull you might look on samsungfirmware.com
I havent seen a kernel specific to the att version. Not sure if anyone has made one yet. You might be stuck untill e get one but I dont think it will be to long. Good money says D.G. Is already on it.
sent from my Infuse at Tranquility Base.
My Fault
I knew I should of waited i just wanted to run Titanium Backup
How did you get the ATT version so soon?
Sent from my GT-I9100 using XDA App
Yeah International kernels dont support bottom keys since they aren't on the Int' version so if you used one of the kernels you will need to go stock like you said or wait for DG to cook up his genius like another poster said.
This might not be the right place for this question and I know it's still very early but anyone think there'll be a way to unlock the AT&T SGS2 for other carriers? I know the Captivate could be unlocked simply by rooting and downloading an app from the market. I only ask because I'll be getting the phone on release day and I'm heading out of the country for 3 weeks. would love to use it wherever I go.
All you have to do is call ATT and ask a rep for the unlock code for your phone once you have it in your hands and they will give it to you.
Make sure to write it down and save it somewhere.
Sent from my SAMSUNG-SGH-I897 using XDA App
it's that simple? i was under the impression I had to wait 6 months for that
illmac said:
it's that simple? i was under the impression I had to wait 6 months for that
Click to expand...
Click to collapse
There may be a waiting period that i'm not sure about. I was under the impression you just had to have the phone's imei number and verification you own the phone and they would give you the unlock code on request.
Sent from my SAMSUNG-SGH-I897 using XDA App
Lol. Wondering same thing.
ronj1986 said:
How did you get the ATT version so soon?
Sent from my GT-I9100 using XDA App
Click to expand...
Click to collapse
Sent from my I897 using XDA App
Nerz said:
Lol. Wondering same thing.
Sent from my I897 using XDA App
Click to expand...
Click to collapse
Yeah, no kidding. I'm glad dg is working on it though! I sent him a PM and he never did respond though.
dayv said:
All you have to do is call ATT and ask a rep for the unlock code for your phone once you have it in your hands and they will give it to you.
Make sure to write it down and save it somewhere.
Click to expand...
Click to collapse
illmac said:
it's that simple? i was under the impression I had to wait 6 months for that
Click to expand...
Click to collapse
It is that simple. However, a lot of recent new phones had been put on 10-month exclusivity clause by AT&T that includes Captivate which means AT&T won't give you unlock code until 10 months after the phone has been released.
The normal waiting period is 90-day if you purchase on contract. But given GS2 will be on 10-month lock, you won't get your code until next summer.
post a tutorial on how to get it and ill upload it for you.
ronj1986 said:
How did you get the ATT version so soon?
Sent from my GT-I9100 using XDA App
Click to expand...
Click to collapse
First rule about fight club...
alton987 said:
Messed around and tried to root a AT&T Galaxy S 2. I'm rooted but now back and search keys do not work on the bottom on the phones. I guess i need the stock AT&T kernel to flash back to?
Any help would be great thanks.
Click to expand...
Click to collapse
Someone who has not flashed a modded kernel will have to pull it.
The good news is - you have the first step. See http://forum.xda-developers.com/showpost.php?p=17777056&postcount=42
Now that you have a rooted kernel with a stock /system, you can get a system partition dump.
Get ADB up and running, and paste the results of running the following command in an ADB shell:
Code:
mount
From that we can figure out which partition is the system partition. After that, the following command (need to put correct system partition into it) will create a system dump:
Code:
dd if=/dev/systempartitionlocation of=/sdcard/system.img bs=1M
If you upload that dump to multiupload and put the link here, someone (maybe myself, although I'm 50/50 on whether I'll actually purchase a device) can root that dump and make an Odin-flashable system partition image. This can be flashed to a phone that has the stock kernel to get root and dump the stock kernel.
Entropy512 said:
Someone who has not flashed a modded kernel will have to pull it.
The good news is - you have the first step. See http://forum.xda-developers.com/showpost.php?p=17777056&postcount=42
Now that you have a rooted kernel with a stock /system, you can get a system partition dump.
Get ADB up and running, and paste the results of running the following command in an ADB shell:
Code:
mount
From that we can figure out which partition is the system partition. After that, the following command (need to put correct system partition into it) will create a system dump:
Code:
dd if=/dev/systempartitionlocation of=/sdcard/system.img bs=1M
If you upload that dump to multiupload and put the link here, someone (maybe myself, although I'm 50/50 on whether I'll actually purchase a device) can root that dump and make an Odin-flashable system partition image. This can be flashed to a phone that has the stock kernel to get root and dump the stock kernel.
Click to expand...
Click to collapse
I have the same problem, can anyone dump a zImage and upload to somewhere? Thanks in advanced!
keeploading said:
I have the same problem, can anyone dump a zImage and upload to somewhere? Thanks in advanced!
Click to expand...
Click to collapse
zImage can't be dumped without a rooted /system.
Do you have root via kernel? If so, get a dump as described above so someone can root their /system and get the stock zImage
Entropy512 said:
Someone who has not flashed a modded kernel will have to pull it.
The good news is - you have the first step. See http://forum.xda-developers.com/showpost.php?p=17777056&postcount=42
Now that you have a rooted kernel with a stock /system, you can get a system partition dump.
Get ADB up and running, and paste the results of running the following command in an ADB shell:
Code:
mount
From that we can figure out which partition is the system partition. After that, the following command (need to put correct system partition into it) will create a system dump:
Code:
dd if=/dev/systempartitionlocation of=/sdcard/system.img bs=1M
If you upload that dump to multiupload and put the link here, someone (maybe myself, although I'm 50/50 on whether I'll actually purchase a device) can root that dump and make an Odin-flashable system partition image. This can be flashed to a phone that has the stock kernel to get root and dump the stock kernel.
Click to expand...
Click to collapse
Stop kidding yourself Entropy. You're getting this phone. You're addicted now.
I'll be getting mine tomorrow.
And my m8 is getting his the same day.
I don't get off work until 6, but I will be flashing mine with an i9100 kernel, and obtaining a system image. Then I will be flashing my m8's with that image, and dumping the zimage to flash back to my own, that is if you all haven't gotten it done by then.
Fenny said:
I'll be getting mine tomorrow.
And my m8 is getting his the same day.
I don't get off work until 6, but I will be flashing mine with an i9100 kernel, and obtaining a system image. Then I will be flashing my m8's with that image, and dumping the zimage to flash back to my own, that is if you all haven't gotten it done by then.
Click to expand...
Click to collapse
Sweet. FYI, some processing is needed to make a dumped image Odin-flashable for native ext4 phones.
http://forum.xda-developers.com/showthread.php?t=1081239
Hello,
me and my friend thought of something..
he unlocked his bootloader, and sent me his binary file
he said that once he sent his hex code, he instantly got the email for the binary code, so we think that because its so fast you might receive a general binary file to flash.
is it possible to use his binary file to unlock my bootloader??\
that way i wont have to agree wiht htc on voiding my warranty?
if so how would i flash it??
Bigv69er said:
Hello,
me and my friend thought of something..
he unlocked his bootloader, and sent me his binary file
he said that once he sent his hex code, he instantly got the email for the binary code, so we think that because its so fast you might receive a general binary file to flash.
is it possible to use his binary file to unlock my bootloader??\
that way i wont have to agree wiht htc on voiding my warranty?
if so how would i flash it??
Click to expand...
Click to collapse
Well we can do an md5sum check of the binary files to see if they are all identical but I seriously doubt that they are. I am pretty sure they use that they use the identifier token to process and produce the unlock.bin file.
Binary100100 said:
Well we can do an md5sum check of the binary files to see if they are all identical but I seriously doubt that they are. I am pretty sure they use that they use the identifier token to process and produce the unlock.bin file.
Click to expand...
Click to collapse
i think the identifier is only a way for them to better track what phone you are unlocking?
but yeah someone should check them..
should i upload his??
Bigv69er said:
i think the identifier is only a way for them to better track what phone you are unlocking?
but yeah someone should check them..
should i upload his??
Click to expand...
Click to collapse
If you want. I'm curious to see what will happen. My guess is that it'll return an error of some kind.
I've been working on trying to decompile or decode the .bin file to see if there is something to edit to give us S-OFF instead of Unlock.
Unfortunately I've been on duty for the last four days doing 12 hour shifts and when I get home I still have about three hours of reports to type up.
I'm just lucky I don't have any pending cases going to trial anytime soon so I can look into it a little more the next couple days.
When you upload the file you will probably have to zip it because I don't think you can upload .bin files on the forums.
Binary100100 said:
If you want. I'm curious to see what will happen. My guess is that it'll return an error of some kind.
I've been working on trying to decompile or decode the .bin file to see if there is something to edit to give us S-OFF instead of Unlock.
Unfortunately I've been on duty for the last four days doing 12 hour shifts and when I get home I still have about three hours of reports to type up.
I'm just lucky I don't have any pending cases going to trial anytime soon so I can look into it a little more the next couple days.
When you upload the file you will probably have to zip it because I don't think you can upload .bin files on the forums.
Click to expand...
Click to collapse
ok here it is..
check it out.. let me know
yeah thats what i was going to tell you, if someone could rewrite it or change the way it unlocks it, to give us S-off right now i would think that would be the most logical way, since they are giving us a partial unlock, maybe someone can make it into a full unlock
Bigv69er said:
ok here it is..
check it out.. let me know
yeah thats what i was going to tell you, if someone could rewrite it or change the way it unlocks it, to give us S-off right now i would think that would be the most logical way, since they are giving us a partial unlock, maybe someone can make it into a full unlock
Click to expand...
Click to collapse
Someone out there do a md5 check please?
I'm at work and shouldn't install extra stuff since I share this computer with another employee. I would like to know if they are the same.
Ok did md5 checksums they are diffrent so it will probably saw invaild unlock_code.bin if you flash but give it a try i think
His: 067e76020977d8a8f603c16d3bbf2f86
Mine: 94771323b128fd3d1689bce177f8c2f3
xboarder56 said:
Ok did md5 checksums they are diffrent so it will probably saw invaild unlock_code.bin if you flash but give it a try i think
His: 067e76020977d8a8f603c16d3bbf2f86
Mine: 94771323b128fd3d1689bce177f8c2f3
Click to expand...
Click to collapse
So just add I thought, HTC does use the token that we submit.
Sent from my HTC Amaze 4G using xda premium
xboarder56 said:
Ok did md5 checksums they are diffrent so it will probably saw invaild unlock_code.bin if you flash but give it a try i think
His: 067e76020977d8a8f603c16d3bbf2f86
Mine: 94771323b128fd3d1689bce177f8c2f3
Click to expand...
Click to collapse
Thanks X..
Aww. So should i try it?? Would it be safe?
Sent from my HTC_Amaze_4G_WHITE using xda premium
Bigv69er said:
Thanks X..
Aww. So should i try it?? Would it be safe?
Sent from my HTC_Amaze_4G_WHITE using xda premium
Click to expand...
Click to collapse
I wouldn't bother, when in doubt--there is no doubt.
^^^That has kept my phones safe for years.
TheSneakerWhore said:
I wouldn't bother, when in doubt--there is no doubt.
^^^That has kept my phones safe for years.
Click to expand...
Click to collapse
Lol yea
Sent from my HTC_Amaze_4G_WHITE using xda premium
i dont know what else to do to flash my tg01 with wp7. i tried every guide that i found in this forum but looks like notthing work for me. also jonnyhall1bmx1 helped me to fix it but there is no way. so i made a video maybe someone can help me to find what is wrong.
http://www.youtube.com/user/odino10?feature=guide
Invalid CheckSum!
Nand have bad blocks！！No way!!!
qinwengui said:
Invalid CheckSum!
Nand have bad blocks！！No way!!!
Click to expand...
Click to collapse
what u mean?
0dino said:
what u mean?
Click to expand...
Click to collapse
Nand, the flash memory on which you write your rom is corrupt, possibly permanently damaged.
Bad blocks cannot be written to.
My suggestion, try and get back to windows mobile, if thats not possible, and that wouldn't surpise me, i dunno what you should do, do you have a riff box handy?
The physical bad blocks can not erase used riff jtag box .
NO way！ You understand?
qinwengui said:
The physical bad blocks can not erase used riff jtag box .
NO way！ You understand?
Click to expand...
Click to collapse
Yes i understand, but what if? Has the OP tried? I know what bad blocks are
wait wait, u guys r confusing me.
i saw in the guides that when u get "invalid checksum" at 99% its a regular error when u flash the wp7boot.bin. why should be different for me?
Nand, the flash memory on which you write your rom is corrupt, possibly permanently damaged.
Bad blocks cannot be written to.
My suggestion, try and get back to windows mobile, if thats not possible, and that wouldn't surpise me, i dunno what you should do, do you have a riff box handy?
Click to expand...
Click to collapse
i can flash back to wm6.5 but it wont start. the phone after i flash back just run a green led for like 3 sec then go off. no i dont have riff box handy.
0dino said:
wait wait, u guys r confusing me.
i saw in the guides that when u get "invalid checksum" at 99% its a regular error when u flash the wp7boot.bin. why should be different for me?
Click to expand...
Click to collapse
NO, is not regular error at 99%- you have to wait 100 % or to flash agai- but you go to next step, to flash wp7 rom ...
mirolg said:
NO, is not regular error at 99%- you have to wait 100 % or to flash agai- but you go to next step, to flash wp7 rom ...
Click to expand...
Click to collapse
ok then, how to fix it? i tried to flash the wp7.bin again and again... but always the same error.
0dino said:
ok then, how to fix it? i tried to flash the wp7.bin again and again... but always the same error.
Click to expand...
Click to collapse
Yes, i think you have a bricked TG01 i am afraid
Unfortunately that is the risk of playing with putting WP7 on your TG01, i should imagine tens of phones have been bricked trying to do this. Its not a safe procedure, and anybody who says otherwise is not telling the truth.
its funny how i have said plenty of times not to try and flash wp7 if you are an unexperienced flasher. but yet people choose to ignore my message then i get pm messages from people telling me to fix there tg01 as they have broke it. ive helped a few people out but i do not have the time to help everyone !! so if you try to flash wp7 and you are not 100% on what you are doing and you are unexperienced etc and you brick your device and come running to me asking to fix your tg01 i will just laugh at you
jonnyhall1bmx1 said:
its funny how i have said plenty of times not to try and flash wp7 if you are an unexperienced flasher. but yet people choose to ignore my message then i get pm messages from people telling me to fix there tg01 as they have broke it. ive helped a few people out but i do not have the time to help everyone !! so if you try to flash wp7 and you are not 100% on what you are doing and you are unexperienced etc and you brick your device and come running to me asking to fix your tg01 i will just laugh at you
Click to expand...
Click to collapse
im wondering how u become so pro without testing....
im no pro sometimes some one has to take a leap of faith i think i was the second or 3rd to flash. i bricked my tg01 several times flashing wp7 because i didnt know any 1 that flashed it that could give me tips. because I risked my tg01 flashing wp7 i can now report back to unexperienced people that, wp7 is too buggy and is not worth the risk
The same experience......
I have the same ERROR!
I guess the NAND is bad.
I tried to use RIFF BOX,but cannot be restored...
I'll find a new method...
That's really a tragedy!
please am new here and really in need of assistance.
i just bought this device two weeks ago (verykool cyprus ll S6005. mt6580. kernel 3.18.19+ masrhmallow 6.0 linux
i tried to root this device with apps both via phone and pc without any result, but meanwhile i made a backup via default cwm which was just the user data since i could not gain access to root at that time. it ended with bootloop when i tried to install twrp. now in the procces of trying to get it back on track, i ended up bricking it. but still produce usb tone when connected to pc. i ended up getting rom but no image in the preloader. and the scatter file has only symbols like this ********************************** throughout. not even one word or number. And file_info also is filled with only symbol. After getting thing bit by bit from internet am at the point where where when i flash the rom, the yellow bar is 100% but this popup error:
ERROR
S_SECURITY_SECURE_USB_DL_DA_RETURN_INVALID_TYPE (6104),MSP ERROR CODE: 0X00)
the solution i tried to apply was to compare similiar device scatter text since i dont have any. thinking since they are of same model, having same kernel....might be of help.
so please i need assistance on how to get it back in working condition. thanks to you in advance.
Please anyone with link for verykool cyprus ll stock/firmware rom for me?
Sent from my SM-G950 using XDA-Developers Legacy app
a7chris said:
Please anyone with link for verykool cyprus ll stock/firmware rom for me?
Click to expand...
Click to collapse
Best would be that this verykool company would give you the right firmware for it...
Could not find s6005, but found another one from verykool - S5524, which is quite similar...
Comparison: https://www.gsmarena.com/compare.php3?idPhone1=8362&idPhone2=8213#diff-
Copied to my mega account because of the adfly crap in the link - and orig. might die someday.
https://mega.nz/#!O1clDIbY!5H-Mag22Khgmuebeezhr4PGY-peJGzWhknyanzGH1I8
(orig. came from here, https://www.needrom.com/download/stock-verykool-s5524/ )
I also saw your hovatek thread in my search results, this https://forum.hovatek.com/thread-26485.html
The partition count matches. Your pics don't show the partition table partitions.
From that S5524 you get a better scatter file. Notice that after userdata
the partition start addresses don't match. So you have to change them
accordingly. (Odd as the internal mem. size is the same...edit: seems that they are from the end <--)
Again do not tick that preloader if it works. S5524's might work or might not,
who knows.... Better avoid using it if not necessary...
BTW, make that firmware file of yours public, if you want it to be checked by someone...
CXZa said:
Best would be that this verykool company would give you the right firmware for it...
Could not find s6005, but found another one from verykool - S5524, which is quite similar...
Comparison: https://www.gsmarena.com/compare.php3?idPhone1=8362&idPhone2=8213#diff-
Copied to my mega account because of the adfly crap in the link - and orig. might die someday.
https://mega.nz/#!O1clDIbY!5H-Mag22Khgmuebeezhr4PGY-peJGzWhknyanzGH1I8
(orig. came from here, https://www.needrom.com/download/stock-verykool-s5524/ )
I also saw your hovatek thread in my search results, this https://forum.hovatek.com/thread-26485.html
The partition count matches. Your pics don't show the partition table partitions.
From that S5524 you get a better scatter file. Notice that after userdata
the partition start addresses don't match. So you have to change them
accordingly. (Odd as the internal mem. size is the same...edit: seems that they are from the end <--)
Again do not tick that preloader if it works. S5524's might work or might not,
who knows.... Better avoid using it if not necessary...
BTW, make that firmware file of yours public, if you want it to be checked by someone...
Click to expand...
Click to collapse
Whaooo. This is so kind of you. Let me try it. But I already ported the preloaded of Cyprus ii jnr S6004. Will it be right if I flash the whole of this similar device S5524? And thanks once again.
Sent from my G3221 using XDA-Developers Legacy app
a7chris said:
Whaooo. This is so kind of you. Let me try it. But I already ported the preloaded of Cyprus ii jnr S6004. Will it be right if I flash the whole of this similar device S5524? And thanks once again.
Click to expand...
Click to collapse
Nope, it might not be a good idea. There is some differences.
In S6004 there is less, so it's probably a better choice.
https://www.gsmarena.com/compare.php3?idPhone1=8363&idPhone2=8213#diff-
Though without knowing the hardwares in these, we are just guessing really...
But both probably have that same scatter you can use with that firmware of yours.
Or is it in a similar mess like its scatter?
If you haven't been able flash anything yet, you could also try to readback
the device and compare it to these different firmwares...
[*]BTW, make that firmware file of yours public, if you want it to be checked by someone...
[/LIST]
[/QUOTE]
Here is the link to the corrupted firmware verykool cyprus ll S6005
https://drive.google.com/file/d/1FkFhCpGrHjqAQ-BhltysKYdS1pK06vqQ/view?usp=sharing
I just did a terrible mistake. I mistakenly flash the whole similar rom of S5524 instead of applying scatter text or preloader with my device firmware. now device is no longer detected by pc. Any solution for this? thanks in advance
a7chris said:
[*]BTW, make that firmware file of yours public, if you want it to be checked by someone...
[/LIST]
Click to expand...
Click to collapse
Here is the link to the corrupted firmware verykool cyprus ll S6005
[/QUOTE]
Okay, checked it with a hex editor. It's all the same. Every file is just some similar
garbage like in that scatter file. Nothing useful in it...
---------- Post added at 13:12 ---------- Previous post was at 12:52 ----------
a7chris said:
I just did a terrible mistake. I mistakenly flash the whole similar rom of S5524 instead of applying scatter text or preloader with my device firmware. now device is no longer detected by pc. Any solution for this? thanks in advance
Click to expand...
Click to collapse
Removing the battery or connecting a testpoint to ground might help.
https://forum.xda-developers.com/showthread.php?t=1943442
Any hardware error probably will do..
edit: If opening the device is difficult, you might try a factory cable first.
No experience about them myself though...
https://forum.xda-developers.com/showthread.php?t=1392693
a7chris said:
I just did a terrible mistake. I mistakenly flash the whole similar rom of S5524 instead of applying scatter text or preloader with my device firmware. now device is no longer detected by pc. Any solution for this? thanks in advance
Click to expand...
Click to collapse
Oh thank God! was able to get the tone back and flash my firmware using similar device's scatter text and preloader. Thank Jesus i did not apply format and download mode. I applied download only. could been worst i guess if format and download mode was applied. All thesame. NO POWER
I flashed similar device's S5524 scatter text but still no power. You will notice that the preloader in the firmware is as well corrupt. sp flash comes up with pop up error message each time the preloader from in the firmware is been applied. (NO IMAGE IN THE PRELOADER) should i try S5524 preloader?
I would try readback the preloader and check/compare it.
Maybe your battery is totally empty???
CXZa said:
I would try readback the preloader and check/compare it.
Maybe your battery is totally empty???
Click to expand...
Click to collapse
So, to do it, you change the region to boot1 and lenght 0x40000 that you get from the scatter file.
And notice that there is 2048 bytes extra at the start when comparing the dump to the one that is in those flashable packages, S5524's, S6004's or whatever.
CXZa said:
I would try readback the preloader and check/compare it.
Maybe your battery is totally empty???
Click to expand...
Click to collapse
Thank you very much
Sent from my G3221 using XDA-Developers Legacy app
CXZa said:
I would try readback the preloader and check/compare it.
Maybe your battery is totally empty???
Click to expand...
Click to collapse
Really? If device is in bricked mode will it still be able charge the battery, despite not been able to turn on?
Sent from my G3221 using XDA-Developers Legacy app
Please how do I change the wrong flashed preloaded in my device? The similar device's preloader (veryKool Cyprus ll jnr s6004) seems to have taken over. every attempts to flash ends up with flash tool error code 4032. Thanks
Sent from my G3221 using XDA-Developers Legacy app
CXZa said:
So, to do it, you change the region to boot1 and lenght 0x40000 that you get from the scatter file.
And notice that there is 2048 bytes extra at the start when comparing the dump to the one that is in those flashable packages, S5524's, S6004's or whatever.
Click to expand...
Click to collapse
You mean in the scatter text file?
Sent from my G3221 using XDA-Developers Legacy app
Why is it that I cannot format my device with it's downloaded firmware except through similar device's firmware?
Sent from my G3221 using XDA-Developers Legacy app
a7chris said:
Why is it that I cannot format my device with it's downloaded firmware except through similar device's firmware?
Click to expand...
Click to collapse
As I said before, that firmware package of yours s6005 is total mess.
None of its files are correct, just some random garbage.
You seem to have done a lot after that mistakenly made full flash.
Hard to say what's in it if it's giving flashing errors and all...
Found possible source for s6005 firmware. Only but is the forum rules.
One cannot download until enough thanks and other activity.
But you probably can ask it anyway. Forum's language is Spanish....
https://www.clangsm.com/forum/index.php?showtopic=492197&view=findpost&p=1880525
CXZa said:
As I said before, that firmware package of yours s6005 is total mess.
None of its files are correct, just some random garbage.
You seem to have done a lot after that mistakenly made full flash.
Hard to say what's in it if it's giving flashing errors and all...
Found possible source for s6005 firmware. Only but is the forum rules.
One cannot download until enough thanks and other activity.
But you probably can ask it anyway. Forum's language is Spanish....
https://www.clangsm.com/forum/index.php?showtopic=492197&view=findpost&p=1880525
Click to expand...
Click to collapse
Whaoo. Thanks let me check it
Sent from my G3221 using XDA-Developers Legacy app
CXZa said:
As I said before, that firmware package of yours s6005 is total mess.
None of its files are correct, just some random garbage.
You seem to have done a lot after that mistakenly made full flash.
Hard to say what's in it if it's giving flashing errors and all...
Found possible source for s6005 firmware. Only but is the forum rules.
One cannot download until enough thanks and other activity.
But you probably can ask it anyway. Forum's language is Spanish....
https://www.clangsm.com/forum/index.php?showtopic=492197&view=findpost&p=1880525
Click to expand...
Click to collapse
Whaoooo. But will its firmware be able 2 correct the error?
Sent from my G3221 using XDA-Developers Legacy app