Develop Bugs

Bricked please help me!

I downloaded superwipe for my phone and ran it and it cleared my phone but the rom I put on the sd card is not showing up so I cant download it!
It is stuck on the black screen with just google on it help!!!
I downloaded a clockmod recovery from the rom manager before I did this but I have no idea how to fix this!!!

How about downloading a rom to your computer and transfer it to the sd card?

Its not showing up on my mac...
How can I get it to show up?

badd99 said:
I downloaded superwipe for my phone and ran it and it cleared my phone but the rom I put on the sd card is not showing up so I cant download it!
It is stuck on the black screen with just google on it help!!!
I downloaded a clockmod recovery from the rom manager before I did this but I have no idea how to fix this!!!
Click to expand...
Click to collapse
You are having exactly the same reaction i've had when i had my first bootloop on my HTC Desire, thanks for the laughs
Super Wipe cleans EVERYTHING, including your SDCARD. Dont worry, your phone is not bricked.
The easiest way for you to boot your phone is to flash a stock image with fastboot or CWM. Follow this great guide:
http://forum.xda-developers.com/showthread.php?t=1392310

haha, Im freaking out
On that guide what part should I follow? I used it to gain root and unlock the boot loader but where on there am I actually going to be restoring it?

if there is a way I can send a .zip file to my phone then I can easily install it form my phone...If only you could remove the sd card!!
That guide seems to tell you how to flash everything...nothing how to restore it.

flakz0r said:
You are having exactly the same reaction i've had when i had my first bootloop on my HTC Desire, thanks for the laughs
Super Wipe cleans EVERYTHING, including your SDCARD. Dont worry, your phone is not bricked.
The easiest way for you to boot your phone is to flash a stock image with fastboot or CWM. Follow this great guide:
http://forum.xda-developers.com/showthread.php?t=1392310
Click to expand...
Click to collapse
Super wipe lite does not wipe the virtual SD card. OP you probably have to flash stock images in fast boot, there is no restoring.
Sent from my Galaxy Nexus using xda premium

Please explain how to do this....
Found someone else did this and the guy who makes the rom posted this:
1. Change ROM name to rom.zip
adb shell
mount /data
exit
adb push rom.zip /data/media
Now reboot into recovery and flash ROM.
Problem is I have no real idea how to do all of this. If anyone could write up how to do it (im on a mac, but can use a pc if have too) then I would SERIOUSLY love them. You have to know the feeling of your brand new phone on day one not working

http://code.google.com/android/nexus/images.html
I believe you put this image on the root of your pc drive, either use adb or fast boot and push it in terminal.

can you explain how to use fastboot to do this? I need steps to follow since im new at android flashing...thank you!

you have to ADB push a rom to your phone.
Send it to the update directory and you can flash it with stock image.

Okay so how do I ADB push a rom?

badd99 said:
can you explain how to use fastboot to do this? I need steps to follow since im new at android flashing...thank you!
Click to expand...
Click to collapse
http://rootzwiki.com/topic/12069-guide-last-resort-fix-for-unfixable-bootloopingpseudo-brickedbricked-phones/

Did I brick my Galaxy s3?

Well.. in a nutshell, I installed CWM recovery, rooted the phone by installing the update from the "SD Card" when it was really the phone's internal memory, and all worked well. The original idea was to edit some .prop file in /system through a root file explorer. Basically, I changed a value as one stupid tutorial suggested which ended up causing the phone to boot in to a black screen. The phone goes in to recovery and D/l mode, but the problem is flashing ANY type of ROM to the phone. Odin is useless because you can only attach .tar, .gzip, .smd,... etc.. and the roms are usually in a .zip format. This means I need to get the .zip rom on to the phone's "Sd card" which is just internal memory and should clearly specify so. I can't exactly access my phone's memory afaik since.. you know.. the phone doesn't have any OS to boot up.
Now what is it that I can do to get a rom on the phone? Android commander is another useless program right now, also. Aside from the program always telling me my rooted phones aren't rooted, the program doesn't even detect the phone while it's in dl mode, recovery mode, bricked mode, garabge mode,... you get the point. I'm just a little irritated after trying for two days to get in to my own internal storage. If anyone has anything to share, and decides to share it, thanks a lot.

