Database Develop

[Q] Loop reboot when installing custom roms

What i did before installing a custom rom:
I rooted my phone using superoneclick method.
Then installed xrecovery V0.1. (with busybox and charm*something)
Made a backup of the original room using Xrecovery
How did i install the custom roms and what happend:
Renamde gingerxd v13 to update.zip and place it on sdcard.
Wiped cache and factory reset(fullwipe).
Install update.zip with Xrecovery.
(after my first attemp failed, i tried to wipe cache and factory reset after installing the room too)
Reboot phone.
Phone goes into reboot loop. First sony ericsoon, then the logo of whatever custom room i'm trying to install.
I tried the MiniCM7-2.0.7 (source)
Then i tought, what if i downloader a back from another phone? i got Floyo 2.2.5 (source)
Restoring this backup too got me into a reboot loop.
Final question(and probably the supidest one if the answer is yes)
Do i need to unlock the bootloader to install a custom room? The guides i used didn't mention it at all, and since it may brick my device beyong xrecovery's help i'd like a straight answer before attempting it.
I tried to make this post as clear as possible and maybe someone can point out if im missing something.

Very important thing: Did your baseband end with 015? If no, that's why you are having these problems.
And no, you don't need to unlock the Bootloader to install Custom Roms.

It ends in 006. Thanks ill be reading on flashing a baseband and report back. PCcompanion says my phone is up do date so i'll be using this. If you have a better alternative let me know.
^^
Edit: Is there a way to configure pcc to make the update for me? Like say im from another country were the update is available?

Use Flashtool, go here

Thanks Chris95X8. my phone is now running 2.3.5 gingerdx rom. everything works. The only thing that's driving me nuts is the notification i get when i lose signal. Any way to fix this?

Sadly it didnt work for me... I have tried out flashing basebands but it wont work. still looping around. makes me crazy.

Kiwiii97 said:
Sadly it didnt work for me... I have tried out flashing basebands but it wont work. still looping around. makes me crazy.
Click to expand...
Click to collapse
Are you sure that you flashed the right baseband?
If you have, maybe try to boot phone without the SD card in it..

Softbrick N7000 Need Help

When my phone boots it only gets to the samsung logo
I am able to use the recoverymode and downloadmode.
Wiping data won´t work. Wiping cache works.
Can´t flash a CustomROM from my SDcard through CWM
I was able to connect my phone to the PC. ADB finds the phone but adb shell won´t work. (No such file or directory <2>)
How can I install either a regular Androidversion or a CustomROM now.
found this but only for Galaxy S3, so the files won´t help me
http://forum.xda-developers.com/showthread.php?t=1840030
Hope you can help me
Tobias

Download a Stock Rom from sammobile.com or one of the prerooted Roms (I always use a GB LC1 from bodivas for this) and install it with the PC version of Odin.

tried that, Odin stops at "NAND write start!!"

AW: Softbrick N7000 Need Help
What Rom did you have and what did you do before this happened?
Sent from my GT-N7000 using xda premium

Now I used a regular Android 4.0.4. ROM
Before that I tried with a 2.3.1 ROM. This is probably the reason for the trouble, isn´t it?

Tobias H. said:
tried that, Odin stops at "NAND write start!!"
Click to expand...
Click to collapse
I wrote to download a new rom and to try it with Odin. 15 min later you said: did this.
So I want to ask: Did you really download a new Rom or did you use one you had already?
And what Rom exactly?
And what did you do before stopping at boot logo?

ThaiDai said:
I wrote to download a new rom and to try it with Odin. 15 min later you said: did this.
So I want to ask: Did you really download a new Rom or did you use one you had already?
And what Rom exactly?
And what did you do before stopping at boot logo?
Click to expand...
Click to collapse
I was already downloading the 4.0.4. ROM. Because I read somewhere it´s not possible to go from ICS to Gingerbread.
The download just finished right after you answered and I tried. I am 100% sure i got the right ROM.
Before getting all these Problems, I wanted to get a CustomROM on my phone. Android 4.0.4 was installed at that point of time.
I rooted my phone and did a backup with CWM. Then i chose wipe data, while doing that I started to charge my phone (I don´t know if that matters). I didn´t see what happen exactly because i wasn´t looking at my phone all the time, but when i looked at it again there was only the charging sign shown. Then I tried to get into recoverymode again. This wouldn´t work. I tried to flash CWM with Odin which worked after some time. Then I tried to Wipe data and cache again. wipe data wouldn´t work. Wipe cache worked. I tried to install the backup. After waiting for more then 1 hour it looked like nothing happend and the installation was stuck. But the regular recovery of Android was installed.
Because flashing a ROM through CWM wouldn´t work, I tried to flash it through Odin. First time I tried with a Gingerbread Version. I was thinking, I don´t care which version as long as it works and try again to install a CustomROM from there on. Odin stopped at NAND Write Start!!. Tried it with the ICS Stock version. Same thing.
This is where I am at now

