Database Users

[Q] Bricked i9505

This morning I was attempting to update the firmware on my i9505.
I downloaded and extracted the .tar.md5 file and opened Odin in administrator mode.
Stupidly I then added the downloaded file as Phone and not PDA and pressed start in Odin. Unsurprisingly it failed.
I downloaded and tried other firmware (as Phone) before I realised my error.
When I boot the phone "normally" I get the failed firmware update message and have tried Kies but it can't connect to the phone.
Download mode does work, but when I try with the firmware (stock and pre-rooted) as PDA it always fails.
Can someone please help to recover my phone? I'm feeling pretty stupid just now

floydart said:
This morning I was attempting to update the firmware on my i9505.
I downloaded and extracted the .tar.md5 file and opened Odin in administrator mode.
Stupidly I then added the downloaded file as Phone and not PDA and pressed start in Odin. Unsurprisingly it failed.
I downloaded and tried other firmware (as Phone) before I realised my error.
When I boot the phone "normally" I get the failed firmware update message and have tried Kies but it can't connect to the phone.
Download mode does work, but when I try with the firmware (stock and pre-rooted) as PDA it always fails.
Can someone please help to recover my phone? I'm feeling pretty stupid just now
Click to expand...
Click to collapse
do you have custom recovery that you can boot into it?

samersh72 said:
do you have custom recovery that you can boot into it?
Click to expand...
Click to collapse
djembey sent me a couple of files and a ROM passed in Odin.
I don't think it's loading though as it's stuck on the SAMSUNG logo (and has been for about 15 mins) ....

floydart said:
djembey sent me a couple of files and a ROM passed in Odin.
I don't think it's loading though as it's stuck on the SAMSUNG logo (and has been for about 15 mins) ....
Click to expand...
Click to collapse
remove battery then insert it, boot into recovery, wipe cache and data, reboot

samersh72 said:
remove battery then insert it, boot into recovery, wipe cache and data, reboot
Click to expand...
Click to collapse
I rebooted to recovery and did a wipe data then a wipe cache. Recovery crashed and the phone rebooted.
This time the boot sound played completely and my phone is back to initial setup screen - thank you :good:

floydart said:
I rebooted to recovery and did a wipe data then a wipe cache. Recovery crashed and the phone rebooted.
This time the boot sound played completely and my phone is back to initial setup screen - thank you :good:
Click to expand...
Click to collapse
Did you feel the adrenalin flowing? I thought I bricked mine earlier. We had a mini power cut half way through flashing and it booted up with "Connect to Kies to do emergency firmware upgrade" or something like that. lol
Felt the cheeks of my bum twitch a bit there. lol
Managed to reflash one of the few stock ROMS I have to hand.

artnada said:
Did you feel the adrenalin flowing? I thought I bricked mine earlier. We had a mini power cut half way through flashing and it booted up with "Connect to Kies to do emergency firmware upgrade" or something like that. lol
Felt the cheeks of my bum twitch a bit there. lol
Managed to reflash one of the few stock ROMS I have to hand.
Click to expand...
Click to collapse
Aye, you could say that
I would say that I won't try flashing again after 3 or 4 hours sleep, but knowing me I probably will ....

S4 bricked after freeze during unmount internal sdcard
Dear friends. I need your help!
I did the actualization on my S4 i9500 (I9500XXUAMDK with root) and after this, I was trying to put more space in my SDcard (editing vold fstab files). During this process, appeared a message on phone about one error in sdcard and it suggested me to unmount the sdcard to try solve the problem. So, when I click yes, the phone froze and then I turned it off, but now it dont pass to Sangung Logo and the phone just go in recovery mode. In recovery mode I tryied clear/mount/unmount some file, but return with error to mount any directories.
I think the phone have the files or some partition corrupted!!! I can access it through ODIN and adb shell as well. There is (in adb commands) a command to fix the partition? How can I do?
I can access the phone in ODIN, and I tried to re-install the original FW. It did well (OK for update), but the phone cant finish the instalation after, because it cant mount anything. And returns to recovery mode with many messages about it cant mount directories.
Every thing I try to do, the phones (in recovery mode) returns "cant mount... or error to mount". I as said, I cant clear cache, format /sdcard or other directory or reset to factory data as well (because I think, the system cant mount any directories).
Somebody had this problem or could help me to solve it, please!!!
Tks in advance!
Barros