bump it would be nice for someone to help....

Nothing is flashing because you changed the ro.build props. There are stock Odin roms floating atound, or you can remove the device check from the updater script in the zips you download and then try to flash.
Sent from my SGH-T999 using xda premium

Or if you have adb you can push back stock build prop back to /system
Sent from my SGH-T999 using xda premium

All these suggestions I read on googled pages from people having similar issues are just such perfect ideas. I wish they worked, though. I have tried pretty much everything.
Since my last post I:
- Wiped every cache you can dream of
- Flashed boot-stock-tmobile-sgh-t999 probably 4 different times, and did the above step after each failure.
- Tried every possible way to get in the "external sd card" meaning "my phone's internal memory"
- Tried pulling the build.props, however without a valid operating system, I'm not going to get very far.
- Looked ALL OVER the internet for a STOCKY RECOVERY ROM in a .tar format. I don't see why it's too much to ask to be able to simply flash a rom from the pc odin since I'm pretty sure I won't be using odin mobile without first getting adroid booted up some how.
Yes, I disabled auto reboot in odin, I've tried pretty much everything and I really don't know where else to turn.

In android updater scripts there is a check into make sure you're flashing the correct phone. If the file is missing, it's going to fail this check and not flash.
If you unzip a Rom and modify this it should work.
On second thought,
You should follow the thread about returning to stock. That has an Odin flash able image that should get you booting again and then you can restart the process to root your phone.
Sent from my SGH-T999 using xda premium

I had that same problem I was only able to go to download mode so I used Odin and flashed stock tmo file to unroot the phone I can't remember exactly what it was called and it worked just fine and now I'm rooted again on cm10 and it works perfectly
Sent from my SGH-T999 using xda app-developers app

boot into recovery with the phone plugged into your computer. then open cmd (if in windows) and cd to the directory with a different rom then do
adb push xxx.zip /sdcard/
wait for it to finish then reboot recovery and flash the rom.

jellydroid13 said:
boot into recovery with the phone plugged into your computer. then open cmd (if in windows) and cd to the directory with a different rom then do
adb push xxx.zip /sdcard/
wait for it to finish then reboot recovery and flash the rom.
Click to expand...
Click to collapse
It's failing getprop ro.build.device
It's gonna do that even with pushing a new Rom to the sdcard unless those lines are removed from updater script.
Sent from my SGH-T999 using xda premium

similar problem, but long story short I can't boot into recovery and flashing through ODIN gets me an "unsupport dev_type" message and no results. Any suggestions?

The super obvious suggestion is to just restore your nandroid backup. Before any mod always make one that's in good shape. Every guide tells you to do this but you didn't mention it. Did you not make one? If you can get into recovery and/or DL mode then I'm pretty sure you are not bricked though.

the-Mike_D said:
If you can get into recovery and/or DL mode then I'm pretty sure you are not bricked though.
Click to expand...
Click to collapse
exactly. something's not being done right.

dyuhas1 said:
similar problem, but long story short I can't boot into recovery and flashing through ODIN gets me an "unsupport dev_type" message and no results. Any suggestions?
Click to expand...
Click to collapse
After seeing this OP, are you saying you can NOT get into d/l mode? also, look under devices on win machine, do you see an entry QLOAD*** if so you can NOT and will not get to d/l mode. It is hard bricked. time to get a jtag service. Stop wasting time looking for an answer and get it fixed. again, if you can not get into d/l mode, this is my suggestion. I HAVE BEEN THERE, DONE THAT. BTW, I have the usb jig, IT WILL NOT WORK on hard brick. hehe used it several times on soft bricks though.
Good luck.

Here is a French company doing that rescue service for bricked Galaxy S3 by JTAG
Réparer brick Galaxy S3

Wow, here is a quick and fast service. Get the usbjiig also for future soft-bricks.
MobileTechVideos.COM
http://mobiletechvideos.mybigcommerce.com/

