Hello,
I am completely new in this rooting/flashing etc, so sorry for a maybe stupid question, and please, if you can help, try to give me detailed instructions. I read some posts on this subject, but it is not obvious to me how to move forward...
I had a running stock firmware. My intention was to root the phone but stay on the stock firmware.
1. I followed Sony's tutorial for unlocking the bootloader:
https://developer.sony.com/develop/...d/unlock-bootloader/how-to-unlock-bootloader/
2. I followed this tutorial for installing TWRP:
https://twrp.me/sony/sonyxperiaxcompact.html
3. I restarted into TWRP
I looked around and wanted to boot the android again
Now I just see alternating screens
black "your device has been unlocked..." screen <-> Sony logo
How to get it working again?
For now I used Sony flash tool:
https://developer.sony.com/develop/open-devices/get-started/flash-tool
and installed the latest available firmware - it seems that I am back on the stock firmware. Ok, better than bricked phone. Yet, I wonder how to proceed with the root? I thought that the TWRP would allow me to install SuperSU(https://supersuroot.org/) and that would be sufficient for me.
Related
I understand there are probably other threads but it gets difficult to follow and ensure I have the latest and most relevant instructions
I have a N4 rooted with CWM recovery. I can't update to 4.3 as it just restarts into the recovery mode but doesn't actually flash anything, I restart the phone and it goes back to 4.2.2
What exactly do I need to do?
NOTE: I also have the USB OTG kernel installed. Otherwise stock rom. I want to keep all of my existing data/settings
Please don't link to a very large general thread which is hard to follow. If I can have a breakdown of the exact steps required i'd much appreciate it. Thank you
Hello,
I installed KANGAPOP v2.5★|►LOLLIPOP GPE (5.0) while on GOLDFINGER v9 (4.4.2). Then everything was just fine before I had my corporate account linked to it which required device to be encrypted. I did that and since then the phone is stuck in boot loader loop (four balls are playing around!). Waited for 5-6 hours before rebooting the device. Had the Nandroid backup for old ROM but when I entered TWRP it was not able to mount /data (may be due to encryption). I am not sure which bootloader I am in but some help is suggesting to install I337UCUAMDL_I337ATTAMDL_ATT via Odin by following guide here,
http://forum.xda-developers.com/showpost.php?p=56453100
But this guide reads,
Who SHOULD NOT use this guide?
-- SGH-I337 users with a MDB or MDL bootloader. (Don’t use this guide or you’ll be locked down for good.)
Not use MDL! I am confused and asked to post here. Few questions I've.
1. Since I only have access to TWRP (without /data and may be some other partitioin), Is there a way to see which bootloader my phone is on right now?
2. Rather than going through ODIN is there a way to decrypt the partition and restored the phone via TWRP?
3. If I had to go through ODIN then what stock version should I use and where can I get one?
I know I made a really bad mess out of it but need solution to get the phone back working. I am seating on the 4th day to dead phone, and it needs life.
raone26 said:
Hello,
I installed KANGAPOP v2.5★|►LOLLIPOP GPE (5.0) while on GOLDFINGER v9 (4.4.2). Then everything was just fine before I had my corporate account linked to it which required device to be encrypted. I did that and since then the phone is stuck in boot loader loop (four balls are playing around!). Waited for 5-6 hours before rebooting the device. Had the Nandroid backup for old ROM but when I entered TWRP it was not able to mount /data (may be due to encryption). I am not sure which bootloader I am in but some help is suggesting to install I337UCUAMDL_I337ATTAMDL_ATT via Odin by following guide here,
http://forum.xda-developers.com/showpost.php?p=56453100
But this guide reads,
Who SHOULD NOT use this guide?
-- SGH-I337 users with a MDB or MDL bootloader. (Don’t use this guide or you’ll be locked down for good.)
Not use MDL! I am confused and asked to post here. Few questions I've.
1. Since I only have access to TWRP (without /data and may be some other partitioin), Is there a way to see which bootloader my phone is on right now?
2. Rather than going through ODIN is there a way to decrypt the partition and restored the phone via TWRP?
3. If I had to go through ODIN then what stock version should I use and where can I get one?
I know I made a really bad mess out of it but need solution to get the phone back working. I am seating on the 4th day to dead phone, and it needs life.
Click to expand...
Click to collapse
If you don't get any help soon you could just flash the stock firmware and that usually takes care of soft bricked phones.
Sorry if this didn't help!
Hi everyone,
I have a Note 4 Exynos version and recently i decided to make the root procedure. My steps was first update to 5.1.1 then, root by flashing the su zip file, flashing TWRP recovery and then i did a full backup to make sure i can keep my files intact just in case. I tried installing CM 12.1 but i had the " Execute updating binary failed etc..." and after a lot of tries i decided to restore my backup. The problem is that after restoring my phone keeps rebooting in randomly.. Can i unroot without flashing stock firmware, so i can keep my backup as it is?
Any thoughts appreciated.
5.1.1 can't be root just yet.
Flash stock rom & setup your phone to fix it.
You can flash another rom after that
So that is the reason for the random rebooting? To be honest i followed the procedure from a known website that was talking about rooting this particular phone with version 5.1.1 ...
Thanks for the response
I'm expecting my 910c to arrive soon and I'm currently reading for root procedures.
So, if my phone arrives with 5.1.1, I won't be able to root? and if I root can I later flash 5.1.1 without problems?
Also, please direct me to a threat that is safe to follow in order to root.
Of course you can root 5.1.1
Just read the development section and follow the instructions there
sent from somewhere
Antreassy i have followed the procedure from a website i do not wish to quote since it might be against the forum rules. But the result was not the best since my phone keep rebooting. So the only thing that saved it is by flashing the stock 5.1.1 firmware using odin and everything came back to normal.
From my own research i believe that at the moment the most valuable custom firmware is CM 12.1 and that is the reason i tried to flash it at first but without any success.
Hello,
In a late-night act of utter stupidity, when over-tired, I re-flashed the boot recovery with TWRP and bricked my M3. It obviously can't now enter boot recovery.
I've used TWRP and successfully re-flashed custom roms on my original Mate, and changed regions. (Not in any way an expert, I know how to follow instructions.)
I was trying to convert my Chinese (I was living there) ROM to UK. It's tricky nowadays.
This was a stupid error when tired. Any way back?
I read somewhere that people with the right hardware can do it, but finding someone. I'm in Leeds, UK.
The pad does (did) what I need, and I'm not in a position to buy a new one. If it's dead, it's dead; and I can move on.
Cheers in advance for any input.
SOLVED
See my last post on this thread.
After using Multi Tool V8 to enquire into the machine I switched off and rebooted.
It came back with a "Wipe cache" and "Reset to factory settings" Huawei screen, so I did both and - It booted!
It had spectacularly failed to do anything but boot-loop since coming out of a very dead battery yesterday.
1) Boot recovery, OTA recovery, and dload recovery from SD were all unavailable after the original overwriting of the bootloader.
2) After being dead for months, all recovery options booted from power button plus vol- Vol+ and Vol+/- - but still bootlooping.
Then, suddenly it booted into wipe cache/factory reset screen.
Android 7, EMUI 5.1.3
I have no idea why.
Now fully working. (Including restarting)
I fell in a similar situation after having flashed a magisk module .. unfortunately my nandroid backup didn't restore my devices, but I was able to enter in twrp recovery.. so,..
if you can boot in twrp recovery, not all hopes are lost..
first of all, you must download a stock firmware for your device (i suggest to download trough huawei firmware finder: https://forum.xda-developers.com/tools/general/huawei-firmware-finder-team-mt-t3469146/amp/)
You must download a fullota version of stock firmware
then, you can flash this firmware (3 zip files) trough hurupdater via twrp recovery: https://forum.xda-developers.com/ho...lash-official-firmware-recovery-t3769279/amp/
in order to not overwrite twrp recovery, put the twrp.img file in the same folder and rename it to recovery.img
you can find more info in this topic (follow the instructions, in particular those on how to use hurupdater): https://forum.xda-developers.com/me...ting-btv-dl09-to-unapproved-firmware-t3817541
in order to find a firmware suitable to your device, try to find info on it: you have a mediapad m3 European? American? asian? just wifi or also 4G-LTE (whit a sim and phone functions)? lite or normal version? 10 inches or 8.4?
everyone of these devices have different codenames and suitable firmwares
I found exact firmware for my devices with the procedure described here:
https://forum.xda-developers.com/showpost.php?p=77241673&postcount=3
.. but, if you flashed a wrong firmware, i really don't know if it might help you..
anyway, i wish the info above could help you.
qllkevuoi said:
I fell in a similar situation after having flashed a magisk module .. unfortunately my nandroid backup didn't restore my devices, but I was able to enter in twrp recovery.. so,..
if you can boot in twrp recovery, not all hopes are lost..
first of all, you must download a stock firmware for your device (i suggest to download trough huawei firmware finder: https://forum.xda-developers.com/tools/general/huawei-firmware-finder-team-mt-t3469146/amp/)
You must download a fullota version of stock firmware
then, you can flash this firmware (3 zip files) trough hurupdater via twrp recovery: https://forum.xda-developers.com/ho...lash-official-firmware-recovery-t3769279/amp/
in order to not overwrite twrp recovery, put the twrp.img file in the same folder and rename it to recovery.img
you can find more info in this topic (follow the instructions, in particular those on how to use hurupdater): https://forum.xda-developers.com/me...ting-btv-dl09-to-unapproved-firmware-t3817541
in order to find a firmware suitable to your device, try to find info on it: you have a mediapad m3 European? American? asian? just wifi or also 4G-LTE (whit a sim and phone functions)? lite or normal version? 10 inches or 8.4?
everyone of these devices have different codenames and suitable firmwares
I found exact firmware for my devices with the procedure described here:
https://forum.xda-developers.com/showpost.php?p=77241673&postcount=3
.. but, if you flashed a wrong firmware, i really don't know if it might help you..
anyway, i wish the info above could help you.
Click to expand...
Click to collapse
Thanks for the reply, and sorry for the delay. New child has somewhat taken over our lives!
I'll take a look at the tablet again when I have time, probably next month.
Update - Bootloader working after battery drain: Now what?
[Edit] Post redundant as it started working - see OP.
NwotNot said:
Thanks for the reply, and sorry for the delay. New child has somewhat taken over our lives!
I'll take a look at the tablet again when I have time, probably next month.
Click to expand...
Click to collapse
Well...
After being without power for so long I turned the tablet on and it booted!
However, it then went into OTA and updated - rebooted - and locked the damned bootloader.
1) It's showing as rooted.
2) Boot loader is locked.
3) Fastboot & rescue mode comes up.
4) Recovery (OTA) still comes up but "Fails" this time.
I don't recall how I unlocked it last time. I don't ever rememebr an unlock code.
Status:
Fastboot reports it exists.
ADB reports "Null" not found. (ADB drivers installed).
Firmware version: CPN-AL00C233B078
Device name: CPN-AL00
Serial Number: Showing
IMEI: Showing
Bootloader state: LOCK
I have an old TWRP backup - don't know how to use it.
Solutions?
a) Any kind devs prepared to work with me and find the boot unlocker code for this 5-year old tablet?
b) Any other solutions now we know what's what?
I'm self employed without income in this pandemic and can't really afford to buy a new tablet. If I have to, it won't be Huawei.
(There's a T3 10.6" at £89, but I'm not biting - I need to sort out a budget tablet with at least the oomph of the M3.)
Any help much appreciated. :good:
David.
Hiya, after redoing lafsploit on my v20, the device only boots to recovery and only twrp 3.4.0-1 works. anything newer and it boots to fastboot.
as we all know, LG has crippled fastboot.
device also crashes/reboots any time you try and write to the device be it flashing roms or copying a file with twrp.
anyway, I'm looking for a solution.
Hey Eriklion,
I am not a pro, in fact I have only rooted my Samsung Galaxy S4 so far, and right now reading everything I can to root my H918, so read what I wrote with a healthy dose of skepticism, because I am most likely completely wrong, but, since no one else is responding I am compelled to try.
If you have followed the thread:
Step by step guide for lg v20 h918 unlocking, downgrading, rooting and twrp
STEP BY STEP GUIDE FOR LG V20 H918 UNLOCKING BOOTLOADER, DOWNGRADING, ROOTING AND INSTALLING CUSTOM ROMS (NOOB FRIENDLY) DISCLAIMER: I'M NOT THE DEVELOPER OF ANY OF THE BELOW SOFTWARE'S AND YOU PROCEED WITH YOUR OWN RISK AS THIS INVOLVES...
forum.xda-developers.com
to KDZ downgrade to "h" and then use lafsploit to flash the TWRP, then in those instructions, there is a slight error:
the instructions do not clearly specify to use only a particular version of the TWRP, yet, that seem to be the requirement.
You can see that discussed in:
H918 Stuck on secure startup "decryption unsuccessful" on boot
after doing this https://forum.xda-developers.com/v20/how-to/step-step-guide-lg-v20-h918-unlocking-t3808258 and finally installing a stock based rom, which is Alpha Omega Rom. I get stuck at secure startup and telling that decryption...
forum.xda-developers.com
Now, in your case, you do not have a decryption issues, but I think the actual results may vary, depending on what version of recovery you flashed using the lafsploit from FWUL.
As to how to fix..? Well in the latter mentioned thread they seem to all suggest fastboot flashing the correct version of TWRP, being very careful not to forget to use advanced format data from the boot to the TWRP that is immediately follows the TWRP flashing process. However, everything I read seem to be telling me that the flash over the fastboot is impossible for the H918 (and I think you mentioned this in your OP), so IDK what they are talking about.
May-be it is possible to reload the TWRP (this time a correct version) the same way you just installed the 3.4.0-1?
If not, may-be reflashing back the "h" KDZ, and then flashing the correct (3.2.3-4) version of TWRP from FWUL?
And do not forget that advanced format of data partition, which has to be completed no later than the first boot to TWRP immediately after TWRP is flashed on, i.e. before the device gets to complete even one boot to system!
This is all I can say. Please, let us know if your issue is resolved and if yes then how. Good luck!
Hi Eriklion, any progress for your situation?