Database Develop

HardSpl ends up in "Error [270]: Update Error"

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.

Imagio 040 SPL

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.​

HOW-TO Flash the Tattoo

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.

HOW TO CHANGE MACADRESS?(about MTTY)

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?

Samsung Galaxy Mini GT-S5570 Bootloop

Hello.
Today I tried rooting and flashing a custom rom to my smartphone. The rooting process was completed normally, superuser was up etc. Installed Rom Manager but didn't flash CWM from there because I couldn't find my device name so I found it independently from here. Afterwards I tried flashing a CM 10.1 rom (Android 4.2.1), so I booted into recovery. Had a problem with backing up my rom so I proceeded (although I have a backup of my files from Titanium). Wiped data/cache and flashed the rom but then I forgot to REwipe data/cache and rebooted, resulting into a bootloop, with the samsung logo coming up, then the samsung galaxy animation, then repeat. Also, I could not enter recovery mode to wipe, because even after pressing the button combo the phone would skip to the samsung boot screen.
After that I tried multiple things:
1.Flashed CWM through Odin 4.38 independently. (File obtained from http://forum.xda-developers.com/showthread.php?t=1342190)
2.Flashed Stock Froyo rom. (File obtained from http://samsunggalaxyreview2.blogspot.gr/2011/05/samsung-galaxy-mini-s5570-original.html)
3.Flashed Stock Gingerbread rom (File obtained from http://yagyagaire.blogspot.gr/2011/08/upgrade-samsung-galaxy-popmini-gts5570.html#.UYmCjqJA3RM)
After Googling my problem and searching the forums I saw that most people got their issue fixed by either entering recovery (something I can't do), or flashing a different rom (which I did but to no avail).
So now I'm stuck with a device unable to fully boot successfully but with a working Download mode (the phone is accepted by Odin).
I don't know if this is what "bricking" is called but I definitely need help, either by a tutorial, link, instructions, etc. Anything you provide will be helping.
Also: it may sound stupid but is there a difference between s5570 and GT-s5570? If yes then probably the mistake is on my part and I'm sorry for making this thread.
Thank you very much.
Alexziab
EDIT: My initial stock version was Froyo 2.2.1

The first mistake you do is, you flashed Froyo over Gingerbread. Which NOT recommended.
Second, you flashed CM10.1 in stock recovery, another NOT recommended.
Third, GT-S5570 is S5570.
Fourth, that's not bootloop, that's Softbrick. Bootloop is looping in bootscreen, NOT bootsplash.

Reply
I see. Thank you for replying. Do you know any way to fix this problem?
EDIT: CM 10.1 was flashed after flashing the CWM recovery for Froyo 2.2.1, not stock recovery.

AlexZiab said:
I see. Thank you for replying. Do you know any way to fix this problem?
EDIT: CM 10.1 was flashed after flashing the CWM recovery for Froyo 2.2.1, not stock recovery.
Click to expand...
Click to collapse
You should have flashed cwm recovery over gingerbread, not on froyo.:what:
Sent Via XDA™ Premium

Reply
Galaxy_Rohit said:
You should have flashed cwm recovery over gingerbread, not on froyo.:what:
Sent Via XDA™ Premium
Click to expand...
Click to collapse
You see, I originally had Froyo. Flashed CWM on it through a thread here on xda (link above) then flashed 10.1.
Gingerbread was flashed later, in an attempt to recover the phone.

AlexZiab said:
You see, I originally had Froyo. Flashed CWM on it through a thread here on xda (link above) then flashed 10.1.
Gingerbread was flashed later, in an attempt to recover the phone.
Click to expand...
Click to collapse
Send it to SSC, they'll know what to do.

recovery problem with mini 2
I have a problem with GALAXY MINI 2, stock rom, stock kernel, rooted, TWRP recovery
I only tried CWM and TWRP, when I reboot into recovery from RomManager or QuickBoot I cannot reboot system, allways reboots into recovery, only other things that let's me do is power off and bootloader, is this a bug from something in stock kernel or something else ? for the moment I do not wish to flash something else in it
only thing that I could do to resolve this problem is to reflash recovery and autoboot from odin, all works ok now beside booting into recovery other way than power off and using hard keys, and it is damn hard to keep pressed that combination, and 90% from tryes I get power off, it shows TWRP screen and powers off
any ideas ?

grigtm said:
I have a problem with GALAXY MINI 2, stock rom, stock kernel, rooted, TWRP recovery
I only tried CWM and TWRP, when I reboot into recovery from RomManager or QuickBoot I cannot reboot system, allways reboots into recovery, only other things that let's me do is power off and bootloader, is this a bug from something in stock kernel or something else ? for the moment I do not wish to flash something else in it
only thing that I could do to resolve this problem is to reflash recovery and autoboot from odin, all works ok now beside booting into recovery other way than power off and using hard keys, and it is damn hard to keep pressed that combination, and 90% from tryes I get power off, it shows TWRP screen and powers off
any ideas ?
Click to expand...
Click to collapse
Go make a separate thread ! This isn't a ASKING THREAD !

Reply
F4uzan said:
Send it to SSC, they'll know what to do.
Click to expand...
Click to collapse
Can't I fix it by myself? My warranty has expired since 2012 so they will probably charge to fix it.

AlexZiab said:
Can't I fix it by myself? My warranty has expired since 2012 so they will probably charge to fix it.
Click to expand...
Click to collapse
No, you can't.

Fixed!
Followed this tutorial here on youtube: /watch?v=dU80AYnzf6g
After following the instructions, the phone finally booted! Language was set to (probably) russian but switched it to english and now I have a normally working (for now) phone! I don't see any problems with it! I guess the problem is solved. Thank you all for your support in any way!
Sorry for dodging the "link posting" rule that says that I should make 10 posts before posting a link. I have no intention to spam or anything, hope you understand.

AlexZiab if you don't now what you are doing just don't do it , buy a new phone and be careful next time
Sent from my GT-S5570 using xda app-developers app

SamsungGalaxyMiniPro said:
AlexZiab if you don't now what you are doing just don't do it , buy a new phone and be careful next time
Sent from my GT-S5570 using xda app-developers app
Click to expand...
Click to collapse
You know what. I have flashed about 30 phones or more but It never happened to me that phone was stuck at bootloop until this phone. AlexZiab made a mistake but we all do mistakes sometimes so I do and you will aswell. He just asked for help. If you dont have any answer you should just be quiet and let somebody else to help. Your post looks like AlexZiab is some stupid guy or whatever. Nobody is so smart as you are probably :laugh: . If he dont made that mistake he will not know next time. We are all learning every day. If we dont do mistakes we will be stupid, You know.

Boot-Loop resurrection - I am stucked
Hi All,
I've a S5570, and seems soft bricked after some
- probably - mistyped dd.
Now it is in boot-loop. . .
I can enter DM but stock ROM-s won't help.
I've managed to get into this baby using openocd
but stucked at identifying the OneNAND flash on-board.
Code:
> arm9 mww 0xa0a000e0 0x00000000
> arm9 mww 0xa0a0000c 0x00000004
> arm9 mww 0xa0a00000 0x0000000b
> arm9 mww 0xa0a00010 0x00000001
> arm9 mdw 0xa0a00014
0xa0a00014 00000020
> arm9 mdw 0xa0a00040
0xa0a00040 00d100d1
>
The Id returned is öxööd1ööd1 but sould be 0x5500bcec or something.
The dump of the controller region seems OK:
Code:
> arm9 mdb 0xa0a00000 0x0x100
0xa0a00000 0b 00 00 00 01 f1 00 00 00 f2 01 f1 04 00 00 00 ................
0xa0a00010 00 00 00 00 20 00 00 00 00 00 00 00 20 00 00 00 .... ....... ...
0xa0a00020 1a 00 d4 aa bd 01 21 00 00 00 00 00 00 00 00 00 ......!.........
0xa0a00030 1a 00 d4 aa bd 01 21 00 06 00 00 10 00 00 00 00 ......!.........
0xa0a00040 d1 00 d1 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
0xa0a00050 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
0xa0a00060 00 00 00 00 00 09 00 00 00 00 00 00 00 00 00 00 ................
0xa0a00070 80 47 80 47 a0 03 a0 03 b9 11 b9 11 a0 85 a0 85 .G.G............
0xa0a00080 20 c0 20 c0 20 c0 20 c0 20 c0 20 c0 00 00 00 00 . . . . . .....
0xa0a00090 00 00 00 00 00 08 00 00 00 00 00 00 00 00 00 00 ................
0xa0a000a0 00 00 00 00 00 00 00 00 00 00 00 00 0d 00 00 00 ................
0xa0a000b0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
0xa0a000c0 41 f2 20 f2 00 00 00 00 00 00 00 00 00 00 00 00 A. .............
0xa0a000d0 90 70 ff f0 00 00 80 00 94 00 f3 00 e0 40 00 00 [email protected]
0xa0a000e0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
0xa0a000f0 ff 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
Now what?
Is it a hard-brick?
Regards
M5

Separate thread
meres5 said:
Hi All,
I've a S5570, and seems soft bricked after some
- probably - mistyped dd.
Now it is in boot-loop. . .
I can enter DM but stock ROM-s won't help.
I've managed to get into this baby using openocd
but stucked at identifying the OneNAND flash on-board.
Code:
> arm9 mww 0xa0a000e0 0x00000000
> arm9 mww 0xa0a0000c 0x00000004
> arm9 mww 0xa0a00000 0x0000000b
> arm9 mww 0xa0a00010 0x00000001
> arm9 mdw 0xa0a00014
0xa0a00014 00000020
> arm9 mdw 0xa0a00040
0xa0a00040 00d100d1
>
The Id returned is öxööd1ööd1 but sould be 0x5500bcec or something.
The dump of the controller region seems OK:
Code:
> arm9 mdb 0xa0a00000 0x0x100
0xa0a00000 0b 00 00 00 01 f1 00 00 00 f2 01 f1 04 00 00 00 ................
0xa0a00010 00 00 00 00 20 00 00 00 00 00 00 00 20 00 00 00 .... ....... ...
0xa0a00020 1a 00 d4 aa bd 01 21 00 00 00 00 00 00 00 00 00 ......!.........
0xa0a00030 1a 00 d4 aa bd 01 21 00 06 00 00 10 00 00 00 00 ......!.........
0xa0a00040 d1 00 d1 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
0xa0a00050 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
0xa0a00060 00 00 00 00 00 09 00 00 00 00 00 00 00 00 00 00 ................
0xa0a00070 80 47 80 47 a0 03 a0 03 b9 11 b9 11 a0 85 a0 85 .G.G............
0xa0a00080 20 c0 20 c0 20 c0 20 c0 20 c0 20 c0 00 00 00 00 . . . . . .....
0xa0a00090 00 00 00 00 00 08 00 00 00 00 00 00 00 00 00 00 ................
0xa0a000a0 00 00 00 00 00 00 00 00 00 00 00 00 0d 00 00 00 ................
0xa0a000b0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
0xa0a000c0 41 f2 20 f2 00 00 00 00 00 00 00 00 00 00 00 00 A. .............
0xa0a000d0 90 70 ff f0 00 00 80 00 94 00 f3 00 e0 40 00 00 [email protected]
0xa0a000e0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
0xa0a000f0 ff 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
Now what?
Is it a hard-brick?
Regards
M5
Click to expand...
Click to collapse
Someone said it before on this same thread, and I'm going to say it again. This is NOT a Q&A thread. If you have a question regarding a problem, make a separate thread. If you don't follow the rules, we are not obliged to help. Simple as that
Cheers

NP
Probably I misunderstood the titles:
> Legacy & Low Activity Devices > Samsung Galaxy Mini > Galaxy Mini Q&A, Help & Troubleshooting >
Sorry for that. . .
Seems I had better to buy a riffbox and do not disturb the "developers"...
(in the URL above)
Lynuxen said:
Someone said it before on this same thread, and I'm going to say it again. This is NOT a Q&A thread. If you have a question regarding a problem, make a separate thread. If you don't follow the rules, we are not obliged to help. Simple as that
Cheers
Click to expand...
Click to collapse

meres5 said:
Hi All,
I've a S5570, and seems soft bricked after some
- probably - mistyped dd.
Now it is in boot-loop. . .
I can enter DM but stock ROM-s won't help.
I've managed to get into this baby using openocd
but stucked at identifying the OneNAND flash on-board.
Code:
> arm9 mww 0xa0a000e0 0x00000000
> arm9 mww 0xa0a0000c 0x00000004
> arm9 mww 0xa0a00000 0x0000000b
> arm9 mww 0xa0a00010 0x00000001
> arm9 mdw 0xa0a00014
0xa0a00014 00000020
> arm9 mdw 0xa0a00040
0xa0a00040 00d100d1
>
The Id returned is öxööd1ööd1 but sould be 0x5500bcec or something.
The dump of the controller region seems OK:
Code:
> arm9 mdb 0xa0a00000 0x0x100
0xa0a00000 0b 00 00 00 01 f1 00 00 00 f2 01 f1 04 00 00 00 ................
0xa0a00010 00 00 00 00 20 00 00 00 00 00 00 00 20 00 00 00 .... ....... ...
0xa0a00020 1a 00 d4 aa bd 01 21 00 00 00 00 00 00 00 00 00 ......!.........
0xa0a00030 1a 00 d4 aa bd 01 21 00 06 00 00 10 00 00 00 00 ......!.........
0xa0a00040 d1 00 d1 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
0xa0a00050 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
0xa0a00060 00 00 00 00 00 09 00 00 00 00 00 00 00 00 00 00 ................
0xa0a00070 80 47 80 47 a0 03 a0 03 b9 11 b9 11 a0 85 a0 85 .G.G............
0xa0a00080 20 c0 20 c0 20 c0 20 c0 20 c0 20 c0 00 00 00 00 . . . . . .....
0xa0a00090 00 00 00 00 00 08 00 00 00 00 00 00 00 00 00 00 ................
0xa0a000a0 00 00 00 00 00 00 00 00 00 00 00 00 0d 00 00 00 ................
0xa0a000b0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
0xa0a000c0 41 f2 20 f2 00 00 00 00 00 00 00 00 00 00 00 00 A. .............
0xa0a000d0 90 70 ff f0 00 00 80 00 94 00 f3 00 e0 40 00 00 [email protected]
0xa0a000e0 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
0xa0a000f0 ff 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
Now what?
Is it a hard-brick?
Regards
M5
Click to expand...
Click to collapse
We all make mistakes reading and remembering. I believe that this thread was in dev section and it was moved but he remembered it veing at the wrong place. We are all tires at the end of the year. Me too. My PC is about to die and I'm rarely in good mood nowdays.
Sent from my GT-S5570 using xda premium

An apology for my behavior
meres5 said:
Probably I misunderstood the titles:
> Legacy & Low Activity Devices > Samsung Galaxy Mini > Galaxy Mini Q&A, Help & Troubleshooting >
Sorry for that. . .
Seems I had better to buy a riffbox and do not disturb the "developers"...
(in the URL above)
Click to expand...
Click to collapse
I am deeply sorry for my behavior, and even more sorry that you misunderstood me.
You are in the right section. When I said this isn't a Q&A thread I meant it wasn't from the likes of this, meaning you post a question and you get an answer. But here you posted your question on another person's thread. This thread was created to by him to help him solve his problem by anyone who knows what that specific problem is. And you just walk right in here and start asking what's wrong with your device. Having a separate thread for your problem is mandatory in a case like this.
Second, I am not a developer. Am trying though. So you don't have to take my word for it, since obviously I have no right of telling what's wrong or what's right since I've never developed anything, right? Here is the same meaning in a different sentence by a person who is experienced here.
F4uzan said:
Go make a separate thread ! This isn't a ASKING THREAD !
Click to expand...
Click to collapse