Galaxy Nexus Bricked

My nexus is from everyway shape or form bricked. I tried all forms of fixing it:
-Tried flashing stock image from fastboot
-tried flashing stock through odin
-tried flashing through recovery
-tried locking and unlocking the bootloader
What I noticed: I can flash different kernels and mods. But as soon as I try to flash a ROM that I already had saved on the SD it cancels the install and shows "(bad)". I also cannot mount /system to format it.
Also, when I try to flash anything thru odin or fastboot, everything works according to ODIN and I get the blue "PASS" sign, but when it reboots nothing sticks. I was able to use the Toolkit v7.8 to boot into TWRP recorvery, and it still doesnt work. NOTE: I can only boot into it with the Toolkit, I cant actually flash the recovery permanently.
I guess the system files became Read-Only.
I have no ROM currently loaded so I can only boot into Download mode/Fastboot and CWM recovery.

Things to try
acesofbelkan said:
My nexus is from everyway shape or form bricked. I tried all forms of fixing it:
-Tried flashing stock image from fastboot
-tried flashing stock through odin
-tried flashing through recovery
-tried locking and unlocking the bootloader
What I noticed: I can flash different kernels and mods. But as soon as I try to flash a ROM that I already had saved on the SD it cancels the install and shows "(bad)". I also cannot mount /system to format it.
Also, when I try to flash anything thru odin or fastboot, everything works according to ODIN and I get the blue "PASS" sign, but when it reboots nothing sticks. I was able to use the Toolkit v7.8 to boot into TWRP recorvery, and it still doesnt work. NOTE: I can only boot into it with the Toolkit, I cant actually flash the recovery permanently.
I guess the system files became Read-Only.
I have no ROM currently loaded so I can only boot into Download mode/Fastboot and CWM recovery.
Click to expand...
Click to collapse
It looks like you've tried just about everything and you are very capable of getting it done. My only suggestion is that when I thought I was bricked, I kept wiping all the data I could find. From CWM I started with a wipe data/factory reset and that had the best results for me. After that, wipe dalvik, wipe battery stats, and I tried loading a new ROM from sdcard. I wouldn't try to install a new kernel or any other mod until you successfully boot into your new(or old) ROM.
Like I said, you probably already knew all of this but I wanted to make sure all the bases were covered. If it doesn't help you, I hope it at least helps someone else. Good luck, and please post your progress!

try using fastboot to erase the system and other partition.
fastboot erase system
fastboot erase userdata
faseboot erase boot
fastboot erase recovery
Then flash stock from fastboot

Ok, I try the fast boot method today after work. I have a feeling it wont work until I can mount the system folder which is the sole problem if Im not mistaken. I wiped absolutely everything I could in CWM to no avail. So fastboot looks like the only choice

acesofbelkan said:
Ok, I try the fast boot method today after work. I have a feeling it wont work until I can mount the system folder which is the sole problem if Im not mistaken. I wiped absolutely everything I could in CWM to no avail. So fastboot looks like the only choice
Click to expand...
Click to collapse
Fastboot does not require mounting of anything -- it writes to the entire partition.

efrant said:
Fastboot does not require mounting of anything -- it writes to the entire partition.
Click to expand...
Click to collapse
I don't have the best knowledge when it comes to this. But if this is true then perhaps I lost root? When I was flashing a Rom my phone shut off and that's when these problems started. Would losing root be the cause of this?

acesofbelkan said:
I don't have the best knowledge when it comes to this. But if this is true then perhaps I lost root? When I was flashing a Rom my phone shut off and that's when these problems started. Would losing root be the cause of this?
Click to expand...
Click to collapse
No. Root has nothing to do with fastboot. Root has nothing to do with your device. Root has to do with the Android build that you are running.
When you are booted into the bootloader (i.e., fastboot mode), there is no Android OS running, so how can there be root?
The fastboot executable on your PC interacts directly with the bootloader, and it will wipe an entire partition, or write an image to a partition.

