Database Develop

[Q] XZ does not boot anymore after CM 10.1

Hi!
I just got a Xperia Z from a friend who try to install CM 10.1.
Apparently the bootloader is unlocked, CWM installed. And after the installation of CM, the device does not boot. Sony logo appears after a press on the start button and it turns down instantly.
What did I already try:
- Flash of two official roms with flashtool. The process stops after the progression bar is one fourth filled but nothing tells that the processus failed. But same issue always here, does not boot.
- Re-locked the bootloader with BLU (flashtool) to restore the phone with using Sony updater service : I have an error : "No loader found on this device".
Need your help please

Have you made a factory reset and cache delete before flashing CM? I make this mistake often but with flashtool I can always install back the stock rom.

wesely said:
Have you made a factory reset and cache delete before flashing CM? I make this mistake often but with flashtool I can always install back the stock rom.
Click to expand...
Click to collapse
I'm pretty sure he did a wipe data and wipe cache before the installation.
Flashtool does not repair my phone after a flash of the stock rom, do not know why..
What can I do ?

Do some research about how fastboot works to flash the official XZ kernel through fastboot
Sent from my C6603 using XDA Premium 4 mobile app

rom123s said:
I'm pretty sure he did a wipe data and wipe cache before the installation.
Flashtool does not repair my phone after a flash of the stock rom, do not know why..
What can I do ?
Click to expand...
Click to collapse
Maybe try to flash the CM kernel and go into recovery and flash a other Rom.. I'm not sure if it works but haven't better idea.

[Troubleshooting] (CM 10.2) Stuck at boot screen after reboot

Many of us are facing this problem where after flashing a 10.2 ROM and rebooting, the device is stuck at boot screen- the Samsung N7000 screen!
This is a strange problem which seems to be affecting only some n7000 handsets as others can keep flashing the ROMs without any issues...wiping, reflashing ROM, etc doesn't work!
I myself faced this problem on almost all custom CM 10.2 Roms and am sharing the solution which worked for me. At the onset, this solution was suggested to me by another member @Super Prince in one of my posts and it worked!!
1. Reboot into recovery
2. Flash the correct gapps once again
3. Reboot
The problem should be gone now and no more stuck-iness for you...
Sent from my GT-N7000 using XDA Premium 4 mobile app

I tried that, and it did not work.
I'm not using the regular Gapps package, but this one:
http://forum.xda-developers.com/showthread.php?t=2012857
What package do you use?

knedge said:
Many of us are facing this problem where after flashing a 10.2 ROM and rebooting, the device is stuck at boot screen- the Samsung N7000 screen!
This is a strange problem which seems to be affecting only some n7000 handsets as others can keep flashing the ROMs without any issues...wiping, reflashing ROM, etc doesn't work!
I myself faced this problem on almost all custom CM 10.2 Roms and am sharing the solution which worked for me. At the onset, this solution was suggested to me by another member @Super Prince in one of my posts and it worked!!
1. Reboot into recovery
2. Flash the correct gapps once again
3. Reboot
The problem should be gone now and no more stuck-iness for you...
Sent from my GT-N7000 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Really? I'll try it next time when I flash some CM based ROM and will get this problem.
I hope it is really the reason.

SirRhor said:
I tried that, and it did not work.
I'm not using the regular Gapps package, but this one:
http://forum.xda-developers.com/showthread.php?t=2012857
What package do you use?
Click to expand...
Click to collapse
Which CM version are you on? This method has worked for me every time on CM 10.2 roms and official CM 10.2 gapps (the one dated 13/08/2013)
I used to get stuck on the GT N7000 screen after every reboot and resorted to all sort of stuff like reflashing, formatting and stuff but to no avail.
The only solution that worked for me was re-flashing the gapps!
Maybe you should try once again with the official gapps..and post your results.

jakuburban said:
Really? I'll try it next time when I flash some CM based ROM and will get this problem.
I hope it is really the reason.
Click to expand...
Click to collapse
The 'Reason', my friend, remains a mystery...
This solution, though worked!
Experienced developers might like to comment on this as to what might be the reason

