Develop Bugs

"Major" error after flashing ICS Kernel - pls help

Hello,
I wanted to get some flavour of ICS and decided to flash an ICS Rom.
First I got the new ICS Kernel from DoomLord as I like his kernels.
After flashing and wanting to go into recovery the screen simply stayed black.
So I took the stock ICS Kernel provided with the Rom, but it had the same effect.
After that I reflashed the Gingerbread Kernel I had before, but here also: black screen.
The only thing left to do is reflash the Stockrom, so I started up flashtool.exe and did the normal steps.
Unfortunately I got the following error message:
FlashTool said:
29/041/2012 06:41:51 - ERROR - ERR_SEVERITY="MAJOR";ERR_CLASS="MEMORY_CLASS";ERR_STATIC="HASH_VER";ERR_DYNAMIC="Block verification failed";
Click to expand...
Click to collapse
ERR_Severity="Major" don't sound good
But maybe someone can help me pls.
EDIT: Posted in wrong forum, pls move to development

are you getting any messages in fastboot when you flash a kernel? And I presume you didn't backup...
sinkster©

sinkster said:
are you getting any messages in fastboot when you flash a kernel? And I presume you didn't backup...
sinkster©
Click to expand...
Click to collapse
I can flash the kernels without any hassle.
I always do Titatnium Backups and might still have an old nandroid on the sd Card.
The phone also vibrates to signify it is booting but after that I get no picture.

I'd re-download dooms kernel and try fastboot with the new file, if that's not succesful then the best idea is to spam the volume rocker as soon as you boot and see if you get the recovery screen up.

I've tried like 5 different kernels and all the same result, the screen doesnt even go on, not even the backlight, guess it's simply a brick now.

Have you tried to flash an ICS Rom again?
Else try first to use fastboot for erasing the flash partitions,
erase boot
erase system
erase userdata

harfot said:
Have you tried to flash an ICS Rom again?
Else try first to use fastboot for erasing the flash partitions,
erase boot
erase system
erase userdata
Click to expand...
Click to collapse
Is there an .FTF ICS Rom available?
I couldn't even flash the rom the first time, after flashing the new kernel I couldn't even boot into recovery.
Screen is just black.
But I will try the three things later.
Thx.

No.
Flash 2.3.4 to get it running again.
Sent from my iPad 2 using Tapatalk

Flo95 said:
No.
Flash 2.3.4 to get it running again.
Sent from my iPad 2 using Tapatalk
Click to expand...
Click to collapse
Doesnt work, that is the problem. I can't flash using flash tool as the error described in the first post appears.

Have you tried to flash an ICS Rom again?
Else try first to use fastboot for erasing the flash partitions,
erase boot
erase system
erase userdata
Click to expand...
Click to collapse
This seemed to have worked, at least it is flashing now

Gnex in reboot loop, cwm & fastboot don't work, please help Xda~eR

Guys~! I need HELP PLEASE!!!
My Gnex keeps rebooting. It will fully boot up then reboot within 1 min or so. I have wiped cache / data and re-flashed this rom under CWM. CWM will complete my request but nothing is wiped or flashed. I tried to restore CWM last backup...again it will process but nothing has changed...I tried to fastboot recovery with new img.(new CWM) The files will transfer to phone under fastboot; but again, nothing will happen with the phone itself. I don't know what to do. Please advise~!!! Thanks in advance..
I am lost now since CWM and Fastboot aren't working~! What can I do?! :crying:
Nexus GSM
4.1.1 - bigxie's JRO03C Deodexed ROM
CWM 5.5.0.2
Baseband UGLC1
Kernel 3.0.31
Build number JR003c
Bootloader PRIMELC03

go back to stock

animal24 said:
go back to stock
Click to expand...
Click to collapse
Can you suggest a WORKING way that I can go back to stock? I have tried using the Samsung Galaxy Nexus ToolKit to download, extract and flash google factory stock rom. The toolkit said flash cmpleted; however when I check the phone... nothing change.. since Fastboot does NOT work
Any other advise? Please!

Any love!?

If you have the drivers installed you could always flash back to stock using Odin? I'm guessing you do have them too since you were able to flash a ROM
Sent from my Galaxy Nexus using xda premium