Did you use cwm.zip?

To use with Odin? No
When I started it from the regular Android Recoverymode? Yes
Don´t you think this might be exactly the problem I have?
http://forum.xda-developers.com/showthread.php?t=1840030

Tobias H. said:
I was already downloading the 4.0.4. ROM. Because I read somewhere it´s not possible to go from ICS to Gingerbread.
The download just finished right after you answered and I tried. I am 100% sure i got the right ROM.
Before getting all these Problems, I wanted to get a CustomROM on my phone. Android 4.0.4 was installed at that point of time.
I rooted my phone and did a backup with CWM. Then i chose wipe data, while doing that I started to charge my phone (I don´t know if that matters). I didn´t see what happen exactly because i wasn´t looking at my phone all the time, but when i looked at it again there was only the charging sign shown. Then I tried to get into recoverymode again. This wouldn´t work. I tried to flash CWM with Odin which worked after some time. Then I tried to Wipe data and cache again. wipe data wouldn´t work. Wipe cache worked. I tried to install the backup. After waiting for more then 1 hour it looked like nothing happend and the installation was stuck. But the regular recovery of Android was installed.
Because flashing a ROM through CWM wouldn´t work, I tried to flash it through Odin. First time I tried with a Gingerbread Version. I was thinking, I don´t care which version as long as it works and try again to install a CustomROM from there on. Odin stopped at NAND Write Start!!. Tried it with the ICS Stock version. Same thing.
This is where I am at now
Click to expand...
Click to collapse
Why did u buy SGN? To brick it?
Do you even read and search before doing something for the first time?
LOOK, READ AND LEARN THIS for stock ROMs and kernels, specialy for ICS:
- http://forum.xda-developers.com/showthread.php?t=1424997
-http://forum.xda-developers.com/showthread.php?t=1371007
-http://forum.xda-developers.com/showthread.php?t=1827394
To run ur device find something and READ.
Try leaked JB custom ROM and stock rooted kernel with safe emmc_cap_erase block (emmc bug fix) -Philz Kernel
READ and LEARN.
Have fun
P.S. Maybe you will need our friend hg42 and his famous .PIT files so here it is: http://forum.xda-developers.com/showthread.php?t=1667886

Xperia SP C5303 Bootloop Help

Hello xda community,
First I have to say I'm french so sorry for my english
I really need your help. I've bought that phone TWO days ago and it already doesn't work. Lemme explain:
- I used DooMLoRD method to Root and install CWM (C5303 model with locked bootloader).
- I installed Xperia Pureness. Wiped System, Cache, Dalvik... It worked fine.
- But i after a few hours Home button didnt work eek so I decided to reflash the rom to reload the System UI. As I used to do with my HTC Sensation, i only wiped dalvik cache and cache for the 2nd flash (ERROR). I realised after have rebooted that i should have had wiped System too.
- It didnt boot since this 2nd flash.
- I've been trying to repair it for this ENTIRE day, nothing happens (pressed red button 5 secs, 10 secs, also tried to reflashed stock .254 ftf with FlashTool...), still can't access Home...
Can you devs find a solution? I really need to repair my phone, bought it 2 day ago :crying:
PS: it doesn't matter if i loose data on my phone

Reflash ROM and dont wipe cache and dalvik If that does not work you need to restrore the backup you made, or you can restore it with my easy restore guide i just made

mrjraider said:
Reflash ROM and dont wipe cache and dalvik If that does not work you need to restrore the backup you made, or you can restore it with my easy restore guide i just made
Click to expand...
Click to collapse
Thanks for the quick reply.
I'm always on bootloop, so can't even access CWM, is it still possible to flash a ROM, or access CWM? I've tried something like 10 times to reinstall stock ROM with FlashTool, still stuck at bootscreen.
I didnt think about making a backup

NaStolgiiK said:
Thanks for the quick reply.
I'm always on bootloop, so can't even access CWM, is it still possible to flash a ROM, or access CWM? I've tried something like 10 times to reinstall stock ROM with FlashTool, still stuck at bootscreen.
I didnt think about making a backup
Click to expand...
Click to collapse
If you follow this guide i made: http://forum.xda-developers.com/showthread.php?t=2476938
You will recover your device with an official Sony tool
After that you can try it again. Since im not into flashing custom ROMS at the moment i cant help you futher with it ( just being honest )

It was long... BUT IT WORKED !!
Thanks a lot !!!!

It was long... BUT IT WORKED !!
Thanks a lot !!!!

[Q] xperia z stuck at boot screen

