Database Develop

Messed up and need help with brick

I was running 208 ics, and wanted to jump to 217 ics with the new tool for ics only. Ran the tool with the associtated flash file and the update failed. The phone would do nothing but go into stock recovery, so like an idiot I did a factory reset. If there is way to recover the phone please let me know. Thanks.

Just fast boot back and try again.
Make sure you are using the right kernel and have it named correctly, ICSFIX.IMG iirc (though I'd check the instructions)
Sent from my Galaxy Nexus using xda app-developers app

podspi said:
Just fast boot back and try again.
Make sure you are using the right kernel and have it named correctly, ICSFIX.IMG iirc (though I'd check the instructions)
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
The program won't connect to the phone anymore. RSD will, but it fails to rewrite the OS

podspi said:
Just fast boot back and try again.
Make sure you are using the right kernel and have it named correctly, ICSFIX.IMG iirc (though I'd check the instructions)
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
Just got it to connect. I replaced the IMG file with the 213 version, of which I already have the update associted with that IMG file on my SD card. Hopefully it will work.

Looks like a go at this point. Appreciate the help.

Dont ever use rom manager

dont ever use rom manager to install recovery its 99% hard brick
SO TO BE SURE DONT USE ROM MANAGER ON YOUR MINI
Sent from my GT-S5570 using xda premium

apklike18 said:
dont ever use rom manager to install recovery its 99% hard brick
SO TO BE SURE DONT USE ROM MANAGER ON YOUR MINI
Sent from my GT-S5570 using xda premium
Click to expand...
Click to collapse
thx for the info, but it's to late, I made it today and my mini is bootlooping...

:c sooo many people are bricking their phone whith rom manager
Sent from my GT-S5570 using xda premium

I have flashed CWM via RomManager multiple times, with no problems. You only brick your device if you flash CWM that is for other devices. You can't blame RomManager for your foolishness.

For install CWM via ROM manager you need stock rom with stock recovery and with root????
Sent from my GT-S5570 using xda app-developers app

gabrielking9 said:
For install CWM via ROM manager you need stock rom with stock recovery and with root????
Sent from my GT-S5570 using xda app-developers app
Click to expand...
Click to collapse
You need root i think but dont try it dont risk it just use theupdte zip
<-------------------->
Reminders:
*Dont even use rom manager
* read instructions carefully
*use the search function
<------------------->

But we have official CWM
Sent from my GT-S5570 using xda app-developers app

Well, official CyanogenMod always have this app as the updater but I always uninstall them.

i dont know why the developers include Rom Manager even they know that it won't work and cause bricking problems

CWM supports galaxy mini!!! Dony choose different device.
Sent from my GT-S5570 using Tapatalk 2

Thanks for letting me know, I was about to try it.

Help for mini-bricks
Like others, I wish I'd read this post before I hard-bricked my phone :crying:
In my case, I just selected the "Reboot into Recovery" option, where I planned to do a nandroid backup. The screen went black and I was hard-bricked.
Anyway, I thought this might be a good thread to repost the information that restored my galaxy mini to good health.
Remove the battery, SD card and sim card.
Hold down the "Download" key combination - Volume-down + Home + Power.
While continuing to hold all three down, insert the battery (almost impossible without a friend).
Continue to hold all three down, and in about a minute, you should get you into "Download" mode, from where you can use ODIN to re-flash your phone with a stock rom.
If this doesn't work at first, keep trying; I tried it several times without success, took it to a local techo who took it to a big city techo, and it was only when they both gave up that I tried this technique again in desperation - and fortunately this time it worked.
Also, the drama was not quite over yet for my phone. When I tried to flash a stock Gingerbread rom via Odin, it failed.
That was solved by first flashing ARM11boot_GT-S5570.tar (attached) in the "Boot" section (everything else blank except for TASS_V1 ops file, which is included in the standard rom). For more information, see this thread: http://forum.xda-developers.com/showthread.php?t=1588892
After that, I successfully flashed stock Gingerbread. And finally installed CWM Recovery properly following this thread: http://forum.xda-developers.com/showthread.php?t=1342190&highlight=cwm+recovery
BE WARNED: On the thread about ARM11boot_GT-S5570.tar, there is a warning from kitrax59:
be careful on flashing the bootloader buddy.. it can hard brick your phone.. DO IT AT YOUR OWN RISK..
Click to expand...
Click to collapse
Of course, if like me, your phone was already hard-bricked, you haven't got much to lose
Anyway, I hope this helps someone else with a Rom Manager inspired hard-brick!

bump, so it won't get lost

[GUIDE] Flash Clockworkmod recovery on Galaxy Mini/Pop
apklike18 said:
dont ever use rom manager to install recovery its 99% hard brick
SO TO BE SURE DONT USE ROM MANAGER ON YOUR MINI
Click to expand...
Click to collapse
I'm guessing that a lot of these problems have a similar cause to mine, where I saw a reference to ClockWorkMod Recovery, searched for that on Google Play, and Rom Manager was the only relevant result returned.
There is an excellent guide to installing CWM Recovery by Bunnybugs_007 here: http://forum.xda-developers.com/showthread.php?t=1342190
Just wondering if there is a "sticky" function on xda? Making threads such as this one and Bunnybugs' more prominent would save a lot of heartache and hard bricks.

Still not working
even tried jtag
pls help

HetBolt said:
Still not working
even tried jtag
pls help
Click to expand...
Click to collapse
If you used ROM manager and bricked your device. Theres no way. Give it to the service center and they would replace the motherboard.

Hah I flashes cem recovery via ROM manager nothing happened .....maybe I was lucky cause I first installed it via of in and then via ROM manager just to see what happens ....
Sent from my GT-S5570 using Tapatalk 2

hsay said:
Hah I flashes cem recovery via ROM manager nothing happened .....maybe I was lucky cause I first installed it via of in and then via ROM manager just to see what happens ....
Sent from my GT-S5570 using Tapatalk 2
Click to expand...
Click to collapse
Lucky dude ! LUCKY ! LUUUCKY !
Also, bump the thread for making it useful for future.

R: Dont ever use rom manager
F4uzan said:
Lucky dude ! LUCKY ! LUUUCKY !
Also, bump the thread for making it useful for future.
Click to expand...
Click to collapse
Wat lucky,for me nothing happens too.. I think rommanager is good but extremely USELESS..
Sent from my GT-S5570 using xda app-developers app

Keep bumpin'
Preventing many bricks.

[Q] Stuck on Cm7

I recently installed CM7 following this guide (http://forum.xda-developers.com/showthread.php?t=1337105) and had no troubles at all. I soon got bored of CM7 and went to try a CM9 ROM but when I went to install it via Clockwork it failed. I tried a few others and they all failed also. I even tried to re install the stock ROM and restore from my backup but nothing worked. I'm still stuck on CM7. Anyone got any ideas of what's going wrong?
Edit 1: For example when I attempt to re install the stock ROM I get an error message saying "E:can't open /sdcard/PG32IMG.zip (bad) Installation aborted"

Bobtehblob said:
I recently installed CM7 following this guide (http://forum.xda-developers.com/showthread.php?t=1337105) and had no troubles at all. I soon got bored of CM7 and went to try a CM9 ROM but when I went to install it via Clockwork it failed. I tried a few others and they all failed also. I even tried to re install the stock ROM and restore from my backup but nothing worked. I'm still stuck on CM7. Anyone got any ideas of what's going wrong?
Edit 1: For example when I attempt to re install the stock ROM I get an error message saying "E:can't open /sdcard/PG32IMG.zip (bad) Installation aborted"
Click to expand...
Click to collapse
install Roms from inc s development section following their instructions and you should be fine. Roms are usually not in pg32img format and are not made to be installed using that method. The guide you're following also does not mention using this filename to install Roms.

In fairness, at least you're stuck on a stable Rom.
Sent from my Incredible S using Tapatalk 2

Take pg32img.zip out of the root of your SD card.
Sent from my Incredible S using xda premium

Yup, delete the PG32IMG file from your SD card or try a new radio(for better performance). You can find it in the development forum thread.
Sent from my Incredible S using xda app-developers app

Just make sure it's not a froyo rom! You don't want to brick your phone.
Sent from my Incredible S using xda app-developers app

Froyo roms wont brick your phone, however there will be no radio support unless you flash a froyo radio which will brick your phone. After saying that I doubt in any case that there are no active links to any froyo anything for the incs any more.
Sent from my Incredible S using xda premium

[Q] I957 ATT , touch screen not working after ICS upgrade

Hello,
I have gotten the stock ICS rom from samfirmware.com, Installed using ODIN and it all went green.
However, after restart the touch screen is not working !
I have tried the following:
1. First the Default (XXX) ICS rom
2. Second, the Actual ATT ICS rom
3. Flashed CWM and it is working
4. Then tried AOKP unofficial rom, not starting
No luck so far, any help is much appreciated please.

The touch screen was working after step 3?
Sent from my SAMSUNG-SGH-I727 using xda premium

wamaOnline said:
Hello,
I have gotten the stock ICS rom from samfirmware.com, Installed using ODIN and it all went green.
However, after restart the touch screen is not working !
I have tried the following:
1. First the Default (XXX) ICS rom
2. Second, the Actual ATT ICS rom
3. Flashed CWM and it is working
4. Then tried AOKP unofficial rom, not starting
No luck so far, any help is much appreciated please.
Click to expand...
Click to collapse
Do you know what rom you flashed from Sam mobile?
Sent from my SAMSUNG-SGH-I957

jd1639 said:
Do you know what rom you flashed from Sam mobile?
Sent from my SAMSUNG-SGH-I957
Click to expand...
Click to collapse
First was this one sammobile (dot) com /firmware/?page=3&model=SGH-I957&pcode=XXX&os=1&type=3#firmware[/url]
Then when it didn't work, tried this one
sammobile (dot) com /firmware/?page=3&model=SGH-I957&pcode=ATT&os=1&type=3#firmware
Sorry for the strange URL format, but seems as anew member I don't get to add URLs yet
orlandoxpolice said:
The touch screen was working after step 3?
Sent from my SAMSUNG-SGH-I727 using xda premium
Click to expand...
Click to collapse
Sorry, I meant the cwm recovery was flashed correctly and functioning
Btwi tried the fix permissions suggestion from the similar thread but no luck

What version of odin did you use? The roms look ok. If you didn't use ver 1.85 download that and re flash the Rom.
Sent from my SAMSUNG-SGH-I957

jd1639 said:
What version of odin did you use? The roms look ok. If you didn't use ver 1.85 download that and re flash the Rom.
Sent from my SAMSUNG-SGH-I957
Click to expand...
Click to collapse
It is the Odin version I have used,
One more note now, am not sure if that is normal if not.but after the latest flash ( preceded by a data wipe and format ) I can now see zip file I have placed on sdcard but can't access them for flashing and/or ad new zip files from pc

In cwm do a factory reset, wipe and format system and data and then boot. I'm hoping that will solve the problem.
Sent from my SAMSUNG-SGH-I957 using xda app-developers app

jd1639 said:
In cwm do a factory reset, wipe and format system and data and then boot. I'm hoping that will solve the problem.
Sent from my SAMSUNG-SGH-I957 using xda app-developers app
Click to expand...
Click to collapse
Tried,booted, "SAMASUNG"screen only ( as expected sicne i formatted the system ), then re-flushed the ATT ICS and same output
Am trying to get a new ROM flashed, but when the device powers up [ without me going through the wizard ], i can't write anything to SD from my PC.
Any info around here about flashing CM or AOKP using ODIN for this I957 ?

Not with Odin that I'm aware of. All are zip files and would go thru cwm. If you get only to the Samsung logo, my experience has been a factory reset usually gets you past that and if that doesn't work flashing the stock rom with Odin does. And I'd flash the honeycomb rom and bring it back to they way I bought it, then upgrade to ics
Sent from my SAMSUNG-SGH-I957 using xda app-developers app

jd1639 said:
Not with Odin that I'm aware of. All are zip files and would go thru cwm. If you get only to the Samsung logo, my experience has been a factory reset usually gets you past that and if that doesn't work flashing the stock rom with Odin does. And I'd flash the honeycomb rom and bring it back to they way I bought it, then upgrade to ics
Sent from my SAMSUNG-SGH-I957 using xda app-developers app
Click to expand...
Click to collapse
Tried the honeycomb step, still same problem
As for Booting to samsung screen .. i did format /system as suggested, so there will be no system to boot to i think

I'm at a loss, you've tried everything that has gotten me beyond the boot screen.
Anyone else have any ideas?
Sent from my SGH-I727

wamaOnline said:
Tried the honeycomb step, still same problem
As for Booting to samsung screen .. i did format /system as suggested, so there will be no system to boot to i think
Click to expand...
Click to collapse
I should mention something that has gotten me worried, i flashed a TWRP recovery to check if the touch would work there, but it didn't.
Not sure if i should be worried about HW now, or try another TWRP for instance? Or perhaps TWRP shares another flawed tab wide configuration with the Android image ?

It's not twrp, I use it on my tab and it Works fine. If you were the only one who has this problem I'd say hardware for sure. But at least one other person has the same problem after updating to ics. It seems like there something with the firmware interfacing with the touch screen.
Sent from my SAMSUNG-SGH-I957 using xda app-developers app

jd1639 said:
It's not twrp, I use it on my tab and it Works fine. If you were the only one who has this problem I'd say hardware for sure. But at least one other person has the same problem after updating to ics. It seems like there something with the firmware interfacing with the touch screen.
Sent from my SAMSUNG-SGH-I957 using xda app-developers app
Click to expand...
Click to collapse
Then why is it still borked when reverting to hc?
Sent from my SAMSUNG-SGH-I727 using xda premium

Good question. One of the guys couldn't get the touch screen to work in twrp either. It sounds like a hardware issue but to have a few guys have the same problem after installing ics? I don't know? Something's doing it which I can't figure out

jd1639 said:
Good question. One of the guys couldn't get the touch screen to work in twrp either. It sounds like a hardware issue but to have a few guys have the same problem after installing ics? I don't know? Something's doing it which I can't figure out
Click to expand...
Click to collapse
yea i dont get how a rom flash could cause a hardware issue

orlandoxpolice said:
yea i dont get how a rom flash could cause a hardware issue
Click to expand...
Click to collapse
Think the other colleague did say he found someone elsewhere who resolved the problem by reverting to an older backup he had, which gives me hope that this is no hw issue
And this was my first time to flash any ROM without a backup first, thought a stock update would be fine !!
Can I use adb for instance to verify if it was a hardware issue,if so then any help is appreciated

wamaOnline said:
Think the other colleague did say he found someone elsewhere who resolved the problem by reverting to an older backup he had, which gives me hope that this is no hw issue
And this was my first time to flash any ROM without a backup first, thought a stock update would be fine !!
Can I use adb for instance to verify if it was a hardware issue,if so then any help is appreciated
Click to expand...
Click to collapse
Got it Reassembled and cleaned it and it worked

same prob, touchscreen not responding
wamaOnline said:
Got it Reassembled and cleaned it and it worked
Click to expand...
Click to collapse
I'm having this issue of the touchscreen not responding on my s2 now
You say you got it reassembled? What did you have to do to repair it
any help greatly appreciated
I have JB 4.1.2 and cwm 9.1 flashed
after reboot screen comes on but won't respond to touch, I can only access download and recobvery screens
I also have the phone not showing on computer when usb attached but am loading rom etc to ext sd card first and installing them from cwm

Got the maintenance center to disassemble it, clean the pins and reconnect the screen and then it worked
Sent from my LT26ii using xda app-developers app

[LINKS ADDED][4.3][OTA][NAKASI-wifi] OTA UPDATE FILE

OTA [UNTESTED] [NAKASI-wifi only!]
NO GUARANTEE IF IT WILL WORK BUT NO HARM IN CHECKING THE FILES!:laugh::victory:
I WILL NOT BE RESPONSIBLE IF IT BRICKS YOUR DEVICE!!!
One Person reports it to be working.... thats good news
http://android.clients.google.com/p....signed-nakasi-JWR66V-from-JDQ39.ab67ca07.zip
LINK CREDITS-StannyG

Downloading. Wish me luck

CheCorchete said:
Downloading. Wish me luck
Click to expand...
Click to collapse
Best of Luck!! Be Really careful!! IT may not work~!

CheCorchete said:
Downloading. Wish me luck
Click to expand...
Click to collapse
How was your luck??

Seems like my pc is missing a driver, lol. But android police make a wonderfull guide with link to the ota http://www.androidpolice.com/2013/0...-to-android-4-3-jwr66v-and-root-it-right-now/

It works, got the link this am from the original post, rebooted in cmw, flashed it, over my stock rooted nexus 7. At first lost root, but found a beta of superuser flashed that with cwm and all of back to normal. Now I am running 4.3 rooted stock Rom...
Sent from my Nexus 7 using XDA Premium HD app

mk69 said:
It works, got the link this am from the original post, rebooted in cmw, flashed it, over my stock rooted nexus 7. At first lost root, but found a beta of superuser flashed that with cwm and all of back to normal. Now I am running 4.3 rooted stock Rom...
Sent from my Nexus 7 using XDA Premium HD app
Click to expand...
Click to collapse
I try to flash the zip through cwm and keep getting an error...
assert failed: apply_patch_check
instalation aborted...status 7 ...
E: error in (filename.zip)
anyone knows what´s going on? already downloaded the zip many times
i´m on stock rooted 4.2.2 LOCKED bootloader (motochopper root method)...maybe something about the bootloader?

mtdelnero said:
I try to flash the zip through cwm and keep getting an error...
assert failed: apply_patch_check
instalation aborted...status 7 ...
E: error in (filename.zip)
anyone knows what´s going on? already downloaded the zip many times
i´m on stock rooted 4.2.2 LOCKED bootloader (motochopper root method)...maybe something about the bootloader?
Click to expand...
Click to collapse
I used nrt to root my n7, I am not sure about the method you used. Also if you changed any build prop parameters, or any stock system apps, you must revert back to the original files before this ota update will work. The update will check your n7 to see if there were any mods to the original stock files. If you can't revert back to know what was changed then you may have to do a full flash of 4.2.2 then flash the update...
Try to write down the error message when you try to flash the update, that may give you some clues...
Sent from my Nexus 7 using XDA Premium HD app