[Q] Galaxy Nexus bricked after Android 4.3 upgrade

Hi guys!
As soon as Google released the factory images for our GNex I downloaded the yakju one and flashed it. All was running fine.
Then I tried to root with Galaxy Nexus Toolkit option for yakju 4.2.2
SuperSU was installed but said no su binary available.
After searching for a while I saw the Chainfire's root method was doing the job for the Galaxy Nexus with 4.3, and applied it to my Nexus.
I can't remember exactly but I think the first restart was fine but I'm not sure.
Now my Nexus is stuck in a boot loop and it can't pass the boot animation. The phone start and show the Google logo, then most of the times I can see the boot animation but suddenly it restarts and the process start again.
Things I've tried before posting:
- Full wipes
- Installing CM10.1 and Gapps from CWM Recovery.
- Restore a backup from CWM Recovery
- Clean install of factory images (takju and yakju, 4.1, 4.22, 4.3)
- Restoring the factory image with ODIN as said in the HOWTO guide in this forum.
- Factory reset with factory images (tajku and yakju, 4.2.2, 4.3) with Galaxy Nexus Toolkit
- OMAP Flash trying to restore some flash memory issues?
By now, nothing works and I'm starting to think that there might be a hardware problem with my Nexus.
So, what you think? Can anybody help me?
Thanks in advance!

have you flashed the new bootloader #4?
Sent from my Galaxy Nexus using Tapatalk 4 Beta

lovejoy777 said:
have you flashed the new bootloader #4?
Sent from my Galaxy Nexus using Tapatalk 4 Beta
Click to expand...
Click to collapse
Yes, each Android stock version or custom ROM I've tried, was with it's bootloader.
I mean, bootloader #3 for 4.2.2 and #4 for 4.3

strange. i had issues here is what i did.
fastboot flashed #4 bootloader
then fastboot reboot-bootloader
factory reset in twrp
flashed 4.3 rom
flashed chainfires root-fix
reboot
hope this helps in some way. i will post a link of the rom i used incase your version is screwed.
cheers
steve
Sent from my Galaxy Nexus using Tapatalk 4 Beta
---------- Post added at 03:07 PM ---------- Previous post was at 03:06 PM ----------
http://forum.xda-developers.com/showthread.php?t=null
Sent from my Galaxy Nexus using Tapatalk 4 Beta

lovejoy777 said:
strange. i had issues here is what i did.
fastboot flashed #4 bootloader
then fastboot reboot-bootloader
factory reset in twrp
flashed 4.3 rom
flashed chainfires root-fix
reboot
hope this helps in some way. i will post a link of the rom i used incase your version is screwed.
cheers
steve
Sent from my Galaxy Nexus using Tapatalk 4 Beta
---------- Post added at 03:07 PM ---------- Previous post was at 03:06 PM ----------
http://forum.xda-developers.com/showthread.php?t=null
Sent from my Galaxy Nexus using Tapatalk 4 Beta
Click to expand...
Click to collapse
Thank you a lot, I read you in other posts from today and yesterday looking for a solution to my problem.
By now nothing solved it, but I'll keep on trying.
All your help is welcome, thanks!

Even after installing factory image takju jwr66v I'm stuck in the boot loop:
- Google logo -> boot animation -> restart.
- (sometimes) Google logo -> restart.
I've flashed it with flash-all.bat script and manually and nothing.
Any idea?

u tried odin flash? i
Sent from my Galaxy Nexus

paarthdesai said:
u tried odin flash? i
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
Yes, I tried.
After 20 or more reboots, it showed the screen:
"Android is upgrading...
Optimizing app XX of XX"
And then, bootloop again.......
So extrange.

For me it's the same, after flashing 4.3. ALWAYS stuck at Google logo, I never even saw a bootanimation. And both TWRP and CWM can't restore a backup, when restoring data they suddenly show FAILED and they stop. Thank you Jellybean 4.3, just to try your laggy, choppy experience I'm now stuck at Google logo.

