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 ?
Related
My i9305 LTE is caught in a boot loop (just loops the start-up screen of any ROM I install). I have access to CWM recovery v6.0.4.5 and also download recovery.
The only thing I can think that might have caused this was when I installed Archidroid I (foolishly?) selected the only partition that wasn't ext4, to be set as ext4. It's not booted past any of the bootscreens on any ROM since I did this.
I've tried wiping all data and cache and also doing a data/factory reset and every "clear data" option available and I'm still caught in a boot screen loop on any ROM I try.
I've formatted each of the folders on the device by mounting and formatting (I don't need to keep any data on the phone) and then to get a new ROM on the phone I've inserted an SD Card, mounted it in CWM recovery and installed it from the .zip that way, all ROMs I've tried just lock up at their boot screen, it just loops over and over.
I've searched this forum and on Google but cannot find a solution or anyone with a similar issue, most that have had a similar looping problem say they performed an Odin factory reset, which brings me to my next question.
I don't know the region of my phone as I cannot access the dialler or any of my settings to find out the region, and forgot (as I rooted so long ago). I do have on the back of the phone the codes:
FCC ID: A3LGI9305
SSN: -I9305GSMH
as well as my IMEI #
How do I know my phone region, and which firmware/rom would I use to perform a full factory reset to at least get it booting again?
Any tips/ideas please, that would be much appreciated.
likeasir said:
My i9305 LTE is caught in a boot loop (just loops the start-up screen of any ROM I install). I have access to CWM recovery v6.0.4.5 and also download recovery.
The only thing I can think that might have caused this was when I installed Archidroid I (foolishly?) selected the only partition that wasn't ext4, to be set as ext4. It's not booted past any of the bootscreens on any ROM since I did this.
I've tried wiping all data and cache and also doing a data/factory reset and every "clear data" option available and I'm still caught in a boot screen loop on any ROM I try.
I've formatted each of the folders on the device by mounting and formatting (I don't need to keep any data on the phone) and then to get a new ROM on the phone I've inserted an SD Card, mounted it in CWM recovery and installed it from the .zip that way, all ROMs I've tried just lock up at their boot screen, it just loops over and over.
I've searched this forum and on Google but cannot find a solution or anyone with a similar issue, most that have had a similar looping problem say they performed an Odin factory reset, which brings me to my next question.
I don't know the region of my phone as I cannot access the dialler or any of my settings to find out the region, and forgot (as I rooted so long ago). I do have on the back of the phone the codes:
FCC ID: A3LGI9305
SSN: -I9305GSMH
as well as my IMEI #
How do I know my phone region, and which firmware/rom would I use to perform a full factory reset to at least get it booting again?
Any tips/ideas please, that would be much appreciated.
Click to expand...
Click to collapse
what country do you live? the region is the country you live in, just search for your official firmware on sammobile or samsung update site. and download the firmware for your country, flash it with odin.
also update your recovery to the latest available in your case cwm 6.0.4.7
PHP:
MaHo_66 said:
what country do you live? the region is the country you live in, just search for your official firmware on sammobile or samsung update site. and download the firmware for your country, flash it with odin.
also update your recovery to the latest available in your case cwm 6.0.4.7
Click to expand...
Click to collapse
I live in Australia but am slightly worried as I bought my phone from Koga online so it's an internationally shipped phone I think originally intended for the uk as it had a uk adaptor for the plug does this matter?
likeasir said:
PHP:
I live in Australia but am slightly worried as I bought my phone from Koga online so it's an internationally shipped phone I think originally intended for the uk as it had a uk adaptor for the plug does this matter?
Click to expand...
Click to collapse
Hmm... Good question. I understand your issue here but im afraid i cant answer this.. While it was working what firmware was running on it? What baseband? If you have any kind of info of the working firmware, analyze it with firmwares on those sites and try to find the one you need.
Sent from my GT-I9305 using XDA Premium 4 mobile app
likeasir said:
My i9305 LTE is caught in a boot loop (just loops the start-up screen of any ROM I install). I have access to CWM recovery v6.0.4.5 and also download recovery.
The only thing I can think that might have caused this was when I installed Archidroid I (foolishly?) selected the only partition that wasn't ext4, to be set as ext4. It's not booted past any of the bootscreens on any ROM since I did this.
I've tried wiping all data and cache and also doing a data/factory reset and every "clear data" option available and I'm still caught in a boot screen loop on any ROM I try.
I've formatted each of the folders on the device by mounting and formatting (I don't need to keep any data on the phone) and then to get a new ROM on the phone I've inserted an SD Card, mounted it in CWM recovery and installed it from the .zip that way, all ROMs I've tried just lock up at their boot screen, it just loops over and over.
I've searched this forum and on Google but cannot find a solution or anyone with a similar issue, most that have had a similar looping problem say they performed an Odin factory reset, which brings me to my next question.
I don't know the region of my phone as I cannot access the dialler or any of my settings to find out the region, and forgot (as I rooted so long ago). I do have on the back of the phone the codes:
FCC ID: A3LGI9305
SSN: -I9305GSMH
as well as my IMEI #
How do I know my phone region, and which firmware/rom would I use to perform a full factory reset to at least get it booting again?
Any tips/ideas please, that would be much appreciated.
Click to expand...
Click to collapse
Well I was in the same pickle
whicever 4.3 rom i flashed through odin i got stuck in boot logo or even if i recovered device from odin through emergency frimware and intillation
Also tried customs 4.3 roms stuck a boot logo
Here what u should try and what i did
1 flash philz recovery + 4.1.2 rom
if it works back up efs
2 Using Philz recovery wipe data factory reset + wipe cache + dalvik cache
3 in mount and storage section format everything ( THINK THIS IS THE MOST IMPORTANT STEP )
4 Used odin to flash a 4.3 stock package it worked ( note u may get knox from this u may try a modifed stock package if u dont have knox and dont want to get it )
AMoizK said:
Well I was in the same pickle
whicever 4.3 rom i flashed through odin i got stuck in boot logo or even if i recovered device from odin through emergency frimware and intillation
Also tried customs 4.3 roms stuck a boot logo
Here what u should try and what i did
1 flash philz recovery + 4.1.2 rom
if it works back up efs
2 Using Philz recovery wipe data factory reset + wipe cache + dalvik cache
3 in mount and storage section format everything ( THINK THIS IS THE MOST IMPORTANT STEP )
4 Used odin to flash a 4.3 stock package it worked ( note u may get knox from this u may try a modifed stock package if u dont have knox and dont want to get it )
Click to expand...
Click to collapse
Thanks for your suggestion, I'll give that a shot tonight. I'm able to get into CWM as explained, mount and format everything so I'm not sure that this step will make a difference, but I'll do it again anyway.
So I'll see how it goes tonight. Actually been quite refreshing without a phone these past couple of days
likeasir said:
Thanks for your suggestion, I'll give that a shot tonight. I'm able to get into CWM as explained, mount and format everything so I'm not sure that this step will make a difference, but I'll do it again anyway.
So I'll see how it goes tonight. Actually been quite refreshing without a phone these past couple of days
Click to expand...
Click to collapse
I managed to fix it, but it had me totally stumped for a while.
I flashed philz recovery and then formatted all of the directories as I'd done previously on CWM.
I tried Slim Rom which didn't work.
I ended up tying CyanogenMod stable which actually worked, it got past the boot loop phase! - I was glad to see a setup screen after 2 days!
I then had another issue with my Cell Reception not working, no data or reception would be shown.
This seemed to happen since I tried a KitKat ROM, as I remember before the bootloop it did this on a couple of ROMs I tried to manually enter the APN over and over and it wouldn't let me save it, very annoying.
I checked the baseband in the about phone section and it was being displayed as "unknown", luckily I remembered my baseband # from when I rooted the phone about 8 months ago (XXBLL3), then I found on this forum a list of 9305i baseband downloads as .zips so I was able to load up CWM and flash it, reboot and it worked!
I will be keeping with CM Stable (10.1.3) for a while now.
I hope this helps someone else that might run into a similar issue.
likeasir said:
I managed to fix it, but it had me totally stumped for a while.
I flashed philz recovery and then formatted all of the directories as I'd done previously on CWM.
I tried Slim Rom which didn't work.
I ended up tying CyanogenMod stable which actually worked, it got past the boot loop phase! - I was glad to see a setup screen after 2 days!
I then had another issue with my Cell Reception not working, no data or reception would be shown.
This seemed to happen since I tried a KitKat ROM, as I remember before the bootloop it did this on a couple of ROMs I tried to manually enter the APN over and over and it wouldn't let me save it, very annoying.
I checked the baseband in the about phone section and it was being displayed as "unknown", luckily I remembered my baseband # from when I rooted the phone about 8 months ago (XXBLL3), then I found on this forum a list of 9305i baseband downloads as .zips so I was able to load up CWM and flash it, reboot and it worked!
I will be keeping with CM Stable (10.1.3) for a while now.
I hope this helps someone else that might run into a similar issue.
Click to expand...
Click to collapse
Cheers on getting ur phone fixed but after wiping all directories a stock rom flash would have cleared all the problems
lol i just did this to my phone, time to find a stock firmware.
Hi guys, i just rooted my device using TWRP. As i am new to all this, i tried flashing CM11 ROM but i was getting "failed" message again and again. Then mistakenly i used option of "Advance Wipe" and wiped everything. Now while booting up the device i am going to recovery but there is no backup available and i am unable to install any ROM as the custom ROM is also deleted along with backup. Please help me out on this. Thanks...
Hemant17 said:
Hi guys, i just rooted my device using TWRP. As i am new to all this, i tried flashing CM11 ROM but i was getting "failed" message again and again. Then mistakenly i used option of "Advance Wipe" and wiped everything. Now while booting up the device i am going to recovery but there is no backup available and i am unable to install any ROM as the custom ROM is also deleted along with backup. Please help me out on this. Thanks...
Click to expand...
Click to collapse
I have done that a few times by mistake I would download the rom on a thumb drive and use my otg cable to plug it in flash it from the thumb drive in recovery.
You can also side load it as well, yet I have never done it that way so you would have to search that.
I have also read some say download the rom to your pc and and plug in phone and drag the rom to your sdcard.
If all else fails you can always return to stock via rsd or mfastboot as long as you can get into download mode.
Thanks a lot for your prompt response. I am having Moto x 2013 edition and tried to flash CM11 ROM using thumb drive in recovery mode but the "failed" message was coming , is it a compatibility issue of ROM with My device? As i told that i am new to all these things can you please guide me or share with me a link for any good ROM which i could flash on my Moto x and make it functional again.
Also if i want to get back to my stock ROM i.e. Kitkat 4.4 then how to do it? will i be able to update to lollipop in future?
Sorry for asking so many questions and thanks again for your support.
It sounds more like you should flash your phone back to stock and leave it there until you understand what you're doing. With the number of guides available anymore, the entire flashing process should be dead simple and difficult to mess up. Add to the fact that wiping/formatting partitions always prompts for confirmation before actually deleting things, and it shows that you don't really have any knowledge about what is going on. Keeping your phone stock until you do know what you're doing is only going to save you from having a paperweight in the long run.
Thanks a lot!!!! with your support i am able to flash my phone on cyanogen12
Thanks agian...
Hello,
I think I've messed up my MI3 a bit to much.
After trying out 15+ ROMs, partitioning with several methods,
swapping CWM & TWRP just to see what will happen,
my MI3 finally "gave the ghost" as we say in good dutch.
I have some idea of what's wrong, but haven't the ghusto to sort it out any more.
Most probable is a few wrong partion sizes allowing me only
to install the last working recovery (CWM).
Anyway, to cut a long story short,
is there any way to COMPLETELY do an original factory reset,
including removing all partions and creating new ones with the right sizes
with an original (MIUI ?) factory ROM installation ?
Alternative ideas are welcome.
Yes, (I think) flashing the original ROM, MIUI, it will restore everything to factory (including the kernel, partitions, etc). Using the official tool is the easiest way http://en.miui.com/thread-92720-1-1.html
ChazyTheBest said:
Yes, (I think) flashing the original ROM, MIUI, it will restore everything to factory (including the kernel, partitions, etc). Using the official tool is the easiest way http://en.miui.com/thread-92720-1-1.html
Click to expand...
Click to collapse
Thanks Chazy,
but .. been there ... done that ... phone not recognised
Inonotting said:
Thanks Chazy,
but .. been there ... done that ... phone not recognised
Click to expand...
Click to collapse
Did you try connecting your phone in fastboot mode? It starts a window where you can flash the latest stable or developer rom.
I just did it and my phone is restored to factory, everything working. It should work, no matter what genocide you did to your phone lol :laugh:
I tried fastboot already, had some errors.
Can't seem to find any fastboot roms anymore, I only have
cancro_images_V6.1.2.0.KXDCNBJ_4.4_cn_2cbb2e76e8.tgz
I'll try again sometime this week.
I seem to recall that fastboot had some problems with my partitioning also.
You mean errors while flashing with fastboot? It should fix the partitions... I flashed the zip to extend to 1.2GB and installed the cm12.1 with stuxnet kernel but it seems there are some problems and it's not booting. So I used the mi manager, connected the usb in fastboot mode and it reverted and installed miui room without errors.
Try the developer room, if you have problems downloading it (with the mi manager, they're having server problems) go to the folder where it downloads (C:\Xiaomi\... can't remember) and open the .cfg file (using notepad) and copy the url link and open it in firefox or chrome, it should download the file at full speed. Delete the two files in the folder and move from downloads the new file. Disconnect the phone and connected it again in fastboot mode, choose the developer room and it should flash it, fixing partitions. (ram usage is a bit improved since the other old stable, getting 1.1/1.2GB uninstalling crapware and system apps like ant hal service, etc)
I'm using the last developer room and there are no problems, everything smooth, stable and good performance (with a new cool interface and themes). Still waiting for 5.1.1 though
Nope, just a message,
"Can not install" or something like that, no explanation
Inonotting said:
Nope, just a message,
"Can not install" or something like that, no explanation
Click to expand...
Click to collapse
Solved :
forum.xda-developers.com/xiaomi-mi-3/general/mi3-bricked-t3195574
I used The Dork Knight Rises' partitioning method, back to stock, then back to extended :
forum.xda-developers.com/xiaomi-mi-3/general/extremely-useful-flashable-zips-t3080860/
Being the complete moron I am, I accidentally flashed Cynogenmod 7.2.0 (Stable version) before installing CWM (v4.0.0.9).
This led to the boot loop. I managed to install CWM with great success, however now I receive error 7 when installing any custom ROM
I have tried:
- Cynogenmod
- TheUltimatum(V4.9)[-The'A'Factor] // With this one, I managed to get the furthest, being able to go into the custom GUI installer, pick the options I wanted, however upon installing I still receive error 7.
- PAC
- Toggling script asserts
- Deleting the phone verification feature in the script, I did this to Cynogenmod, however it did not work. I think trying it again might work but I know that if (for example) it is not the correct ROM I think it is, I'll have a nice paper weight.
- Looked at about 30 different pages claiming to have the Gingerbread 2.3.3 download (I'd be happy to just go back to that at this point, even if it was ugly and slow).
- Used Odin to install a custom ROM, I have Kies which has installed several drivers for the phone. I do not know exactly what it says, but I am able to see the phone in Odin, I am able to choose the ROM and press start, however, once I have pressed start I see it do something for a second, then it gets stuck at SetupConnection.
- Wiping data/factory reset
- Wiping cache partition
- Wiping Dalvik cache (I read in several place this does something..)
I have searched the internet far and wide, XDA has been quite the website with the most help ( Thank you guys ) however they all seem to say the same thing for what I am searching for and that does not seem to work. Or maybe, just maybe, I'm stupid... (Probably the latter)
dideej848 said:
Being the complete moron I am, I accidentally flashed Cynogenmod 7.2.0 (Stable version) before installing CWM (v4.0.0.9).
This led to the boot loop. I managed to install CWM with great success, however now I receive error 7 when installing any custom ROM
I have tried:
- Cynogenmod
- TheUltimatum(V4.9)[-The'A'Factor] // With this one, I managed to get the furthest, being able to go into the custom GUI installer, pick the options I wanted, however upon installing I still receive error 7.
- PAC
- Toggling script asserts
- Deleting the phone verification feature in the script, I did this to Cynogenmod, however it did not work. I think trying it again might work but I know that if (for example) it is not the correct ROM I think it is, I'll have a nice paper weight.
- Looked at about 30 different pages claiming to have the Gingerbread 2.3.3 download (I'd be happy to just go back to that at this point, even if it was ugly and slow).
- Used Odin to install a custom ROM, I have Kies which has installed several drivers for the phone. I do not know exactly what it says, but I am able to see the phone in Odin, I am able to choose the ROM and press start, however, once I have pressed start I see it do something for a second, then it gets stuck at SetupConnection.
- Wiping data/factory reset
- Wiping cache partition
- Wiping Dalvik cache (I read in several place this does something..)
I have searched the internet far and wide, XDA has been quite the website with the most help ( Thank you guys ) however they all seem to say the same thing for what I am searching for and that does not seem to work. Or maybe, just maybe, I'm stupid... (Probably the latter)
Click to expand...
Click to collapse
if you can go in download mode, you can try to install stock ROM (not custom ROM) by odin:
http://live.samsung-updates.com/index.php?device=GT-S5830
daniga74 said:
if you can go in download mode, you can try to install stock ROM (not custom ROM) by odin:
http://live.samsung-updates.com/index.php?device=GT-S5830
Click to expand...
Click to collapse
Try formatting system, cache and data and retry in cwm in advanced settings
Hi everyone,
I really need help, I have tried everything I could think of and nothing works. So if someone more knowledgeable could help me, that would be great.
I followed the instructions in this thread https://forum.xda-developers.com/z3-compact/general/how-to-root-backup-drm-keys-t3013343
and everything went ok until I flashed a new ROM.
Current situation : Bootloop when I power up. Can still access TWRP recovery. Phone is recognized by flashtool/xperia companion/emma.
Tried to flash a new ROM with flashtool->error (can't read byte value), I tried de/re-installing flashtool and the drivers and different ROMs, always the same result
Tried to repair with xperia companion->error, can't complete
Tried emma->phone is locked
Tried sideloading ROM to flash through TWRP-> error
I don't understand how, even if I flashed a corrupted ROM, it could prevent me from flashing a new one over it?
Any ideas?
Thank you.
You can try xflasher tool as well.
https://forum.xda-developers.com/crossdevice-dev/sony/dev-xflasher-command-line-flasher-t2986634
But be warned - this is for more experienced users. I never tried it but it sounds like to be very powerfull.
For questions ask in xflasher thread... I never used it up to now...
But sometimes it helps to wipe cache/dalvik AND data from TWRP. Yes - all your data is away then!
Not nice to loose data but a bootable phone is even better...
Or flash again full ftf via flashtool. Wipe APPS_LOG/USERDATA (check boxes) but do not flash simlock.ta (if its there) !!!
This will wipe all your data as well..... While flashing, say NO to "fcs-script" popup.
. .
Thanks for the replies.
I tried different USB cable/port, no change.
I always selected to wipe everything in flashtool. I just got the phone so there was none of my data to save.
I will look at xflasher although, as you said, it looks intimidating...
. .