Hello,
I own an Xperia Z C6603 and i was running the latest oficially available firmware before
i m quite new to all the stuff regarding flashing/rooting/unlocking etc
so today i decided to give it a shot.
now my phone is in a state that i cant use it any more.
Basically what i wanted to do is install this [BeanStalk-4.4015] custom rom. Now its stuck on the loadscreen forever.
I started with rooting the device following the description in one of the posts i found here (flashing the previous kernel with flashtool then rooting it and flashing the original latest kernel again) which worked out very well.
After that i unlocked the bootloader following another guide here in forums which went ok without any problems aswell.
As it seemed like it reset all my settings after unlocking the bootloader i reenabled the developer mode to set the USB debugging and security options for unofficial software aswell.
All went fine and i was preparing to install the custom rom so i put the zip file on my sd card entered the recovery mode and flashed the rom zip file.
It seemed all ok and the phone was restarting and its stuck in the boot screen ever since that. I tried to get it back in order by trying out various stuff i could find here on forums.
when i tried to reset the delvik cache initially i did not see any error messages or anything so i assumed that its done correctly also cleared the other caches which were listed. I was getting a bunch of errors but i assumed its because the folders could be empty as it seemed like the phone was completely reset after the bootloader unlock.
I could not get anywhere with the CWM recovery mode so i flashed MOEW kernel through flashtool. The meow kernel was mentioned in the post regarding the custom rom as viable and it included TWRP recovery so i wanted to give it a try.
First exactly the same happened when i tried to boot it normally... Stuck...
So after that i tried to mess around with the TWRP recovery which seemed a bit more complicated than CWM.
First that came to my eye was that i could not enable all the partitions (system was constantly disabled) i managed to enable it after hitting the fix permissions button a bunch of times also i started to get some error messages while trying to reset dalvik cache but none of this changed the main problem at all.
Also i m unable to access the SD card from my computer for some reason even if i enable USB teathering in CWM or TWRP.
any suggestions how to get the phone back to work ?

druvisk said:
Hello,
I own an Xperia Z C6603 and i was running the latest oficially available firmware before
i m quite new to all the stuff regarding flashing/rooting/unlocking etc
so today i decided to give it a shot.
now my phone is in a state that i cant use it any more.
Basically what i wanted to do is install this [BeanStalk-4.4015] custom rom. Now its stuck on the loadscreen forever.
I started with rooting the device following the description in one of the posts i found here (flashing the previous kernel with flashtool then rooting it and flashing the original latest kernel again) which worked out very well.
After that i unlocked the bootloader following another guide here in forums which went ok without any problems aswell.
As it seemed like it reset all my settings after unlocking the bootloader i reenabled the developer mode to set the USB debugging and security options for unofficial software aswell.
All went fine and i was preparing to install the custom rom so i put the zip file on my sd card entered the recovery mode and flashed the rom zip file.
It seemed all ok and the phone was restarting and its stuck in the boot screen ever since that. I tried to get it back in order by trying out various stuff i could find here on forums.
when i tried to reset the delvik cache initially i did not see any error messages or anything so i assumed that its done correctly also cleared the other caches which were listed. I was getting a bunch of errors but i assumed its because the folders could be empty as it seemed like the phone was completely reset after the bootloader unlock.
I could not get anywhere with the CWM recovery mode so i flashed MOEW kernel through flashtool. The meow kernel was mentioned in the post regarding the custom rom as viable and it included TWRP recovery so i wanted to give it a try.
First exactly the same happened when i tried to boot it normally... Stuck...
So after that i tried to mess around with the TWRP recovery which seemed a bit more complicated than CWM.
First that came to my eye was that i could not enable all the partitions (system was constantly disabled) i managed to enable it after hitting the fix permissions button a bunch of times also i started to get some error messages while trying to reset dalvik cache but none of this changed the main problem at all.
Also i m unable to access the SD card from my computer for some reason even if i enable USB teathering in CWM or TWRP.
any suggestions how to get the phone back to work ?
Click to expand...
Click to collapse
hey if you wana go back to stock rom follow this post forum.xda-developers.com/showthread.php?t=2240614
i think u have to fastboot and flash boot.img
try pacman rom which is better and bug free rom

Hi, are you still able to connect to flashtool in flashmode? If so have you tried to flash back to stock rom?
Check this thread out, it contains good stuff.... 3rd video show how to flash stock ....
http://forum.xda-developers.com/showthread.php?t=2275632
Good luck !!

Hello,
thx for your replies i m still able to access all the modes it just does not load up if i dont do anything
after i unlock the bootloader to i need to reroot the phone ?
as it seems right now to me it simply doesnt write anything when i try to flash the rom also some partitions are not available

Hello,
i managed to unbrick the phone using this tutorial http://forum.xda-developers.com/showthread.php?t=2458530
however i tried to redo all the steps following the guide to install the beanstalk rom and noticed that i m getting an error about updater package when i try to execute the installation from TWRP any ideas ?
would you suggest trying another 4.4 based rom ?