rgbarros said:
Dear friends. I need your help!
I did the actualization on my S4 i9500 (I9500XXUAMDK with root) and after this, I was trying to put more space in my SDcard (editing vold fstab files). During this process, appeared a message on phone about one error in sdcard and it suggested me to unmount the sdcard to try solve the problem. So, when I click yes, the phone froze and then I turned it off, but now it dont pass to Sangung Logo and the phone just go in recovery mode. In recovery mode I tryied clear/mount/unmount some file, but return with error to mount any directories.
I think the phone have the files or some partition corrupted!!! I can access it through ODIN and adb shell as well. There is (in adb commands) a command to fix the partition? How can I do?
I can access the phone in ODIN, and I tried to re-install the original FW. It did well (OK for update), but the phone cant finish the instalation after, because it cant mount anything. And returns to recovery mode with many messages about it cant mount directories.
Every thing I try to do, the phones (in recovery mode) returns "cant mount... or error to mount". I as said, I cant clear cache, format /sdcard or other directory or reset to factory data as well (because I think, the system cant mount any directories).
Somebody had this problem or could help me to solve it, please!!!
Tks in advance!
Barros
Click to expand...
Click to collapse
Why on Earth would you mess around with stuff like that? I hope you get help here, and next time just flash it and don't mess around. Perhaps get an external SDCard to solve your "space" problem.

artnada said:
Why on Earth would you mess around with stuff like that? I hope you get help here, and next time just flash it and don't mess around. Perhaps get an external SDCard to solve your "space" problem.
Click to expand...
Click to collapse
hehehe... I agree totally with you. But, it wasnt brick because there is some mistake in vold.fstab edition (I suppose). My fault is to accept unmout sugestion in the phone message.
But, it has a soft brick now. I got the access thought adb and odin and I'm trying to find a valid pit to rebuild the partition, that I think is corrupted now (I cant mount anything there. I can access it, but not change anything there).
I found a post here that there is a pit file. I cant ask there because I dont have enough privileges to post in development topic. The links are http://forum.xda-developers.com/showthread.php?t=2217777 and http://forum.xda-developers.com/showthread.php?t=2214865
I´d like to know if this pit (the second link has a file attached), is a valid pit. If yes, I could fix the phone!!!
Tks

rgbarros said:
hehehe... I agree totally with you. But, it wasnt brick because there is some mistake in vold.fstab edition (I suppose). My fault is to accept unmout sugestion in the phone message.
But, it has a soft brick now. I got the access thought adb and odin and I'm trying to find a valid pit to rebuild the partition, that I think is corrupted now (I cant mount anything there. I can access it, but not change anything there).
I found a post here that there is a pit file. I cant ask there because I dont have enough privileges to post in development topic. The links are http://forum.xda-developers.com/showthread.php?t=2217777 and http://forum.xda-developers.com/showthread.php?t=2214865
I´d like to know if this pit (the second link has a file attached), is a valid pit. If yes, I could fix the phone!!!
Tks
Click to expand...
Click to collapse
i think it is the right pit file for I9500 "Adonis.pit"

samersh72 said:
i think it is the right pit file for I9500 "Adonis.pit"
Click to expand...
Click to collapse
+1
@rgbarros: That is for I9500. Do not try it for I9505

stress nsitylf
samersh72 said:
i think it is the right pit file for I9500 "Adonis.pit"
Click to expand...
Click to collapse
Tks samersh72. I'll try it and I'll give the feedback after. :fingers-crossed:

demlasjr said:
+1
@rgbarros: That is for I9500. Do not try it for I9505
Click to expand...
Click to collapse
Tks demlasjr. My phone is a i9500 (not the ...905).
I run the adonis.pit on pit magic and it generated a analisys report (attached). Before I put it to run on ODIN, you (or somebody) could give a feedback about the entry memory below:
----------------------------------------------------------
Entry Memory Address: 0x754
----------------------------------------------------------
Binary Type: 0 (UNKNOWN)
Device Type: 2 (MMC)
Identifier: 12
Attribute: 5 (READ / WRITE)
Update Attribute: 1 (FOTA)
Block Size: 196.608
Block Count: 16.384
File Offset (Obsolete): 0
File Size (Obsolete): 0
Partition Name: CDMA-RADIO
Flash FileName: modem_cdma.bin
FOTA FileName:
My doubt is about the Partition Name CDMA-RADIO. Is this correct for a i9500 S4? I just really confirm and just to avoid to brick totally my phone, because when I run this pit through ODIN, or fix it or break it (no more chances to revive it)!!!
Tks very much!!!