ledoweb said:
For me it's the same, after flashing 4.3. ALWAYS stuck at Google logo, I never even saw a bootanimation. And both TWRP and CWM can't restore a backup, when restoring data they suddenly show FAILED and they stop. Thank you Jellybean 4.3, just to try your laggy, choppy experience I'm now stuck at Google logo.
Click to expand...
Click to collapse
So sorry to read another case.
In mine I can see the bootanimation most of the times.
I really can't understand how the Nexus can't boot properly even after a full wipe or a factory reset using the official factory images (or after ODIN)
As I told before, I'm starting to think about hardware problems, caused or not by the 4.3 upgrade.

i just wanna make sure.
when you are flashing the factory images. are you also doing a data wipe/factory reset?
what happens if you relock then unlock? are you able to even issue the fastboot oem lock/unlock commands?
also. there has actually been times where i thought my phone was stuck forever in the bootloop. then i just let it sit(full battery) and checked it once in a while to make sure it wasnt getting too hot, and it has fixed itself. i would get worried as heck thinking that i was screwed because all the methods i tried just refused to work(including a nandroid restore with the data error mentioned above) and somehow it fixed itself and finally booted up. then once it was booted fully i went with factory img restores.

ashclepdia said:
i just wanna make sure.
when you are flashing the factory images. are you also doing a data wipe/factory reset?
what happens if you relock then unlock? are you able to even issue the fastboot oem lock/unlock commands?
also. there has actually been times where i thought my phone was stuck forever in the bootloop. then i just let it sit(full battery) and checked it once in a while to make sure it wasnt getting too hot, and it has fixed itself. i would get worried as heck thinking that i was screwed because all the methods i tried just refused to work(including a nandroid restore with the data error mentioned above) and somehow it fixed itself and finally booted up. then once it was booted fully i went with factory img restores.
Click to expand...
Click to collapse
Yes, I'm doing a wipe/factory reset before and after flashing stock factory images, and I've tried without doing any wipe and still nothing.
I can use all fastboot commands (lock, unlock included), flash custom recovery images, etc
Now, with CM10.1 without Gapps installed, sometimes the phone can complete a boot and show the lockscreen or even permit me navigate through the launcher but suddenly, it shows some airtfacts in the screen and restarts again.
Thanks!

||M^nnu|| said:
Yes, I'm doing a wipe/factory reset before and after flashing stock factory images, and I've tried without doing any wipe and still nothing.
I can use all fastboot commands (lock, unlock included), flash custom recovery images, etc
Now, with CM10.1 without Gapps installed, sometimes the phone can complete a boot and show the lockscreen or even permit me navigate through the launcher but suddenly, it shows some airtfacts in the screen and restarts again.
Thanks!
Click to expand...
Click to collapse
its sounding more and more like the time i accidentally left mine in a freezer(worked in a kitchen. set it down after using in an industrial freezer that goes -10F !! for over and hour. it just wouldnt boot. after warming up it was as if /data was corrupted. i couldnt do ANYTHING.)
i was pleasantly surprised when it just fixed itself after insane amount of tries of wipes, installs, restores.
good luck! i hope it gets back in working order.
(im also wondering if it might have something to do with the supersu install, as ive read that there has been issues with it and people not being able to get to the symlinked /data things such as the legacy symlink. have you checked to see if there is a "supersu removal" zip you can flash? just in case that helps? or maybe try to fastboot boot the 4.2.2 boot.img? wondering if installing cm10.1 and then fastboot boot the CM stock boot img just in case something isnt installing right with that)

Try fastboot erase commands instead of factory reset in recovery

Maybe this can sounds stupid but, did you check MD5 of the downloaded image? I don't know, just to discard some reasons

Sdobron said:
Try fastboot erase commands instead of factory reset in recovery
Click to expand...
Click to collapse
just DO NOT fastboot erase bootloader
lol
just had to say it.
this was gonna be the next thing i mentioned also
especially the fastboot erase data

ashclepdia said:
just DO NOT fastboot erase bootloader
lol
just had to say it.
this was gonna be the next thing i mentioned also
especially the fastboot erase data
Click to expand...
Click to collapse
Thanks haha..didn't think about anyone doing that but you never know lol.
MD5 check would be advised too.