knedge said:
Which CM version are you on? This method has worked for me every time on CM 10.2 roms and official CM 10.2 gapps (the one dated 13/08/2013)
I used to get stuck on the GT N7000 screen after every reboot and resorted to all sort of stuff like reflashing, formatting and stuff but to no avail.
The only solution that worked for me was re-flashing the gapps!
Maybe you should try once again with the official gapps..and post your results.
Click to expand...
Click to collapse
I'm on Carbon, but I tried another CM based ROM as well and it did not work.
I will try it with the official Gapps and Slim Gapps then report back.
EDIT 1: Well. I tried the lastest Carbon nightly 10/17, with both Slim Gapps and normal regular Gapps and the same result, stuck on boot logo.
Both times I flashed a clean install. I'm out of options now.
EDIT 2: When I'm using a kernel from 4.3 and I'm on CWM trying to format Preload, I always get this message:
E:format_volume: make_extf4fs failed on /dev/block/mmcblk0p12
Error formatting /preload
Could that be a possible reason?, does anyone else have that same message?

No suggestions?
Am I'm stuck on 4.2?
Sent from my GT-N7000

It's the same for all on the new Cwm. Preload cannot be formatted in Cwm 10.2.
What happens when you clean install a rom without gapps. And boot it.?

nokiamodeln91 said:
It's the same for all on the new Cwm. Preload cannot be formatted in Cwm 10.2.
What happens when you clean install a rom without gapps. And boot it.?
Click to expand...
Click to collapse
I tried that last night actually, clean flash and no Gapps and the same result, stuck on boot screen.
What I've tried so far:
- Flashing different 4.3 ROMs with three different Gapps combinations.
- Flashing Carbon with no Gapps.
Thank you in advance for any ideas you can provide.

I have never encountered such an issue after a clean flash ever. So not sure what's going on there.
When a clean install, do you format system, data and cache and then install the new rom?

nokiamodeln91 said:
I have never encountered such an issue after a clean flash ever. So not sure what's going on there.
When a clean install, do you format system, data and cache and then install the new rom?
Click to expand...
Click to collapse
Yeah, what I do is to do a factory reset twice, then clear cache, then preload twice, data once, system twice and dalvik twice, and only then I flash the ROM and then Gapps.
I let it settle for one hour and then I start the configuration.
It is weird, because if I leave it to boot up normally for the first time, without opening any apps or configurations, it reboots normally. And only when I open Settings or an app, and then I reboot the phone, it gets stuck on the boot logo.
I've even tried to format the SD Card and no difference.

tried without the external SD card inserted?

nokiamodeln91 said:
tried without the external SD card inserted?
Click to expand...
Click to collapse
No, gonna try that tonight.
EDIT 1: Tried lastest Carbon nightly with NO Gapps and no External SD Card. Same crap.
EDIT 2: I found this thread and it basically says that I have to flash Stock, then root it and then do a factory reset.
http://forum.xda-developers.com/showthread.php?t=2427569
Sent from my GT-N7000

SirRhor said:
No, gonna try that tonight.
EDIT 1: Tried lastest Carbon nightly with NO Gapps and no External SD Card. Same crap.
EDIT 2: I found this thread and it basically says that I have to flash Stock, then root it and then do a factory reset.
http://forum.xda-developers.com/showthread.php?t=2427569
Sent from my GT-N7000
Click to expand...
Click to collapse
@SirRhor Please try anothjer work-around before you do anything else:
1. Do all the wipes from a safe kernel
2. Flash Rom (only rom and no gapps)
3. Reboot the system without gapps
4. Now, reboot into recovery (I prefer to leave the system for 10-15 minutes to settle down before rebooting)
5. Flash the correct gapps
6. Reboot and set up ur google account etc.Restore apps or whatever u need from the play store. Dabble with rom settings
7. Reboot!
Did it work now?