Hello again,
ok so i gave up on the beanstalk 4.4 rom and decided to try my luck with pac rom mtayabkk suggested
so now the problem is not as big as it was.
Able to get the rom to run however i m unable to import my contacts/sms/call log using titan backup
The restore seems to work but after that i m getting com.android phone has stopped error everywhere i go on my phone (the contacts/etc are actually restored in this process tho and work fine apart from the errors)
i did restore a bunch of other settings together with the contacts aswell which i found as safe to back up in a guide i found
so can you give me an advice how to properly restore this to the newest pac man rom and avoiding various errors after that ?
ps
i moved all my media to sd card so it does not concern me the only thing i cant seem to be able to move over apart from contacts/sms/call log are the APN settings which is bothering me a bit aswell as i can not receive the configuration messages from carrier but i found them on the internet and i will add them manually
trying to restore the stock backup from PC companion right now to export them again as i lost the backup in process of trying to deal with the error i was getting
would you suggest trying again with titan backup or any other tools ?

Bricked my Xperia T when flashing new ROM

EDIT: I managed to flash stockrom via flashtool, I didn't do anything different so I can't really help others with the same problems, I just kept trying.
But I can tell you the root of all the mess I did: Neowave ROM requires unlocked bootloader, which I didn't had. I'm still curious why it messes up everything and not only /boot
and /system, but I'm glad that everything works again.
So I managed to (hopefully soft)brick my phone again when flashing new rom. (from Omega to Neowave)
What I did:
-flashed new recovery (Philz Touch recovery)
-wiped /system
-flashed new rom, gapps minimal, aosp calendar sync addon and supersu update (all without rebooting)
-then I rebooted the phone, screen was black, no LED, only a vibrate at the beginning.
-PC detects it as SEMC flash drive, the phone automatically disconnects and then reconnects again after ~1min
-Repair with Sony Companion didn't work, it just said that there is no software for my phone
-adb devices said there are no devices
-I can't enter recovery or fastboot, only fastboot worked twice but I disconnected the phone because the Sony Companion said so
Additional info:
-rooted
-locked bootloader
What should I do now?
I wanted a new clean rom because the old one was so damn laggy and had many problems and high battery drain, and I'm going on a vacation
in 2 day so I'm in a hurry. I don't have a 2nd phone because this is already my 2nd (lost my LG G2 2 weeks ago..)
I hope u understand my struggle and take your time to help me, thanks in advance)

NO surrender
Tazmaniiac said:
EDIT: I managed to flash stockrom via flashtool, I didn't do anything different so I can't really help others with the same problems, I just kept trying.
But I can tell you the root of all the mess I did: Neowave ROM requires unlocked bootloader, which I didn't had. I'm still curious why it messes up everything and not only /boot
and /system, but I'm glad that everything works again.
So I managed to (hopefully soft)brick my phone again when flashing new rom. (from Omega to Neowave)
What I did:
-flashed new recovery (Philz Touch recovery)
-wiped /system
-flashed new rom, gapps minimal, aosp calendar sync addon and supersu update (all without rebooting)
-then I rebooted the phone, screen was black, no LED, only a vibrate at the beginning.
-PC detects it as SEMC flash drive, the phone automatically disconnects and then reconnects again after ~1min
-Repair with Sony Companion didn't work, it just said that there is no software for my phone
-adb devices said there are no devices
-I can't enter recovery or fastboot, only fastboot worked twice but I disconnected the phone because the Sony Companion said so
Additional info:
-rooted
-locked bootloader
What should I do now?
I wanted a new clean rom because the old one was so damn laggy and had many problems and high battery drain, and I'm going on a vacation
in 2 day so I'm in a hurry. I don't have a 2nd phone because this is already my 2nd (lost my LG G2 2 weeks ago..)
I hope u understand my struggle and take your time to help me, thanks in advance)
Click to expand...
Click to collapse
When a mistake is always better to return to the " factory " ROM before trying again . I recommend using flashtool . through fastboot , put his boot.img and then a flash the stock rom
I have a TX, roms and testing step that you like . but if the PC recognizes there is hope.
I'm using the google translator . : P

Tazmaniiac said:
EDIT: I managed to flash stockrom via flashtool, I didn't do anything different so I can't really help others with the same problems, I just kept trying.
But I can tell you the root of all the mess I did: Neowave ROM requires unlocked bootloader, which I didn't had. I'm still curious why it messes up everything and not only /boot
and /system, but I'm glad that everything works again.
Click to expand...
Click to collapse
You need to flash a stock ftf.
Keep us updated on how far.

sublinker said:
You need to flash a stock ftf.
Keep us updated on how far.
Click to expand...
Click to collapse
With flashing stockrom I meant flashing stock ftf, sorry for that.