I've seen that you have the 9500 later, but the forum was down and I couldn't edit my post. On that thread is a discussion about it. Somebody days that may be from 9502. I just seen the art you posted there, try adding this info too, including the pit magic report. Kinda hard to get confirmation and a trustful pit yet.
Sent from my GT-I9300 using Tapatalk 2

demlasjr said:
I've seen that you have the 9500 later, but the forum was down and I couldn't edit my post. On that thread is a discussion about it. Somebody days that may be from 9502. I just seen the art you posted there, try adding this info too, including the pit magic report. Kinda hard to get confirmation and a trustful pit yet.
Sent from my GT-I9300 using Tapatalk 2
Click to expand...
Click to collapse
Dear demlasjr, the forum was down and I forgot to attach the pit magic report when the forum goes up. Im attaching the files now (magic pit report and the adonis.pit that I got in other topic about S4 forum).
If you (or somebody) could help me to analyse it and give us a feedback if this pit is a valid pit for samsung S4 i9500, I will thank a lot!!!
Ps.: I´m trying to solve the problem too, looking for a way to mount the files through adb shell, because I got access my phone with this way and I can see all the files inside there. I just cant to mount any drive yet. Is it possible the problem be only a vold.fstab file corruption or missed? And in this case, is only to solve this file (vold.fstab) to revive my phone?
Or there is a some command in adb shell that could repair the structure files (like scandisk for dos?). I'm newbie on linux and I'm trying to use fsck command, but it returns a error message (fsck: not found). I dont know if I'm putting a correct/complete command to scan and repair the system/drives/files (or if there is a error)...
So, I´m trying to solve it using 3 differents ways of thinking (finding a valid pit, edit/restore vold.fstab and find a correct adb command line to scan and repair eventually corrupt files/directories) and if I solve the problem, I'll be happy to post a tuto here to help some other guys in the future.
Until there, Im working to find a solution.
Tks for help me!!!

nothing worse than this feeling. I remember when I did this to my S2, felt a cold sweat instantly... :crying:

crimptool said:
nothing worse than this feeling. I remember when I did this to my S2, felt a cold sweat instantly... :crying:
Click to expand...
Click to collapse
I agree totally with you my friend!!! I put it down in the first day I bought it... Its terrible!!! hehehe I put other phones down too, but how the others were olds phones (more then 6 months in the market), always I found the cfw or pit's to revive...
S4 is a newest phone, so, there is not a consistent or many topics/files/cfw tested yet. I´m looking for 3 full days about this and I found a lot of topics in how to root/unroot the phone, but not yet about pits, commands, etc...
The problem is that phone has a corruption files inside (my first diagnostic) and this is avoid to flash any firmware there until I fix this problem.
I´m trying to keep calm to avoid to worst the situation. I can access the phone yet, so I see a light in the end of tunnel yet!!!
But, the feeling is terrible!!! hahaha

Until Odia or GSMCN came back to you, we can't help you my friend. Only them can confirm the .pit file comparing the one already published with his phone's pit file.
One question....what if you try Emergency recover in KIES. Connect your phone to pc, open KIES, open emergency recover and insert your phone serial number. I read that people messed some times with the partitions and KIES saved their phone. It will not hurt to try, KIES is a putty compared with the repartitioning.

demlasjr said:
Until Odia or GSMCN came back to you, we can't help you my friend. Only them can confirm the .pit file comparing the one already published with his phone's pit file.
One question....what if you try Emergency recover in KIES. Connect your phone to pc, open KIES, open emergency recover and insert your phone serial number. I read that people messed some times with the partitions and KIES saved their phone. It will not hurt to try, KIES is a putty compared with the repartitioning.
Click to expand...
Click to collapse
I tried to connect it in KIES, but KIES didnt recognizes the phone. I'll try once again!!! I think I really discovered what the problem is, reported by adb parted command in /dev/block/mmcblk0: "error: Both the primary and backup GPT tables are corrupt. Try making a fresh table, and using Parted´s rescue feature to recover partitions"
So, probably when the phone froze during unmounting sdcard, the partitions were corrupted. I'm really thinking to use the adonis.pit, due I think there is no other manner to solve the problem.
I'm waiting any reply from Odia, to see if him can help me. Otherwise, I'll cross fingers and press "enter", to see what happen!!!
My friend, tks for all!!! After I´ll post the results!!! :fingers-crossed:

(Help) Note 4 bricked, unable to mount data

Hi guys, i have some big problems with my n910f, tried to upload a pic to facebook and my phone crashed.
It simply does nothing, not booting, not charging, download and stock recovery are working.
I tried everything possible>
*flashed 3 different stock firmwares with odin
*tried a pit file repartion in odin
*wiped cache, did a few factory resets from stock revovery
*bought a new battery
*tried to root and flash a custom recovery but doesnt work
It is simply as bricked as it could be, the only information about this i have is stock recovery telling me unable to mount /data
So it seems my filesystem got corrupted as hell
The question is, how do i repair it?
Like i said pit file and bootloader flash did nothing, odin lets me flash everything without an error but it doesnt help.
I assume i could somehow repair it with adb fastboot but how?
Any help is welcome!

atilla88 said:
Hi guys,
Any help is welcome!
Click to expand...
Click to collapse
It may or may not help but I would sure try Kies. You NSFW get done errors like Kies telling you is not compatible bit but I would try the firmware initialization.

CodeNameRedNeck said:
It may or may not help but I would sure try Kies. You NSFW get done errors like Kies telling you is not compatible bit but I would try the firmware initialization.
Click to expand...
Click to collapse
Well i forgot to mention that i tried kies aswell, everyhting went good but didnt help, still nothing.
It confuses me a bit that it doesnt even charge, could a broken filesystem lead to this?

atilla88 said:
Well i forgot to mention
Click to expand...
Click to collapse
I am not sure what parts of the system need to be working for the battery to be able to charge. Good luck.

CodeNameRedNeck said:
I am not sure what parts of the system need to be working for the battery to be able to charge. Good luck.
Click to expand...
Click to collapse
did try root=> costum recovery for your variant => installing costum roms for your variant (all can be done with odin +sd card and some fils on it) but warranty is lost it may worth the try
did you try the 5 flashing fils(pit pda bl csc phone) to initial stocks with odin

ZOHUHRZED said:
did try root=> costum recovery for your variant => installing costum roms for your variant (all can be done with odin +sd card and some fils on it) but warranty is lost it may worth the try
did you try the 5 flashing fils(pit pda bl csc phone) to initial stocks with odin
Click to expand...
Click to collapse
i have the same problem, do you know where can we find the complete 5 files (pit pda bl csc phone) for flashing with odin?
its the only thing i haven't already tried.

I manage to fix the issue with storage partition, i used a pit file and the one file firmware in csc button, that made the hole data partition rewriten again so the phone is able to boot properly.
Hope you gays this may help.
Happy new year!!

heratis said:
I manage to fix the issue with storage partition, i used a pit file and the one file firmware in csc button, that made the hole data partition rewriten again so the phone is able to boot properly.
Hope you gays this may help.
Happy new year!!
Click to expand...
Click to collapse
What makes you assume we're all gay?

Sorry pal, i better watch my grammar, i ment guys.

[Help] MLA-L03 No OS, no Backup, Black Screen need help.

I've probably messed this thing up just about as badly as I can.
Here's what I can tell you:
Update: I just figured out that you are supposed to put dload onto a separate sd card, So i'll be trying that when the phone comes out of it's coma XD anything else you can suggest is very welcome.
- The phone currently isn't turning on after messing around in twrp(tried to restart into bootloader)
- While trying to get it working, it is now showing up as CAN-L11(likely from trying some backups of others)
- I was unable to use ANY roms I tried. full update files didn't work. always error 7
- It seems in twrp that I'd often get this error: mountencrypt failed to mount /data, despite wiping /data many times
- I've tried using iso files extracted from some update.app, and using that to get system and data on there, as well as recovery too
- I was switching between twrp and default recovery to transfer files and then use dload to try to recover the system, never let me do it though. got to 5% then told me something like: "Getting package info failed". it would do this in the download and recover mode as well when I would hook up to the internet and it would also give me that error.
You are free to ask me any questions about the device.
I think I just need to drain the battery then I should be able to at least get something out of it, but until then, if anyone has any recommendations after it's functional again let me know. Any help is appreciated.