first off you need to download wugfresh's Gnex toolkit:
http://forum.xda-developers.com/show....php?t=1766475
second you need to install all the drivers if you haven't already.
then you need to choose your model type
after you will need to click on back to stock what it does is it resets everything, assuming your phone cant boot up choose not booting
once that is done you can choose the factory image which can be downloaded from Googles factory images or you can use the options provided
after that you follow all the steps provided in the tool kit. the tool kit is mostly automatic so it wont take allot of time.
once that is done you are back in stock and have lost everything but don't fret because you can root it again using the same tool kit.
quick point your phone still has an unlocked boot loader so don't worry about that.
once youve completed the above steps you should be back to your good old galaxy nexus home screen

NoorGnex said:
[snip]
first off you need to download wugfresh's Gnex toolkit
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1469909

efrant said:
http://forum.xda-developers.com/showthread.php?t=1469909
Click to expand...
Click to collapse
I've personally never had problems with tool kits and have found them very helpful, because of my busy schedule I don't have the time to do it myself even with my amateur coding skills, and have found only people who dont understand what there getting themselves into get bricked, thats not to say you cant brick your phone if your smart but if your smart you would have done a nandroid before flashing anything.
thanks again for that enlightening post

NoorGnex said:
first off you need to download wugfresh's Gnex toolkit:
http://forum.xda-developers.com/show....php?t=1766475
Click to expand...
Click to collapse
Link is bringing up a 404 error. Did the toolkit move locations?

JackG058 said:
Link is bringing up a 404 error. Did the toolkit move locations?
Click to expand...
Click to collapse
sorry
http://forum.xda-developers.com/showthread.php?t=1766475

NoorGnex said:
sorry
http://forum.xda-developers.com/showthread.php?t=1766475
Click to expand...
Click to collapse
Thanks. I'm prepping for doing a ROM tomorrow night so trying to do my due diligence now.

JackG058 said:
Thanks. I'm prepping for doing a ROM tomorrow night so trying to do my due diligence now.
Click to expand...
Click to collapse
This is what you should be reading for due diligence...

efrant said:
This is what you should be reading for due diligence...
Click to expand...
Click to collapse
I will add this to my reading list, and send you my kind thanks.
edit: And bookmarking, of course.

I tried WugFresh's toolkit, everything was flashed(at least thats what the program said). But when the phone reboots, nothing, just logo screen

acesofbelkan said:
I tried WugFresh's toolkit, everything was flashed(at least thats what the program said). But when the phone reboots, nothing, just logo screen
Click to expand...
Click to collapse
That's what I was trying to get across earlier...
Use this: http://forum.xda-developers.com/showthread.php?t=1626895 That way, you can see where you are having issues.
And in case you missed it earlier: http://forum.xda-developers.com/showpost.php?p=30015315&postcount=9

NoorGnex said:
first off you need to download wugfresh's Gnex toolkit:
http://forum.xda-developers.com/show....php?t=1766475
second you need to install all the drivers if you haven't already.
then you need to choose your model type
after you will need to click on back to stock what it does is it resets everything, assuming your phone cant boot up choose not booting
once that is done you can choose the factory image which can be downloaded from Googles factory images or you can use the options provided
after that you follow all the steps provided in the tool kit. the tool kit is mostly automatic so it wont take allot of time.
once that is done you are back in stock and have lost everything but don't fret because you can root it again using the same tool kit.
quick point your phone still has an unlocked boot loader so don't worry about that.
once youve completed the above steps you should be back to your good old galaxy nexus home screen
Click to expand...
Click to collapse
Only after you learn what is going on in the background.
I think i'm going to stop trying to help people using toolkits if it seem that they did not even bordered to read up on fastboot and adb..

efrant said:
http://forum.xda-developers.com/showthread.php?t=1469909
Click to expand...
Click to collapse
+1

acesofbelkan said:
I tried WugFresh's toolkit, everything was flashed(at least thats what the program said). But when the phone reboots, nothing, just logo screen
Click to expand...
Click to collapse
This quote pretty much defines why people hate toolkits.

Stuck at bootscreen, can't enter CWM