knedge said:
@SirRhor Please try anothjer work-around before you do anything else:
1. Do all the wipes from a safe kernel
2. Flash Rom (only rom and no gapps)
3. Reboot the system without gapps
4. Now, reboot into recovery (I prefer to leave the system for 10-15 minutes to settle down before rebooting)
5. Flash the correct gapps
6. Reboot and set up ur google account etc.Restore apps or whatever u need from the play store. Dabble with rom settings
7. Reboot!
Did it work now?
Click to expand...
Click to collapse
I haven't tried that yet, I'll do it tomorrow, but I really doubt it's going to work. I think this whole problem it's caused by errors located on some blocks of memory.
Sent from my GT-N7000

SirRhor said:
I haven't tried that yet, I'll do it tomorrow, but I really doubt it's going to work. I think this whole problem it's caused by errors located on some blocks of memory.
Sent from my GT-N7000
Click to expand...
Click to collapse
Well, can be!
Much abused handset...and much loved too!
But do give it a try!

SirRhor said:
No, gonna try that tonight.
EDIT 1: Tried lastest Carbon nightly with NO Gapps and no External SD Card. Same crap.
EDIT 2: I found this thread and it basically says that I have to flash Stock, then root it and then do a factory reset.
http://forum.xda-developers.com/showthread.php?t=2427569
Sent from my GT-N7000
Click to expand...
Click to collapse
maybe your bootloader corrupted already. Reflash the bootloader only or whole stock rom using ODIN may help ..

I'm glad to inform you that I was able to solve my problem following this guide:
http://forum.xda-developers.com/showthread.php?t=2427569
But instead of flashing the Stock Rooted ROM using Odin, I just flashed it within Philz Recovery.
Right now I'm changing settings and restarting on Carbon 4.3, and so far I have not had any problems.
To anyone experiencing this, just read this thread so you will not waste your time trying ALL the bullcrap I did and instead just try the guide above.
Thank you for everyone who helped me out.
EDIT: Maybe the OP can change the title of this thread to "FIXED" or "SOLVED".

So...which Stock Rooted ROM using to flash?...

heihei123 said:
So...which Stock Rooted ROM using to flash?...
Click to expand...
Click to collapse
Actually, I found a better more permanent solution.
Follow this guide to check for errors on the different partitions:
http://forum.xda-developers.com/showthread.php?t=1396366
Let me know if it helps.
And to answer your question, I flashed a stock ROM from Hungary I think, no problems.
EDIT: Forgot to mention, instead of using the switches described on that guide, I used -f and -y at same time.
Sent from my GT-N7000

Any custom rom - Boot loop

I've tried in twrp and cwm/cwm touch - I get a boot loop no matter which rom I flash
I made a backup of my stock 404 on cwm and twerp so It's easily reversible in either.
Similar to this post - http://forum.xda-developers.com/showthread.php?p=45795997#post45795997
It involves flashing Pi-llama 1.4 via adb and then installing the custom rom over the top.
Ran into all sorts of issues, would hang on the third data write, so I cancel it and then it would continue etc... and install
Now I'm up and running I've got half PiLlama and this rom I put on, battery drain is bad and the clock process crashes when I try and set an alarm. Otherwise it's great.
Any ideas? Seems to be the data partition causing the problems.
I'm rooted and unlocked, thought I'd add.

Flacid Monkey said:
I've tried in twrp and cwm/cwm touch - I get a boot loop no matter which rom I flash
I made a backup of my stock 404 on cwm and twerp so It's easily reversible in either.
Similar to this post - http://forum.xda-developers.com/showthread.php?p=45795997#post45795997
It involves flashing Pi-llama 1.4 via adb and then installing the custom rom over the top.
Ran into all sorts of issues, would hang on the third data write, so I cancel it and then it would continue etc... and install
Now I'm up and running I've got half PiLlama and this rom I put on, battery drain is bad and the clock process crashes when I try and set an alarm. Otherwise it's great.
Any ideas? Seems to be the data partition causing the problems.
Click to expand...
Click to collapse
Damn! Please can someone move this to http://forum.xda-developers.com/razr-i/help Posted it in here by accident