TheProgrammerEX said:
I've probably messed this thing up just about as badly as I can.
Here's what I can tell you:
- The phone currently isn't turning on after messing around in twrp(tried to restart into bootloader)
Click to expand...
Click to collapse
It isn't even charging?
- While trying to get it working, it is now showing up as CAN-L11(likely from trying some backups of others)
Click to expand...
Click to collapse
Yeah, that's why. The model name can be changed in build.prop, but you're still using a CAN-L11 ROM though.
- I was unable to use ANY roms I tried. full update files didn't work. always error 7
Click to expand...
Click to collapse
You haven't flashed the TWRP mentioned in the first post of their thread, hence you've got that error which is basically telling you that you're trying to flash the ROM on an unsupported device (the phone's codename / model is mentioned in TWRP and ROM checks for it), but actually it's working on all models.
- It seems in twrp that I'd often get this error: mountencrypt failed to mount /data, despite wiping /data many times
Click to expand...
Click to collapse
That occurs because TWRP doesn't support decryption. You have to format data, not wipe. You can format it from TWRP > Wipe > Format data.
- I've tried using iso files extracted from some update.app, and using that to get system and data on there, as well as recovery too
Click to expand...
Click to collapse
What happened after you've tried that?
- I was switching between twrp and default recovery to transfer files and then use dload to try to recover the system, never let me do it though. got to 5% then told me something like: "Getting package info failed". it would do this in the download and recover mode as well when I would hook up to the internet and it would also give me that error.
Click to expand...
Click to collapse
Try to unplug the cable from PC. Also, note that I've read in past somewhere that the firmwares from Firmware Finder has to be approved by Huawei and if it isn't, then the stock recovery will fail to flash it. Other Huawei phones has modified / patched stock recovery which allows to flash unapproved firmwares though.
You are free to ask me any questions about the device.
Click to expand...
Click to collapse
How do you guys end up like this? xD
Update: I just figured out that you are supposed to put dload onto a separate sd card, So i'll be trying that when the phone comes out of it's coma XD anything else you can suggest is very welcome.
Click to expand...
Click to collapse
Hah, here's the answer to the above question: not reading xD. Try to slap the phone to wake it from the coma ahahahah xD. When did it get into coma though?

How to backup the AT&T stock rom?

I'm going over this guide https://forum.xda-developers.com/lg-v35/development/bootloader-unlock-root-instruction-t4052145 and at some point it reads:
There are a couple warnings. The first is that AT&T does not release flashable roms. There is no going back unless of course you take the time to make a backup of the rom itself.
Click to expand...
Click to collapse
I'm new to LG Android and don't know exactly what is considered a twrp-less rom backup here. Is it the "partition extraction" the same guide goes on to describe? If not, can someone please tell me how to do it or point me in the right direction?

It is pretty straightforward:
1. Install and configure QPST and QFIL as per the guide on your PC.
2. Plugin your phone and enter 9008 as per guide.
3. Dump your partitions using QFIL (you will need about 60 GB of free space)

Thanks vlad48!
vlad48 said:
3. Dump your partitions using QFIL (you will need about 60 GB of free space)
Click to expand...
Click to collapse
That's a lot of space! To backup the rom do I really need to back up all of the partitions? Seems like that is including userdata or otherwise more than just the rom :S

rpgdev said:
Thanks vlad48!
That's a lot of space! To backup the rom do I really need to back up all of the partitions? Seems like that is including userdata or otherwise more than just the rom :S
Click to expand...
Click to collapse
hi!
did you ever complete your full partition backup?
Thanks!

cloud1250000 said:
hi!
did you ever complete your full partition backup?
Thanks!
Click to expand...
Click to collapse
Nah, I just went ahead and got rid of the AT&T rom. Haven't needed it and don't miss it.

A word of caution for others, even if you do backup with QFIL, it is hit and miss and flashing partitions from QFil backup can give you errors. Sometimes changing .bin extension of the partition data to .img can help but in my experience most times even after successful flash you may not be able to boot successfully from either slot. I couldn't recover to AT&T Android 10 from my backup and had to flash Korean Android 10 because once you go up to Android 10, you can't downgrade to Pie or Oreo.