I'm experiencing some issues. I flashed a bad rom and now I'm stuck at boot screen (google logo). I can enter fastboot, but I can't get into CWM. I've tried the nexus toolkit, but the ADB drivers won't function.
What do I do next?

Hope I haven't bricked my phone...

If you can enter fast boot then your phone is not bricked. Read up on how the flash the stock Google image using fast boot. You will loose all you data but you will have a working phone again.
Sent from my Galaxy Nexus using xda premium

Ok, the problem is that suddenly my computer won't see the phone as an ADB device. I've tried every usb driver I can find. I've tried the PDAnet, but I won't install properly when I can't enter the rom and tick the usb debugging mode.

killbox said:
Ok, the problem is that suddenly my computer won't see the phone as an ADB device. I've tried every usb driver I can find. I've tried the PDAnet, but I won't install properly when I can't enter the rom and tick the usb debugging mode.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1626895

I managed to get into CWM
What I'm actually trying to do is to restore a cwm backup I made before I sent my device to repair the usb port.
So far I've figured out that you must be using a ICS rom to be able to restore a ICS backup right?

killbox said:
I managed to get into CWM
What I'm actually trying to do is to restore a cwm backup I made before I sent my device to repair the usb port.
So far I've figured out that you must be using a ICS rom to be able to restore a ICS backup right?
Click to expand...
Click to collapse
Not necessarily but you will need to format/wipe data if restoring a different OS version.
Sent from my Galaxy Nexus using xda premium

Ok, will I loose everything on SD card then? included cwm backups?

killbox said:
Ok, will I loose everything on SD card then? included cwm backups?
Click to expand...
Click to collapse
Nah only app+data. Your "SD Card" will be fine.

Ok, tried that.
I get:
Error while restoring /system!
I'm not quite sure, but I think the rom I'm trying to restore is ARHD 4.1.0, while the one I have now is ARHD 6.1.0

killbox said:
Ok, tried that.
I get:
Error while restoring /system!
I'm not quite sure, but I think the rom I'm trying to restore is ARHD 4.1.0, while the one I have now is ARHD 6.1.0
Click to expand...
Click to collapse
Did you ever figure out how to fix this??
I just ran into a similar dilemma and have yet to fix it.
On my Verizon Galaxy Nexus, I had Vicious Jellybean V.5
Starting acting up.
Made a backup using CW.
Went to recovery.
Wiped the device for a clean install.
Then went to use the toolkit and the drivers wont install properly..
FML.
I can boot into FASTBOOT, CWM recovery, and ODIN. But Google logo is as far as it gets when I try to get into android..
I'm using the latest version of Galaxy Nexus Toolkit V.7.8
Any way to flash using Odin?? Way back when, there was something like odin that I used for my Droid X.. Does that exist?
PLEASE HELP :\

mikeright25 said:
Did you ever figure out how to fix this??
I just ran into a similar dilemma and have yet to fix it.
On my Verizon Galaxy Nexus, I had Vicious Jellybean V.5
Starting acting up.
Made a backup using CW.
Went to recovery.
Wiped the device for a clean install.
Then went to use the toolkit and the drivers wont install properly..
FML.
I can boot into FASTBOOT, CWM recovery, and ODIN. But Google logo is as far as it gets when I try to get into android..
I'm using the latest version of Galaxy Nexus Toolkit V.7.8
Any way to flash using Odin?? Way back when, there was something like odin that I used for my Droid X.. Does that exist?
PLEASE HELP :\
Click to expand...
Click to collapse
If you can boot into recovery you can just flash a ROM onto your phone. If for some reason you don't have one then just boot to recovery, go to mounts and storage, mount the SD card, then you should be able to put a ROM on there and flash it.
For future reference I would personally stay away from the toolkit. It's convenient but there isn't really a substitute for knowing how to do everything yourself =]
If you need more help feel free to PM me!