I you want to flash a custom rom just don't wipe data and don't do a format /wipe data

The problem with that is it has previous rom stuff still installed.
I like a clean fresh install of a rom, so no contacts, messages, apps etc...
There is no way to do this without a bootloop.

Flacid Monkey said:
The problem with that is it has previous rom stuff still installed.
I like a clean fresh install of a rom, so no contacts, messages, apps etc...
There is no way to do this without a bootloop.
Click to expand...
Click to collapse
flash a stock rom via rsd-lite..this will wipe the data too..then flash a custom rom

antkalaitzakis96 said:
flash a stock rom via rsd-lite..this will wipe the data too..then flash a custom rom
Click to expand...
Click to collapse
Boot loop.
Get to the rom boot animation and it does the updating apps then boot loops back to the moto screen and rom animation then repeats until i power off and restore a backup.
Thank you both for suggestions so far. Getting closer to solving
Sent from my XT890 using XDA Premium 4 mobile app

Flacid Monkey said:
Boot loop.
Get to the rom boot animation and it does the updating apps then boot loops back to the moto screen and rom animation then repeats until i power off and restore a backup.
Thank you both for suggestions so far. Getting closer to solving
Sent from my XT890 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
u using cwm?
before flash a rom -> wipe data /system / cache! / dalvik chache -> then flash!
if this dont help do above + wipe battery stats then flash the rom.
have fun.
regards

pangyaaaaaa said:
u using cwm?
before flash a rom -> wipe data /system / cache! / dalvik chache -> then flash!
if this dont help do above + wipe battery stats then flash the rom.
have fun.
regards
Click to expand...
Click to collapse
Yes, I'm using cwm. Tried touch and twrp.
Tried the above, same bootloop.
Only works if i leave my stock 404, push pillama 1.4 via adb and then flash the custom ROM over that in cwm.
This leaves residue from 404 and pillama on my phone though.
Sent from my XT890 using XDA Premium 4 mobile app

Flacid Monkey said:
Yes, I'm using cwm. Tried touch and twrp.
Tried the above, same bootloop.
Only works if i leave my stock 404, push pillama 1.4 via adb and then flash the custom ROM over that in cwm.
This leaves residue from 404 and pillama on my phone though.
Sent from my XT890 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Does stock 404 mean, you are still on ICS?
If so why don't you flash JB with RSD-Lite and try again installing a custom rom?

Can u make a logcat about it?

ICuaI said:
Does stock 404 mean, you are still on ICS?
If so why don't you flash JB with RSD-Lite and try again installing a custom rom?
Click to expand...
Click to collapse
Trying this now
Hazou said:
Can u make a logcat about it?
Click to expand...
Click to collapse
Will try the above then if it doesn't work I'll log it :good:

So I tried RSD lite with Android 4.1.2 Blur_Version.91.2.26001.XT890.Retail.en.EU
No dice. Failed at 7/16 System_Signed
This royally put me in a bad place. 45 minutes of ADB later, I'm back on my CWM backup of 404.
Gonna clean the logs and start from scratch

Flacid Monkey said:
So I tried RSD lite with Android 4.1.2 Blur_Version.91.2.26001.XT890.Retail.en.EU
No dice. Failed at 7/16 System_Signed
This royally put me in a bad place. 45 minutes of ADB later, I'm back on my CWM backup of 404.
Gonna clean the logs and start from scratch
Click to expand...
Click to collapse
I have the same problem and I am on Stock 4.1.2. I have given up and no longer have a rooted phone with a custom ROM. I would, however, be grateful if someone could find a solution
If you are on 404 and trying to get to 4.1.2 you can root your phone then use the following method to unroot and install 4.1.2. You can then root again if you wish.
http://forum.xda-developers.com/showthread.php?t=2398347