Android# said:
because once you go up to Android 10, you can't downgrade to Pie or Oreo.
Click to expand...
Click to collapse
Sheeeeeeeeeit. I didn't know that thank you for posting that. Guess Android 10 isn't so good then? What was your experience? Feel free to pm.

internal SDCARD Allocation Error ?

Hi,
Problem: After Update & Root Errors
Now it shows internal SD memory says now it only has 5gb instead of 32 (28~GB)
it had had normal size before.
WTF...?
I maybe messed with some wrong file before on flash, but I really wonder, how to solve this problem..
Damn every phone has its own difficulties, rooted so many phones, but this the process is always somehow unique...
And where is the proper TWRP file for the A20e latest android 9 version?
DBT-A202FXXU3ASL4-20200120200600
Please someone link it for me. The one I found doesn't seem to work..

lol, you need to know it was because of the wrong VBmeta file.
I wondern why the manuals can't be clearer sometimes.
Just like the TWRP tutorial - somehow you need to have the right vbmeta in Hand, but nothing more about this and where to get the proper one.
Whatever, it helped to relock Bootloader and to make a clean install with CSC (not HOME_CSC), then the files and sizes got right again.
Also re-partition helps in this case.
Anyway it's really frustrating to root these days, but at least we still can do this.
Without root many things would suck alot... i would not buy a phone without the possibility of it.

hmmm I wonder if this is why I'm experiencing problems with my recently rooted a20e and no choice for internal storage.

||||| said:
lol, you need to know it was because of the wrong VBmeta file.
I wondern why the manuals can't be clearer sometimes.
Just like the TWRP tutorial - somehow you need to have the right vbmeta in Hand, but nothing more about this and where to get the proper one.
Whatever, it helped to relock Bootloader and to make a clean install with CSC (not HOME_CSC), then the files and sizes got right again.
Also re-partition helps in this case.
Anyway it's really frustrating to root these days, but at least we still can do this.
Without root many things would suck alot... i would not buy a phone without the possibility of it.
Click to expand...
Click to collapse
@moogle
The vbmeta.img is included in the TWRP.tar
https://forum.xda-developers.com/ga...overy-twrp-3-4-0-0-galaxy-a20e-a202f-t4141767
This is the Android 10 version
You need to upgrade first

physwizz said:
@moogle
The vbmeta.img is included in the TWRP.tar
https://forum.xda-developers.com/ga...overy-twrp-3-4-0-0-galaxy-a20e-a202f-t4141767
This is the Android 10 version
You need to upgrade first
Click to expand...
Click to collapse
This is the tutorial I was following, I unlocked, flashed TWRP and rooted successfully but SD card storage seems to be operating strangely.
What do you recommend to diagnose / fix?

moogle said:
This is the tutorial I was following, I unlocked, flashed TWRP and rooted successfully but SD card storage seems to be operating strangely.
What do you recommend to diagnose / fix?
Click to expand...
Click to collapse
Stock or GSI

physwizz said:
Stock or GSI
Click to expand...
Click to collapse
I cannot seem to get a GSI installed successfully, many of the tutorials say to use an AB partition GSI but the treble partition check says the SM-A202F/DS isn't an AB partition device.
It says:
"Your device does not support Seamless System Upgrades and is detected to have an A-only system partition."

moogle said:
I cannot seem to get a GSI installed successfully, many of the tutorials say to use an AB partition GSI but the treble partition check says the SM-A202F/DS isn't an AB partition device.
It says:
"Your device does not support Seamless System Upgrades and is detected to have an A-only system partition."
Click to expand...
Click to collapse
A205 is fake ab ( a plus SAR)
Send pm to a202 users

did you mean to write a202?

moogle said:
did you mean to write a202?
Click to expand...
Click to collapse
ask @Xyn XDotnest or @Wire1122
Send a personal message
I don't have a202
I have a205yn

||||| said:
lol, you need to know it was because of the wrong VBmeta file.
I wondern why the manuals can't be clearer sometimes.
Just like the TWRP tutorial - somehow you need to have the right vbmeta in Hand, but nothing more about this and where to get the proper one.
Whatever, it helped to relock Bootloader and to make a clean install with CSC (not HOME_CSC), then the files and sizes got right again.
Also re-partition helps in this case.
Anyway it's really frustrating to root these days, but at least we still can do this.
Without root many things would suck alot... i would not buy a phone without the possibility of it.
Click to expand...
Click to collapse
Which model of the a20e did you have?