foxehkins said:
If you can boot into recovery you can just flash a ROM onto your phone. If for some reason you don't have one then just boot to recovery, go to mounts and storage, mount the SD card, then you should be able to put a ROM on there and flash it.
For future reference I would personally stay away from the toolkit. It's convenient but there isn't really a substitute for knowing how to do everything yourself =]
If you need more help feel free to PM me!
Click to expand...
Click to collapse
Hey,
Thanks so much for the quick response! Unfortunately, the biggest problem lies in the fact that I am unable to push anything to CWM recovery because my computer wont install the driver properly and I've been trying to figure out a way to do that or push a file to the phone for 6 hrs now
When I did a factory reset and wiped cache it actually deleted the backup that I made and everything else..
So I need to find a way to get a zip file on to the phone to flash or figure out how to get this driver working. Maybe a different computer.. Ugh.
I've been looking into ODIN and such, But this is so frustrating. Can't believe I made such a rookie mistake.
-Mike

mikeright25 said:
Did you ever figure out how to fix this??
I just ran into a similar dilemma and have yet to fix it.
On my Verizon Galaxy Nexus, I had Vicious Jellybean V.5
Starting acting up.
Made a backup using CW.
Went to recovery.
Wiped the device for a clean install.
Then went to use the toolkit and the drivers wont install properly..
FML.
I can boot into FASTBOOT, CWM recovery, and ODIN. But Google logo is as far as it gets when I try to get into android..
I'm using the latest version of Galaxy Nexus Toolkit V.7.8
Any way to flash using Odin?? Way back when, there was something like odin that I used for my Droid X.. Does that exist?
PLEASE HELP :\
Click to expand...
Click to collapse
If you can go to CWM, AND you have fastboot and adb files, you can always push one of the ROM to sdcard via "adb push ROM_NAME.zip /sdcard/"
If you don't have adb and fastboot files, just google them. It wouldn't be hard to find

mikeright25 said:
Hey,
Thanks so much for the quick response! Unfortunately, the biggest problem lies in the fact that I am unable to push anything to CWM recovery because my computer wont install the driver properly and I've been trying to figure out a way to do that or push a file to the phone for 6 hrs now
When I did a factory reset and wiped cache it actually deleted the backup that I made and everything else..
So I need to find a way to get a zip file on to the phone to flash or figure out how to get this driver working. Maybe a different computer.. Ugh.
I've been looking into ODIN and such, But this is so frustrating. Can't believe I made such a rookie mistake.
-Mike
Click to expand...
Click to collapse
Did your computer recognize the device before? If so then you shouldn't need to reinstall the drivers. PM me and I can try to wlk you through it over gtalk or something.
---------- Post added at 04:05 PM ---------- Previous post was at 03:58 PM ----------
The drivers can also be found here. http://dl.dropbox.com/u/15110285/FYA Files/GNexus-root-package-FYA.zip

Have you tried downloading the drivers again?
Sent from my Galaxy Nexus using xda app-developers app

Change operating systems..
Just uninstall all drivers, reboot, feed it the same driver again.

bk201doesntexist said:
Change operating systems..
Just uninstall all drivers, reboot, feed it the same driver again.
Click to expand...
Click to collapse
Thanks guys for the ideas
But, yes my computer used to recognize the Nexus just fine.
Now, tried all usb ports didn't work, and trying it in my old computer (with the 32bit version of win7 instead of x64) gave a pnpui.dll error (which I'm going to assume means plug n play user interface error).
The first kind of fresh idea is using ADB commands [good thought], but I haven't used those since I first got it, when the nexus was released.
And I believe, in that case the drivers will still need to be recognized..Right?
I'm going to try going through the precise steps in the WugToolkit for installing the drivers, but I have a feeling that something that affects the drivers may have been wiped when I did the whole factory reset/cache wipe (to an already corrupt version of jellybean)
Any other ideas guys?