grampsharry said:
I have the same problem and I am on Stock 4.1.2. I have given up and no longer have a rooted phone with a custom ROM. I would, however, be grateful if someone could find a solution
If you are on 404 and trying to get to 4.1.2 you can root your phone then use the following method to unroot and install 4.1.2. You can then root again if you wish.
http://forum.xda-developers.com/showthread.php?t=2398347
Click to expand...
Click to collapse
Thank you will give that a go.
I've got a problem now after trying the official 4.1.2 upgrade which failed miserably, the boot image has changed to the warning unlocked phone bla bla bla
My SMS centre number keeps disappearing stopping texts sending. Receiving and calling work fine. Tried the fixes online but all work for two minutes then it disappears again.
Can't factory reset, just boots back up with everything as it was when it turned off. Can't get into the stock recovery so stuck with CWM or twrp
Any time I flash a rom it boot loops.
Ideas on how I can get a clean official 4.1.2 onto the phone? Re-lock bootloader, remove root and then try?

So locking bootloader and removing root does not work.
I'd advise anyone that doesn't know what they're doing to avoid it.
It pretty much soft bricked my phone.
I've started a new thread in q&a with another issue regarding multi flash in fastboot hanging on the third or fourth download.
Im certain parts of the 4.1 are still there even after formatting everything in cwm and restoring my original backup.
Having network issues, 3g and wifi etc are fine. Sms, calls and anything to do with changing network operator just stops a few minutes after boot. I can still receive fine which is odd.
What's the deal with putting a radio on over an official ROM? Yey or ney
Sent from my XT890 using XDA Premium 4 mobile app

need help with flashing android hd 62.0

hello there,
so earlier i was trying to flash my htc one m7 with android 62.0 but it seems it wasn't a success because now my phone is just stuck in a boot loop and i cant get into recovery mode anymore. Now its been awhile since i flashed a rom, i had android hd 31.0 before that so i thought id update it but its seems its gonna be a bit harder that that. my phone is showing s-on with hboot 1.55 and i used clockwork to flash the rom. now could i get some advice as to how i could get this android hd 62.0 to work on my htc? or should i just try to revert to what i used to but the problem is the old rom isn't on my phone anymore and i was never able to find the stock rom for my phone (rogers canada m7). any advice here ?

If you have an old CWM, try upgrading it first. With newer OSs, something in the Android install procedure has changed. You need a recovery that's at least as new as TWRP 2.6.3.3. To get back to recovery, try using the power+volume down button to get to fastboot mode, and use the computer for "fastboot erase recovery" and "fastboot erase cache". Then boot to recovery.

fenstre said:
If you have an old CWM, try upgrading it first. With newer OSs, something in the Android install procedure has changed. You need a recovery that's at least as new as TWRP 2.6.3.3. To get back to recovery, try using the power+volume down button to get to fastboot mode, and use the computer for "fastboot erase recovery" and "fastboot erase cache". Then boot to recovery.
Click to expand...
Click to collapse
hey there fenstre thanks for answering so quickly,
so i was able to install a most recent cwm version, i tried to flash the same rom again but this time it just stay stuck on the htc screen.i tried to clear the cache..not really sure what else i should try at this point is there anything else i might be doing wrong ?

