Hi, my phone had a brick. Using the Flashtool and the Rom b108 I was able to repair it, but had a new brick a few hours later and now I am not able to repair it.
I can unlock the bootloader, but when I try to reinstall the rom the flashtool although it seems to work fine nothing happens on the phone (it stays showing the Huawei logo). The only thing that changes when I try to install a Rom is the bootloader (it's locked again when I try to install the b108), but the rest of the Rom is not installed (although the flashtool says yes), I discovered this because I tried to install a Rom with a modified recovery and when the installation ends my phone still has the official recovery.
Does anyone know if there is anything I can do?
PD: I apologize if I wrote something strange, I don't speak English and I had to use the google translator
Related
The new SEUS says that if the phone has modified software then it cannot be updated thus it cannot unbrick the phone right?
so if the case is like this. if i brick my phone with the installation of a custom rom then reverted to my working backup (Android 2.1 clean) will it be able to repair my phone even if it is rooted? has anyone tried this?
thanks
I only know this
When you bricked your phone, just enter to xRecovery and restore your backup
When you bricked your phone, just download and use x10flashtool and flash the X8 flash file
Sorry i just know this.. I didn't know anything about SEUS (because i never use it, when i use it, the update failed...)
I installed original firmware yesterday. Here is what I did. I had froyobread installed on my phone but since SEUS requires the original build.prop file of the SE firmware, I restored a backup of a SE ROM. Then the process went normally. SEUS didn't refuse to repair the phone.
Sent from my X8 using XDA App
howardmatthew168 is right! If you brick the phone you can flash the stock firmware with x10flashtool!
Hey guys!
My friend just got the G900F and I wanted to help him root it and install custom recovery + custom rom.
1. I installed custom recovery
2. I rooted the phone with towelroot
- Everything seemed to work perfectly, I used apps that required root and had no problems.
3. I made a backup of the phone's original software
4. I made a backup of the phone's EFS
5. I updated the modem+bootloader to Lollipop latest versions for G900F (I did this when I had 4.4.2 installed on the phone)
6. I booted into TWRP and made a total wipe
7. I Installed XtreStoLite INTL 2.2 - I choose Ktoonsez's kernel and NEE as I am from Sweden.
8. I rebooted the phone and now the phone is in an endless bootloop - says Set Warranty Bit: Kernel and the Samsung Logo, then it reboots and vibrates 2 times.
I've tried to reinstall TWRP via latest ODIN v.3.10 - it works to install but I cannot go into recovery as it just restarts and the same bootloop as step 8 happends.
I've tried to reinstall CF-Auto-Root via latest ODIN to restore the original Recovery - it works to install it, I can see on the phone that it is recovering original recovery et.c but after that it ends in a bootloop as step 8.
I have no problems getting into download mode, KNOX is 0x1.
I don't know what to do and I seem to lack the knowledge how-to search correctly to find an answer for this model(?) How can I either get back to stock or make a total clean adb fastboot?
I'm guessing its semi or hard bricked? I don't understand why as I followed the steps 100% from this guide http://forum.xda-developers.com/showthread.php?t=2699648
then I used the guidelines edgarf28 gives when installing the XtreStoLite rom and updating the modem/bootloader.
Help is very very appreciated.
Probably the Kernel not playing nice with the ROM
Install Samsung drivers on PC (KIES3 installs them, or grab from samsung.com)
Boot the phone into download mode (Volume Down, Home & Power)
Flash a stock ROM using ODIN 3.10.6 from sammobile dot com, or from the link in my Sig (United Kingdom G900F ROMS)
Great! Thanks. Exactly what I was looking for, I'm not the best on the search function. I did actually try to find the version needed to totally reboot via ODIN but didn't find it. I made the process and the phone works again, I will try to reproduce the steps but I guess I should skip Ktoonsez's kernel? Any idea why it doesn't work with it? As it is baked into the rom's aroma installer I thought it was compatible.
The kernel being the problem is just a guess, could have been something else, but from what you said, the only step I can see that might have bricked it was an incompatible Kernel, or maybe it didn't flash correctly and corrupted something
You can try flashing it again now you know how to recover the phone, see if it was just bad luck - best to reboot after each step to make sure it's working up to that step, then if it fails to boot after doing something else, you know exactly which step went wrong and can avoid it next time
Alright, made the exact same steps as before and it booted after every step. Last step was installing the ROM and it worked fine, after it says the same thing but this time I do not end up in a bootloop. Waiting for the phone to start for the first time, usually takes awhile.. I have seriously no idea what went wrong, only thing I could think of is that the phone was on 4.4.2 on the first try and the second I used your 5.0.. so.. conclusion is that.. that was the problem.
These things happen, I flashed back to KK to give it a try a few weeks ago, first flash ended in a bootloop, so I flashed the exact same KK ROM again, exact same process, second time it booted fine
It's what makes things like this fun & interesting I suppose, always something to learn
You're right! I'm happy that you helped me! Works perfect now, I'll continue to tweak things to give my friend the best experience... so nice to remove all the bloatware! What a beast compared to original.....
I have a xperia c4 e5303, is a awesome device and 5-6 days ago i wanted to use xposed firmware to enable a fake gyroscope.
AND THE HELL STARTED.
I had the device rooted with custom recovery twrp when i was in lollipop 5.1, i installed the firmware for xposed and the phone was stucked in "android optimization", for hours. I restarded it sometimes but nothing, so i formatted my device and when i rebooted it, i was stucked in "sony" logo screen, some minutes ago i founded that my phone was totally empty.
c: *internal screaming*
I waited the next day, i downloaded the ftf of original marshmallow 6.0 firmware for sony xperia c4 and i installed it on my device, then everything worked perfectly luckely.
Easy peasy lemon squeezy, or not?
Some hours after i founded that i couldn't use the recovery mode!
I searched and searched and i founded that the problem could be the bootloader,so i used a sony official guide to unlock that.
I couldn't finished that guide becouse with any connection, on any computer, android sdk can't install his components(such as google usb driver, that are required for that method), and the program just install everytime the same package in loop. I tried aaaallll the method in the universe for that, i tried also to install once per once the zip files of the downloaded package but it was totally useless.
So i founded another method after some days of searching (with flashtool) and now my bootloader is fully unlocked, if i use flashtool to unlock the bootloader, it says that is unlocked and ask me if i want to relock it so i think now the bootloader unlock is done. FINALLY.
Then, i turned off the phone and started it by pressing the volume down+power botton, and all the device did was reboot himself repitetly until i release hard keys and when i do it the phone start automatically.
I think my device now reboot himself instead of going in recovery mode.
What can i do i am totally frustrated about this and i really don't want to buy a new device becouse i don't have a gyroscope. I love my xperia c4, i just don't know why i can't get the recovery mode back to install twrp, for rooting the device, for retry to get xposed virtual sensor and then finally enjoy my vr experience...
In the end, i have a Xperia C4 5303 with original Marshmallow 6.0 firmware installed, that can't go in recovery mode in any ways.
Pls someone help me..
no one?..
No one here know hot to save my smartphone?
update: now i can use fasboot and adb commands becouse i installed the drivers properly.
but i still can't flash a custom recovery to get the root..
asnachan said:
update: now i can use fasboot and adb commands becouse i installed the drivers properly.
but i still can't flash a custom recovery to get the root..
Click to expand...
Click to collapse
Digging through XDA (next time use the website's search bar, tee hee hee) I found this thread:
https://forum.xda-developers.com/xp.../bootloader-unlocked-custom-recovery-t3285521
Edit: I know it says C5 Ultra whatever but the thread says it also works with your model (C4 E5303 no?)
Before trying anything, I'd seriously recommend reading all eleven pages so you don't miss anything and end killing your phone (or back at square 1).
I'm not an expert on Android or anything (I personally have only owned 1 device — a first gen Moto G), but the method presented in the thread is very odd. Are all Xperia phones this weird?
Read carefully — some steps might be unnecessary (after all, you already unlocked your bootloader [maybe?])
P.S. you lost the recovery because by installing the original firmware it basically got erased (original firmware didn't have TWRP after all!)
P.S.S. you should create a backup once you get TWRP up and running, just in case.
I can't help you more than this because I do not own the device, so I cannot share ~personal wisdom~ with you (beyond recommending the Moto G series).
Good luck!
( And search the forums and threads before posting — that's an XDA rule! )
Sent from my Motorola Moto G using XDA Labs
thx
Bludwurst said:
Digging through XDA (next time use the website's search bar, tee hee hee) I found this thread:
https://forum.xda-developers.com/xp.../bootloader-unlocked-custom-recovery-t3285521
Edit: I know it says C5 Ultra whatever but the thread says it also works with your model (C4 E5303 no?)
Before trying anything, I'd seriously recommend reading all eleven pages so you don't miss anything and end killing your phone (or back at square 1).
I'm not an expert on Android or anything (I personally have only owned 1 device — a first gen Moto G), but the method presented in the thread is very odd. Are all Xperia phones this weird?
Read carefully — some steps might be unnecessary (after all, you already unlocked your bootloader [maybe?])
P.S. you lost the recovery because by installing the original firmware it basically got erased (original firmware didn't have TWRP after all!)
P.S.S. you should create a backup once you get TWRP up and running, just in case.
I can't help you more than this because I do not own the device, so I cannot share ~personal wisdom~ with you (beyond recommending the Moto G series).
Good luck!
( And search the forums and threads before posting — that's an XDA rule! )
Sent from my Motorola Moto G using XDA Labs
Click to expand...
Click to collapse
Thanks a lot for your time, but i am using that thread to root this, and i am stucked at the last point becouse i don't know what he means with:
"THIS IS IMPORTANT
The rom has
Code:
recovery.from.boot.p"
I did all the steps except for that, and i get no errors but when i try to boot in recovery the phone just stay on the logo and then after some minutes reboot himself and starts normally.
i already ask what the last point is in that thread
p.s.: i know i will not have twrp if i reinstall stock fw, but the point is that i don't have also the normal recovery, i can't access to that via adb or via hard keys..
asnachan said:
Thanks a lot for your time, but i am using that thread to root this, and i am stucked at the last point becouse i don't know what he means with:
"THIS IS IMPORTANT
The rom has
Code:
recovery.from.boot.p"
I did all the steps except for that, and i get no errors but when i try to boot in recovery the phone just stay on the logo and then after some minutes reboot himself and starts normally.
i already ask what the last point is in that thread
p.s.: i know i will not have twrp if i reinstall stock fw, but the point is that i don't have also the normal recovery, i can't access to that via adb or via hard keys..
Click to expand...
Click to collapse
Ah. You should've mentioned it (i.e. linked to the guide). Sorry sorry!
Read further down. The "recovery.from.boot.p" is this thing that overwrites TWRP with the stock recovery. Following the «THIS IS IMPORTANT» indication are instructions to get rid of the thing, and so being able to keep TWRP permanently.
You need that last step to succeed.
Sent from my Motorola Moto G using XDA Labs
in the other thread they said to me to roll back to 5.1 i am doing it now
nvm i got hard brick, the phone is dead and i can't enter in download mode....
asnachan said:
nvm i got hard brick, the phone is dead and i can't enter in download mode....
Click to expand...
Click to collapse
I'm very sorry to hear that ?
Sent from my Motorola Moto G using XDA Labs
Is fine, i had to buy another phone that is why is tarted to root the xperia.
just..i'm out from the world of rooting i think. i broke 2 devices 1 by flashing a original rom with sony original flashtool and 1 by installing a root with kigroot, and now on that i can't read the sim.
i wait until the world of rooting will be more stable and with more official custom roms...
RIP
Hi, the other day i got a new P10 Lite(WAS-LX1A), i wanted to install a new OS it but i only could install TWRP, i thought i installed the root but no, i made a tutorial of how to change the custom rom but i bricked the phone, now when i boot it, it only appears a screen that says:"Your device has been unlocked and can't be trusted.
To learn more,visit:
(There is a link here but it doesn't work)
(Some useless instruccions here)
Your device is booting now...".
I only can get into fastboot and eRecovery, all the roms i try to install doesnt work and i dont know my build number so i dont know the exact rom i was using before bricked.
Any ideas?
Hi,
I was really unhappy with Pie and tried to prepare my device for Oreo downgrade.
What I did was
- unlock bootloader
- tried to install TWRP
- mixed something up in that processs
- realized TWRP cannot be installed apparently on Pie right now
- MiFlash seems to be not working as well when trying to install stock rom (says flashing but nothing happens)
Well Pie is running right now, but when trying to lock the bootloader again for future updates, the phones is only showing a black screen.
After that I am trying to unlock bootloader again (fastboot oem unlock) and everything works again, except when I try to boot into recovery ("the system is destroyed" or something like that).
Trying to "hotboot" into TWRP currently is also not working, "unable to mount..." and after that automatically reboots into the system itself.
Any idea how I can either put a standard Pie installation with working recovery and locked bootloader on?
Or how I can maybe install Oreo instead? As I said, the MiFlash tool doesn't do anything (tells me "flashing" but actually doesn't do anything).
Thanks for your help!
cyrrel said:
Hi,
I was really unhappy with Pie and tried to prepare my device for Oreo downgrade.
What I did was
- unlock bootloader
- tried to install TWRP
- mixed something up in that processs
- realized TWRP cannot be installed apparently on Pie right now
- MiFlash seems to be not working as well when trying to install stock rom (says flashing but nothing happens)
Well Pie is running right now, but when trying to lock the bootloader again for future updates, the phones is only showing a black screen.
After that I am trying to unlock bootloader again (fastboot oem unlock) and everything works again, except when I try to boot into recovery ("the system is destroyed" or something like that).
Trying to "hotboot" into TWRP currently is also not working, "unable to mount..." and after that automatically reboots into the system itself.
Any idea how I can either put a standard Pie installation with working recovery and locked bootloader on?
Or how I can maybe install Oreo instead? As I said, the MiFlash tool doesn't do anything (tells me "flashing" but actually doesn't do anything).
Thanks for your help!
Click to expand...
Click to collapse
https://forum.xda-developers.com/mi-a1/development/treble-twrp-installer-treble-manager-t3793637
Hi,
I somehow managed to put 8.1 on and everything is back to normal.
Thanks
cyrrel said:
Hi,
I somehow managed to put 8.1 on and everything is back to normal.
Thanks
Click to expand...
Click to collapse
can you explain us the procedures that you have followed to downgrade. It would be really helpful. i have tried this
method but it didn't work for me. i am facing IMEI 0/no signal issues using this method.
Thanks
well I have done a lot of stuff that made my phone not working anymore because using a wrong .img file and didn'T understand the tutorial (same link you have provided) fully.
But at the end it was quite close to the link you have sent, the MiFlash tool I needed for example to try like 10 times per step until it worked, maybe a bad cable - I don't know.
But finally it was working, after March update without network signal, but with /boot & /efs partitions and Nov fastboot image, it was working.
If you need any more detail for a specific step, you can of course ask and I can check if there was anything special I can remember
cyrrel said:
well I have done a lot of stuff that made my phone not working anymore because using a wrong .img file and didn'T understand the tutorial (same link you have provided) fully.
But at the end it was quite close to the link you have sent, the MiFlash tool I needed for example to try like 10 times per step until it worked, maybe a bad cable - I don't know.
But finally it was working, after March update without network signal, but with /boot & /efs partitions and Nov fastboot image, it was working.
If you need any more detail for a specific step, you can of course ask and I can check if there was anything special I can remember
Click to expand...
Click to collapse
Are your imei & mac same as original? won't the imei/mac get affected by restoring someone else efs?
I don't know about mac, but imei is ok