Hi, I used towelroot + flashgordon to root and install recovery on my device which was successful, but every time I flash a ROM and reboot the phone softbricks (no signs of life besides single vibration). I have to reflash the firmware every time in flashtool to fix it. Why does this keep on happening, why are none of the ROMs booting? Any help would be appreciated, thank you.
Related
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..
My device is sc-03e and the rom I flash is rooted-stock-rom provided by docomo.
The history of ROMs I flashed is : from long ago -> rooted-stock-rom from odin -> cunsom rom based on 4.3 from recovery -> AOSB ROM 1.3.5 kk4.4.3 from recovery -> yesterday flash from odin.
After flashing, odin said everything's OK and the device reboot into recovery.
In recovery it said file or something else check failure, and asked me whether I wanna install un-trusted apps or something alike.I chosed yes of course.
After that, it would reboot and asked me whether to install SU, yes again.
Then reboot, if connect to PC or charger, stuck as charging screen with the screen unchanged.
if not connected to anything, after a few seconds device turns off.
What may be the problem?
Do I need to re-partition or re-install the bootloader?
Finally I flashed by adb sideload since I can boot into recovery, but I really want to know the why I failed to boot after flashing from odin.
P.S. tried twice, and odin check the md5 file correct.
Thanks very much.
Blangero said:
My device is sc-03e and the rom I flash is rooted-stock-rom provided by docomo.
...
After flashing, odin said everything's OK and the device reboot into recovery.
In recovery it said file or something else check failure, and asked me whether I wanna install un-trusted apps or something alike.I chosed yes of course.
After that, it would reboot and asked me whether to install SU, yes again.
Then reboot, if connect to PC or charger, stuck as charging screen with the screen unchanged.
if not connected to anything, after a few seconds device turns off.
What may be the problem?
Do I need to re-partition or re-install the bootloader?
Finally I flashed by adb sideload since I can boot into recovery, but I really want to know the why I failed to boot after flashing from odin.
P.S. tried twice, and odin check the md5 file correct.
Thanks very much.
Click to expand...
Click to collapse
Hi mate,
Firstly, this isn't an I9305 question, but it's still an S3 so here goes...
Second, DO NOT RE-PARTITION YOUR PHONE, unless you want a brick.
It sounds to me like the Kernel or Bootloader in that package isn't working properly.
I'm not sure if the sc-03e (Japanese) needs a different Kernel from the I9300 (International).
Just to be sure, I would use CWM or something to format: /system /boot /cache etc. before flashing.
I suggest you install a completely Stock ROM using ODIN and then CF-Auto Root to gain Root Access.
EDIT: This might help also: http://forum.xda-developers.com/galaxy-s3/general/official-japanese-sgs-iii-sc-03e-t2172063
Have a great day!
-Shaz
Lord Shaz said:
Hi mate,
Firstly, this isn't an I9305 question, but it's still an S3 so here goes...
Second, DO NOT RE-PARTITION YOUR PHONE, unless you want a brick.
It sounds to me like the Kernel or Bootloader in that package isn't working properly.
I'm not sure if the sc-03e (Japanese) needs a different Kernel from the I9300 (International).
Just to be sure, I would use CWM or something to format: /system /boot /cache etc. before flashing.
I suggest you install a completely Stock ROM using ODIN and then CF-Auto Root to gain Root Access.
EDIT: This might help also: http://forum.xda-developers.com/galaxy-s3/general/official-japanese-sgs-iii-sc-03e-t2172063
Have a great day!
-Shaz
Click to expand...
Click to collapse
Thanks for your reply, wiping really makes it go.
I found that the pre-rooted ROM doesn't wipe itself, which is different from the stock ROM which I remember will wipe automatically.
I'm having trouble making the flash on the device. This screen always appears to me ... I try to hold the flash by CWM, TWRP Touch and Philz and none works. I root the device by new root method and I realize the wipe, I flash the rom and the device always gaaps and does not turn over, then I have to recover it by Flashtool firmware in stock. I would love to put the cyanogenmod or pacmanrom on my device, but I gave up because there was no other way. Someone could help me?
Hi there,
I've got a problem with my Z1. I am with 14.4.0.157 stock ROM, and locked BL.
I rooted it (working), then added Dual Recovery (working).
Then I tried to install DStriker ROM (http://forum.xda-developers.com/xperia-z1/development/rom-dstrikerz1-kai-rom-1-0-t2928666).
With TWRP, at the end of Aroma installer, I unticked 'reboot now' then bim, black screen, nothing possible to do, nothing worked : stucked at black screen. I pushed hard power off button, then at reboot : stuck at Sony logo.
I searched this forum and found how to make it back : I went to flashtool then reflashed stock, all was working again.
I made all the root and recovery operations. All was working. Then I tried with CWM Recovery. After install/reboot (as asked in the installation instructions) : stuck at Sony logo.
So I made (once again) all modifications to flash stock/root/recovery. So I tried another custom ROM : iHAckers one (http://forum.xda-developers.com/showthread.php?t=2716182). Aroma working well, install OK then reboot : STUCK again at Sony Logo !
In conclusion : only stock ROMs seem to work on my phone (or the ones flashed with Flashtool), I can root and install Recovery, install ROMs from recovery too, but impossible to boot on these new ROMs.
Searching for a solution to install a new custom ROM.
Any help ?
I guess I found something :
- I changed the Dual recoveyr script with the last one (I thought I already had) : I used the last one from http://nut.xperia-files.com/
- I loaded and rooted before with 14.4.A.0.108 stock version.
I don't know which one solved the problem. I guess it is the recovery script, but I will do more tests, I believe it can help someone...
I will keep you up-to-date.
i've had the same problem. The solution i found is that i should start the operation from stock 14.1.G.1.534. whenever i used another stock version, phone got stuck at sony logo.
1G1_2 said:
i've had the same problem. The solution i found is that i should start the operation from stock 14.1.G.1.534. whenever i used another stock version, phone got stuck at sony logo.
Click to expand...
Click to collapse
I think Xperia Z1 is against newer stock firmwares when we want to update.
So till I installed iHackers with the method I explained above (other stock firmware), I've never met the problem again.
I then flashed to Dstriker and no problem. I think there was something wrong when coming from stock/rooted/dual recovery/locked BL 14.4.A.0.157...
Best regards and happy new year all.
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.