deerome said:
so i was able to install a most recent cwm version, i tried to flash the same rom again but this time it just stay stuck on the htc screen.i tried to clear the cache..not really sure what else i should try at this point is there anything else i might be doing wrong ?
Click to expand...
Click to collapse
Do you need to wipe data? Did you wipe data within the ARHD installer? (For me, it doesn't ever work unless I do this. You can make a nandroid backup before if you want.)

fenstre said:
Do you need to wipe data? Did you wipe data within the ARHD installer? (For me, it doesn't ever work unless I do this. You can make a nandroid backup before if you want.)
Click to expand...
Click to collapse
i didint wipe the data the first time i tried flashing i thought i didint need to but guess i was wrong but i did try to flash it a second time while wiping it and it still seem to stay stuck on the htc logo..grr would there be another way to go around about it ? could the rom be not compatible with my phone?

deerome said:
i didint wipe the data the first time i tried flashing i thought i didint need to but guess i was wrong but i did try to flash it a second time while wiping it and it still seem to stay stuck on the htc logo..grr would there be another way to go around about it ? could the rom be not compatible with my phone?
Click to expand...
Click to collapse
Could be--is your phone the m7-ul, the international HTC One? If so, did you wipe cache and dalvik cache in recovery, and data inside the ARHD installer? If you've done all that, I'm about out of ideas...

ARHD requires TWRP 2.6.3.3 CWM will not work and will just bootloop
http://techerrata.com/browse/twrp2/m7
ARHD 2.7 has known issues
Sent from my GT-I9505 using XDA Premium 4 mobile app

fenstre said:
Could be--is your phone the m7-ul, the international HTC One? If so, did you wipe cache and dalvik cache in recovery, and data inside the ARHD installer? If you've done all that, I'm about out of ideas...
Click to expand...
Click to collapse
yea i even tried that and it didint work.if i found a stock rom for my htc carrier (roger) would i be able to install that on my phone ?

deerome said:
yea i even tried that and it didint work.if i found a stock rom for my htc carrier (roger) would i be able to install that on my phone ?
Click to expand...
Click to collapse
Yes, do it from the bootloader (after re-locking it). You'll have to find the instructions somewhere...

bored_stupid said:
ARHD requires TWRP 2.6.3.3 CWM will not work and will just bootloop
http://techerrata.com/browse/twrp2/m7
ARHD 2.7 has known issues
Sent from my GT-I9505 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
that was the issue this fixed my problem your a genius ! thanks :good:

deerome said:
that was the issue this fixed my problem your a genius ! thanks :good:
Click to expand...
Click to collapse
Your welcome
Sent from my GT-I9505 using XDA Premium 4 mobile app

Auto going to cwm after flashing every rom ( flashable zip)

Hi,
I am using Sony xperia sp c5303, unlocked bootloader.
Everytime i try to flash a rom through cwm,it is auto switching to recovery again in every boot.
Only working when i am flashing ftf or flashing cm11 through cwm.
But non of sony stock zip is working. Please help me out. Hope my problem makes sense i wipe and erase Everytime data cache system dalvik but no luck.
Sent from my C5303 using XDA Premium 4 mobile app

(Bump)
Sent from my C5303 using XDA Premium 4 mobile app

(BUZZ)

Wish I could help but it seemed it might will not help you. So here come suggestions.
My friend's XSP also faced this problem. But I fixed it easily by wiping the phone's system partition and re-flash the ROM.

TechnoSparks said:
Wish I could help but it seemed it might will not help you. So here come suggestions.
My friend's XSP also faced this problem. But I fixed it easily by wiping the phone's system partition and re-flash the ROM.
Click to expand...
Click to collapse
I wiped more than i brush these days ty btw

amigo911 said:
I wiped more than i brush these days ty btw
Click to expand...
Click to collapse
Lets use an another odd method that I once got something fixed with. Only if you choose to take your time.
First do a nandroid backup of your device. Then flash stock ROM and wipe everything via flashtool. Afterwards root it, and install a recovery. Then from that recovery restore your nandroid backup.
Things to note:
- Make sure integrity of your nandroid backup
- For safety backup your apps through Titanium Backup too
- If SP does not boot after restoring nandroid, flash the ROM zip again. This may have to do with the kernel.

TechnoSparks said:
Lets use an another odd method that I once got something fixed with. Only if you choose to take your time.
First do a nandroid backup of your device. Then flash stock ROM and wipe everything via flashtool. Afterwards root it, and install a recovery. Then from that recovery restore your nandroid backup.
Things to note:
- Make sure integrity of your nandroid backup
- For safety backup your apps through Titanium Backup too
- If SP does not boot after restoring nandroid, flash the ROM zip again. This may have to do with the kernel.
Click to expand...
Click to collapse
Alright honey, on it. Will let you know update ?