just something to mention. when i tried to install 1st time then tried to return to 4.2 my twrp backups did not boot i tried alsorts and had to wait untill a good 4.3 rom was posted. my 1st 4.3 rom still gets stuck on bootloop. whos 4.3 have you tried?
Sent from my Galaxy Nexus using Tapatalk 4 Beta

OP what computer OS are you trying to do this from? I am wondering if something isnt flashing right due to a windows issue and as others like Sdobron mentioned check the MD5 of the tar.

lovejoy777 said:
just something to mention. when i tried to install 1st time then tried to return to 4.2 my twrp backups did not boot i tried alsorts and had to wait untill a good 4.3 rom was posted. my 1st 4.3 rom still gets stuck on bootloop. whos 4.3 have you tried?
Sent from my Galaxy Nexus using Tapatalk 4 Beta
Click to expand...
Click to collapse
i am using the shiny ota rom from baldwinguy
you can find it at rootzwiki. i dont know if its posted over here
i havent had any issues at all.(i am also now running faux kernel, he tweeted the 4.3 update just now. running awesome right now)
here is the link
http://rootzwiki.com/topic/36706-ro...tock-android-43-jss15j-no-bugs/page__st__4810

[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

[Q] boot problems cm11

im having problems upgrading to cm11 i already know how to wipe data, cahe, dalvik and install the roms the problem is it boots then on the cyanogen logo it freezes then reboots and keeps doing it ive tried factory reset redownload the rom and gapps but nothing seems to work
i am clockwork recovery 6
cm11
gapps 4.4.2 core 1-16

What exact version of cwm do you have, also try flashing the boot.img on the phone. Extract the zip, find the boot.img and place it in the root of your platform tools folder on you're computer, boot into fastboot on your phone, initiate the command: fastboot flash boot boot.img
It will send the boot. If you're on Mac do: ./fastboot flash boot boot.img
If it is a confirmed write of the boot.img, reboot the device.
Sent from my Rezound using xda-developers app. CyanogenMod 11. S-off

my clockworkmod is 6.0.3.2
Sent from my ADR6300 using Tapatalk

S-off or s-on? If s-on I would suggest flashing the boot.img via the command:
fastboot flash boot boot.img
You say you can get past the boot screen of CM 11? Its more than likely you need to flash the boot.img in fastboot.
Sent from my Rezound using xda-developers app. CyanogenMod 11. S-off

javinesteves said:
im having problems upgrading to cm11 i already know how to wipe data, cahe, dalvik and install the roms the problem is it boots then on the cyanogen logo it freezes then reboots and keeps doing it ive tried factory reset redownload the rom and gapps but nothing seems to work
i am clockwork recovery 6
cm11
gapps 4.4.2 core 1-16
Click to expand...
Click to collapse
df /system please, even tho it should be fine
I have a feeling your inc is just not stable with the cpufreq stock speeds

zachf714 said:
df /system please, even tho it should be fine
I have a feeling your inc is just not stable with the cpufreq stock speeds
Click to expand...
Click to collapse
so what do i do i get an error with fastboot that remote not allowed

javinesteves said:
so what do i do i get an error with fastboot that remote not allowed
Click to expand...
Click to collapse
your bootloader is locked, is it not ? if it is not try fastboot erase cache then flash a recovery

zachf714 said:
your bootloader is locked, is it not ? if it is not try fastboot erase cache then flash a recovery
Click to expand...
Click to collapse
my bootloader is unlocked and when i flash the boot.img it still reboots mainly when i use the playstore

javinesteves said:
my bootloader is unlocked and when i flash the boot.img it still reboots mainly when i use the playstore
Click to expand...
Click to collapse
Those things do not correlate, that has to do with the phone ram going to zip and the system not being able to reclaim it
Sent from my SCH-I535 using Tapatalk

zachf714 said:
Those things do not correlate, that has to do with the phone ram going to zip and the system not being able to reclaim it
Sent from my SCH-I535 using Tapatalk
Click to expand...
Click to collapse
so what do i do? im tired of cm7

javinesteves said:
so what do i do? im tired of cm7
Click to expand...
Click to collapse
Lower the clock speed and deal with the lag
Sent from my SCH-I535 using Tapatalk