mikeright25 said:
Thanks guys for the ideas
But, yes my computer used to recognize the Nexus just fine.
Now, tried all usb ports didn't work, and trying it in my old computer (with the 32bit version of win7 instead of x64) gave a pnpui.dll error (which I'm going to assume means plug n play user interface error).
The first kind of fresh idea is using ADB commands [good thought], but I haven't used those since I first got it, when the nexus was released.
And I believe, in that case the drivers will still need to be recognized..Right?
I'm going to try going through the precise steps in the WugToolkit for installing the drivers, but I have a feeling that something that affects the drivers may have been wiped when I did the whole factory reset/cache wipe (to an already corrupt version of jellybean)
Any other ideas guys?
Click to expand...
Click to collapse
I recommend using this package by 1wayjonny. It works perfectly and, unlike most other packages, 1wayjonny’s repack does not install any crapware along with it. That said, it doesn’t include an .exe file, so it needs to be installed manually from the .inf file. If you do not now how to do that, see here for instructions.

killbox said:
Ok, the problem is that suddenly my computer won't see the phone as an ADB device. I've tried every usb driver I can find. I've tried the PDAnet, but I won't install properly when I can't enter the rom and tick the usb debugging mode.
Click to expand...
Click to collapse
Just a quick FYI "adb" is only accessible once booted up to the rom.

[Very serious]Non-booting/non-changing/not working problem

I woke up today to a bootloop. After pulling out the battery, I cant turn it on, it was stuck at the google logo. I thought it was some rom issue or something. When I had the time, in the afternoon, I just boot to recovery, and wiped data+sd card. Turns out sd card was not wiped.
Just now, I found a way to boot it. (AFTER WIPING DATA) I used the gnex toolkit and boot with insecure image, and guess wat? My old rom boots. Everything was the way it was, and then it crashed and stuck on the google logo again.(I made sure i wiped things two to three times, data and sd) I did a few experiments:
1) Flash using ODIN
2) Flash CWM using toolkit--it changed back to twrp after reboot
3) Changing the icon on my homescreen after boot--- everything was the same again after booting
4) Flash stock image using toolkit
5) Wipe data using manual adb
6) Try to lock my bootloader
Everything I tried changing, change back to the original state after reboot. What is the problem?
Device: Galaxy Nexus
ROM: Purity 7 sept release
Kernel: Fancy r42
Logs in twrp are showing updating partition, not FAIL. So I really don't think there is a need to show the recovery log.
HELP ME!

are you flashing your recovery or just booting the recovery?
fastboot oem unlock
fastboot flash recovery recovery.img
use ClockWorkMod. I've heard nothing but problems with TWRP.

player911 said:
are you flashing your recovery or just booting the recovery?
fastboot oem unlock
fastboot flash recovery recovery.img
use ClockWorkMod. I've heard nothing but problems with TWRP.
Click to expand...
Click to collapse
umm, i can boot recovery. i cannot flash cwm. i tried, but when i reboot, it went back to twrp.
what is oem unlock for? coz its smth i havent tried.

jacktay94 said:
umm, i can boot recovery. i cannot flash cwm. i tried, but when i reboot, it went back to twrp.
what is oem unlock for? coz its smth i havent tried.
Click to expand...
Click to collapse
Oem unlock will unlock your bootloader and wipe the internal storage in the process. I saw you didn't use fastboot. You could try that. Flash the Factory image via fastboot. If that fails try omap flash.
Sent from my Galaxy Nexus using XDA Premium HD app

mrgnex said:
Oem unlock will unlock your bootloader and wipe the internal storage in the process. I saw you didn't use fastboot. You could try that. Flash the Factory image via fastboot. If that fails try omap flash.
Sent from my Galaxy Nexus using XDA Premium HD app
Click to expand...
Click to collapse
Yup,I tried it already thru toolkit. Not working either.

Dude the toolkit blows, flash back to stock manually via adb command prompt. There are tutorials around here on how to do it. It's guaranteed to work if you don't screw it up.
Honestly flashing back to stock via adb should be something everyone should learn if you plan on flashing roms.

SoHaunted said:
Dude the toolkit blows, flash back to stock manually via adb command prompt. There are tutorials around here on how to do it. It's guaranteed to work if you don't screw it up.
Honestly flashing back to stock via adb should be something everyone should learn if you plan on flashing roms.
Click to expand...
Click to collapse
i did adb bro, its the last thing i tried, i learnt and try.
Sent to Samsung centre, they told me its my flash IC thats blown. sobs