Related
Hello People,
Firstly I would like to apologize if this is a duplicate post, Googling reveals tons of different documents which actually has confused me and as I have tried many, I don't even know now what have I screwed up.
Phone - U8800H
OS - Linux
I tried to update my phone and it got messed up. It simply won't boot but go in an infinite loop or restarting every 3 seconds (once the HUAWEI logo is displayed).
By pressing both Vol buttons and starting the phone I can go into bootloader mode (pink screen) and the phone drives get mounted. However trying to go to recover mode by pressing the Vol UP key during start up simply again keeps restarting the phone.
I have tried various solutions which include re-downloading the images folder files again, replacing the recover.img from clockwork, formatting that partition and retrying, almost everything.
The phone simply keeps restarting. Replacing or removing any of the file in the images folder gives me a blue screen during going to bootloader mode.
As I cant get to recover mode I don't know what to do.
The warranty of the phone is finished as it was only of three months. I was told by the company I purchased it from to be a "power problem" but I think its a software problem as I messed it up myself.
If anyone has faced such situation before please help.
Thanks.
find original rom and reinstall it.
Otherwise what rom where you on?
arkudos said:
find original rom and reinstall it.
Otherwise what rom where you on?
Click to expand...
Click to collapse
U cant install rom without clockworkmod?
sent from ideos x5
eddydc1 said:
U cant install rom without clockworkmod?
sent from ideos x5
Click to expand...
Click to collapse
_original_ means what the phone came with
Rom is the.......
He needs to go back to original phone, or to find probably the old boot.img he had, that is why I asked which rom he was on....
arkudos said:
_original_ means what the phone came with
Rom is the.......
He needs to go back to original phone, or to find probably the old boot.img he had, that is why I asked which rom he was on....
Click to expand...
Click to collapse
Okk
sent from ideos x5
The original ROM was U8800HV100R001AREC00B135SP01 CUSTC213D001 (Kuwait VIVA). I have downloaded it as well.
However as suggested it asks me to create a dload folder in a formatted SD card with the zipped files within it, and then start the phone in 'recovery mode'. However the phone doesn't start in that mode with the same restarting issue.
One person suggested to create a 'dload' folder in the SD card with no contents in it and then start the phone in 'bootloader' mode and the phone will auto revert to its default firmware. I did as suggested but it didn't work either.
I have the original boot.img that came with the phone. I also downloaded a fresh boot.img (along with the other three files that come in the images folder) but still the same result of restarting during trying to start in 'recover mode'.
It was working fine till I messed it up trying to upgrade it to 2.3 to change the patched wpa_supplicant file to connect to Ad-Hoc networks.
I think I need to change the files required for 'recover mode' to default ones, but I don't know where they reside. Any tutorial in this direction would be great.
Thanks.
My guess is that some of the partitions got messed up somehow, some different filesystems (ext4 over ext3) in 2.3 stock fw.
Have you tried copying update.app to dload-folder of sdcard then booted phone with both vol-down and vol-up pressed (bootloader mode). That should in theory start the update...
Sent from my u8800 using XDA App
huzefa_from_kuwait said:
The original ROM was U8800HV100R001AREC00B135SP01 CUSTC213D001 (Kuwait VIVA). I have downloaded it as well.
However as suggested it asks me to create a dload folder in a formatted SD card with the zipped files within it, and then start the phone in 'recovery mode'. However the phone doesn't start in that mode with the same restarting issue.
One person suggested to create a 'dload' folder in the SD card with no contents in it and then start the phone in 'bootloader' mode and the phone will auto revert to its default firmware. I did as suggested but it didn't work either.
I have the original boot.img that came with the phone. I also downloaded a fresh boot.img (along with the other three files that come in the images folder) but still the same result of restarting during trying to start in 'recover mode'.
It was working fine till I messed it up trying to upgrade it to 2.3 to change the patched wpa_supplicant file to connect to Ad-Hoc networks.
I think I need to change the files required for 'recover mode' to default ones, but I don't know where they reside. Any tutorial in this direction would be great.
Thanks.
Click to expand...
Click to collapse
Ok then.... because I'm lost... which rom was on!
2.2.1?
or 2.3.?
these are the files needed FIRST....
---------- Post added at 05:31 PM ---------- Previous post was at 05:16 PM ----------
Ok IF you were on 2.2.... on sdcard make \dload folder with update 2.2 original rom!!!!
Vol+ Vol- Power on...pink screen and it should do the rest!!!
Recovery after you reinstall 2.2!
Now IF you managed to put 2.3... then put 2.3 update in sdcard \dload and again it should do the rest.
If you are trying to come back to 2.2 or miui oxygen cm7 from the beta.... first put the 2.3 beta back on via the sdcard.
I have put the original ROM in 'dload' folder and as suggested I shall have started the phone in 'bootloader' mode now. There is no movement on the screen so I don't know even if its doing something.
How much should I wait or shall I be notified if the update is done ?
Thanks.
huzefa_from_kuwait said:
I have put the original ROM in 'dload' folder and as suggested I shall have started the phone in 'bootloader' mode now. There is no movement on the screen so I don't know even if its doing something.
How much should I wait or shall I be notified if the update is done ?
Thanks.
Click to expand...
Click to collapse
Is your folder structure like this
/sd
/sd/dload
/sd/dload/update.app
If it is, then boot to bootloader. you should see it is doing stuff.
julle131 said:
Is your folder structure like this
/sd
/sd/dload
/sd/dload/update.app
If it is, then boot to bootloader. you should see it is doing stuff.
Click to expand...
Click to collapse
I have double checked it again, the structure is 'dload' folder in the root of the memory card and the update.app file in it, still however I don't see any movement in the 'bootloader' mode, just the "pink" screen continuously lit.
What am I doing wrong ?
Thanks.
huzefa_from_kuwait said:
I have double checked it again, the structure is 'dload' folder in the root of the memory card and the update.app file in it, still however I don't see any movement in the 'bootloader' mode, just the "pink" screen continuously lit.
What am I doing wrong ?
Thanks.
Click to expand...
Click to collapse
Pink screens means it didn't work. Your phone isn't mounting the sd-card right in bootloader mode. You could try to put the dload-folder on internal sd-card, should be possible since you're on linux. Think you just need to mount the right partition when connecting your phone via usb when in pinkscreen. I don't recall exactly which partition as I'm using Windows and haven't tried this, but you should be able to find some more info around here by searching a bit...
U8800
Hello XDA-Forum!
Same problem here with my u8800
I have original recovery.img but i fd' other files by overwriting them.. (yes i know...)
Now my phone doesen't start flashing and i cant do anything. I was using almost latest version of oxygen mod.
Do i need original files to flash my phone back to stock in image/... floder? And if i need, can i dig version form recovery.img? or might this is problem with partitions? I think oxygen is known by partition problems.
HFZenon said:
Pink screens means it didn't work. Your phone isn't mounting the sd-card right in bootloader mode. You could try to put the dload-folder on internal sd-card, should be possible since you're on linux. Think you just need to mount the right partition when connecting your phone via usb when in pinkscreen. I don't recall exactly which partition as I'm using Windows and haven't tried this, but you should be able to find some more info around here by searching a bit...
Click to expand...
Click to collapse
I have tried as you suggested, There were 5 partitions on the phone 2 of which were smaller than 200MB and therefore could not save the update file which is larger in size. I have tried over the remaining three partitions but in vain, they all end up with the same pink screen.
However you might be correct that my phone is not mounting the SD card as I can't see the SD card in the list of mounted drives in the computer.
To put/move files on SD card I have to use my another phone
I will get another SD card and try. In the meanwhile if there is anything else I could try, do advice me.
Thanks.
Nahkamies said:
Hello XDA-Forum!
Same problem here with my u8800
I have original recovery.img but i fd' other files by overwriting them.. (yes i know...)
Now my phone doesen't start flashing and i cant do anything. I was using almost latest version of oxygen mod.
Do i need original files to flash my phone back to stock in image/... floder? And if i need, can i dig version form recovery.img? or might this is problem with partitions? I think oxygen is known by partition problems.
Click to expand...
Click to collapse
Hi, and welcome to XDA!
I guess you got the same problem with sd-card not mounting properly if you can't initiate stock flashing via dload-folder-method.
If you search the forums you'll find links to download all files that's needed in the image-folder of pinkscreen-partition. Then you'll hopefully be able to boot to recovery (vol-up + power), wipe data/cache/dalvik cache and flash whatever ROM you'd like. Remember this erases all your data, hopefully you've backed up whatever precious stuff you've got on your phone.
HFZenon said:
Hi, and welcome to XDA!
If you search the forums you'll find links to download all files that's needed in the image-folder of pinkscreen-partition.
Click to expand...
Click to collapse
Thank u!
I loaded Official 2.3 overseas original boot.img & recovery.img but nothing new happened. volume up+power = bootloop, if i try flash volumeup+down + power = pinkscreen. If i delete image folder comes blue. Another ideas?
Nahkamies said:
Thank u!
I loaded Official 2.3 overseas original boot.img & recovery.img but nothing new happened. volume up+power = bootloop, if i try flash volumeup+down + power = pinkscreen. If i delete image folder comes blue. Another ideas?
Click to expand...
Click to collapse
Remember that you need all files from the same version. Try this, those are from stock 2.2 if I'm not mistaken. When (if?) you get into recovery, remember to clear cache / data / dalvik cache.
HFZenon said:
Remember that you need all files from the same version. Try....
Click to expand...
Click to collapse
Bingo! I'm very grateful of your help!
Nahkamies said:
Bingo! I'm very grateful of your help!
Click to expand...
Click to collapse
Glad to hear you get it working as we both had the basically same problem.
For me however still it is the same issue, except that while going into the recover mode now it shuts down instead or restarting endlessly. Where as the bootloader mode simply does nothing.
Can you post the exact steps you did to get your work so I can also repeat them?
Thanks.
@huzefa_from_kuwait:
You've got the U8800H right? Then you need to find the correct image-folder for your phone, as it differs from what I uploaded which is for U8800.
sorry for asking so many questions here...
so i've just installed the stock rom back on my motorola X play
everything works! except one thing:
the Sim-card
i am 100% sure the sim card works since i have tested it already on a other phone
what could be the cause of the problem?
Flash the whole rom again
Bhishma2 said:
Flash the whole rom again
Click to expand...
Click to collapse
nope that didn't work
dempixels said:
nope that didn't work
Click to expand...
Click to collapse
Take out sim.
Code:
fastboot erase modemst1
Fastboot erase modemst2
Fastboot erase cache
Insert sim.
bablu048 said:
Take out sim.
Code:
fastboot erase modemst1
Fastboot erase modemst2
Fastboot erase cache
Insert sim.
Click to expand...
Click to collapse
sorry that didn't work too
dempixels said:
sorry that didn't work too
Click to expand...
Click to collapse
Have you tried another sim card ?
bablu048 said:
Have you tried another sim card ?
Click to expand...
Click to collapse
yes, it detects the sim-card. it even asks for the pin-code to unlock the sim
but as soon I unlock the sim... nope no service did I install the wrong driver for this device?
bablu048 said:
Have you tried another sim card ?
Click to expand...
Click to collapse
some more information:
I've tried to search to mobile carriers and it successfully finds them on 4g, 3g or 2g but it won't register.
if i tap my carrier it says ''registering on Lebara'' and i get a message ''sorry we couldn't register at this time, try again later''
bablu048 said:
Have you tried another sim card ?
Click to expand...
Click to collapse
I am really getting scared that my phone will never be able to function normally again
dempixels said:
I am really getting scared that my phone will never be able to function normally again
Click to expand...
Click to collapse
first remove the sim pin-code and clear cache from recovery and see if it detects. if it doesn't work see if you have twrp backup of previous rom on which you were on, and restore the backup.
or flash any new rom and see if it detects the sim.
bablu048 said:
first remove the sim pin-code and clear cache from recovery and see if it detects. if it doesn't work see if you have twrp backup of previous rom on which you were on, and restore the backup.
or flash any new rom and see if it detects the sim.
Click to expand...
Click to collapse
well that's just it,
the sim cards are perfectly detected from A-Z
but when the phone has to register it to a carrier it fails to do so.
dempixels said:
well that's just it,
the sim cards are perfectly detected from A-Z
but when the phone has to register it to a carrier it fails to do so.
Click to expand...
Click to collapse
Same error in different rom also ??
bablu048 said:
Same error in different rom also ??
Click to expand...
Click to collapse
I don't know which rom to try,
at first I mistakenly flashed the Asian dual-sim version. but the sims didn't work at all, no detection no nothing.
later I tried the correct version from Europe, and the Sim got detected but it didn't wanted to be used. atleast the phone didn't
I've the same problem. I just flashed correctly stock version of system, but I didn't notice that it is version Dual SIM. Then I wanted to flash CM 14.1 but unfortunetly modem doesnt work. I've tried flashed once again modem of stock version and it result i could input my pin code, but in settings I see that radio is off.
EDIT: I want to add that after noticed CM 14.1 modem doesnt work, I've flashed stock one sim modem. But device still recoganize that my XT1562 is dual sim. Is there any adb/fastboot command which could fix my issue?
Kozioleczek said:
I've the same problem. I just flashed correctly stock version of system, but I didn't notice that it is version Dual SIM. Then I wanted to flash CM 14.1 but unfortunetly modem doesnt work. I've tried flashed once again modem of stock version and it result i could input my pin code, but in settings I see that radio is off.
EDIT: I want to add that after noticed CM 14.1 modem doesnt work, I've flashed stock one sim modem. But device still recoganize that my XT1562 is dual sim. Is there any adb/fastboot command which could fix my issue?
Click to expand...
Click to collapse
I've figured out that it's my IMEI number that's missing but I can't acces the ADB commands, maybe you are having a lucky day.
If you still have the original box you could find your IMEI number and fix it with this: http://forum.xda-developers.com/oneplus-one/general/steps-how-to-recover-bad-imei-t3171452
but please becareful with this solution I don't know if it's 100% compatible with android 6.0
dempixels said:
I've figured out that it's my IMEI number that's missing but I can't acces the ADB commands, maybe you are having a lucky day.
If you still have the original box you could find your IMEI number and fix it with this: http://forum.xda-developers.com/oneplus-one/general/steps-how-to-recover-bad-imei-t3171452
Click to expand...
Click to collapse
Maybe it would solve my problem. I'll try your fix in week time. I've checked up my fastboot and behind Baseband, there is nothing written.
My mobile was updated with the December version and since then I have infinite bootloops
I've reinstalled the November version with myFlash but I'm still the same. I tried with tprw but i have some errors with the /cache partition
Can anybody help me?
Thanks
what december version?
ludditefornow said:
what december version?
Click to expand...
Click to collapse
7.12.7_7.1, after that, my movile bootloop every 30 secons more or less
Now, when i turn the mobile on, it tells me that the SIM is blocked, but I tried the SIM in another mobile and it works
A/B partition are there so if device is stuck in bootloop it should boot from dormant partition.
You have to flash stock firmware.
Try flashing the persist.img from every build that exists till now. If you manage to flash one of them the issue will be fixed. I've tested it myself.
cafernan said:
My mobile was updated with the December version and since then I have infinite bootloops
I've reinstalled the November version with myFlash but I'm still the same. I tried with tprw but i have some errors with the /cache partition
Can anybody help me?
Thanks
Click to expand...
Click to collapse
Please just follow the guide here to get it fixed: https://forum.xda-developers.com/mi-a1/how-to/ota-official-fastboot-image-n2g47h-7-12-t3728929
As it includes all necessary scripts for proper flashing it is secure to use
In worst case, you can also use the appropriate included script to factory reset at the same time when flashing. If nothing else helps, that should do the trick for you
Edwin Hamal said:
Try flashing the persist.img from every build that exists till now. If you manage to flash one of them the issue will be fixed. I've tested it myself.
Click to expand...
Click to collapse
I tried flashing persist.img, and it works!!!
Now I have 2 differents problems.
When I start my mobile, the SIM Pin page shows the message SIM CARD IS LOCKED - NO SERVICE. My sim works in another mobile
When I pu my pin, I get the message "preparing sdcard - Solving errors"
Please just do a full clean flash as recommended by me earlier and your issue should be gone. At least if they are firmware or software related.
After that do a clean flash and that issue should be fixed.
Edwin Hamal said:
After that do a clean flash and that issue should be fixed.
Click to expand...
Click to collapse
Excuse me. What do you want to say with "do a clean flash"?
Follow the guide I linked for you above. You have to use the flash_all script. So please have a look and give it a try.
Edwin Hamal said:
After that do a clean flash and that issue should be fixed.
Click to expand...
Click to collapse
Dont't works
It shows the same message SIM CARD IS LOCKED - NO SERVICE
Any help?
cafernan said:
Dont't works
It shows the same message SIM CARD IS LOCKED - NO SERVICE
Any help?
Click to expand...
Click to collapse
Shooting blindly here.
Have you tried another sim in your phone.
If another sim card works then have you tried changing your sim from carrier. It's easy.
Have you also tried a factory reset?
majamee said:
Have you also tried a factory reset?
Click to expand...
Click to collapse
Yes, and I flash boot and persist too. I think that it's possible a error with any .img inside my phone, but i don't now ...
My phone show me the page with de SIM Pin. I put the correct Pin, and after that phone don't connect with the network. I can't call because it's without service.
I tried the same SIM in another phone and it works. I tried diferents sim in my phone and all of them fail
Please, someone has any idea about what I need to do
Thanks
cafernan said:
Yes, and I flash boot and persist too. I think that it's possible a error with any .img inside my phone, but i don't now ...
My phone show me the page with de SIM Pin. I put the correct Pin, and after that phone don't connect with the network. I can't call because it's without service.
I tried the same SIM in another phone and it works. I tried diferents sim in my phone and all of them fail
Please, someone has any idea about what I need to do
Thanks
Click to expand...
Click to collapse
Have you tried the script to flash the full stock rom flash_all from https://forum.xda-developers.com/mi-a1/how-to/ota-official-fastboot-image-n2g47h-7-12-t3728929 here as well? If you only flashed the persist.img until now, you should give it a try.
majamee said:
Have you tried the script to flash the full stock rom flash_all from https://forum.xda-developers.com/mi-a1/how-to/ota-official-fastboot-image-n2g47h-7-12-t3728929 here as well? If you only flashed the persist.img until now, you should give it a try.
Click to expand...
Click to collapse
Thanks majamee but I flash all with MiFlash and it doesn't work, this isn't the problema
Finally I checked my IMEI and I discovered that it's 0.
Someone knows how can I recovery the phone's IMEI
Thanks
cafernan said:
Thanks majamee but I flash all with MiFlash and it doesn't work, this isn't the problema
Finally I checked my IMEI and I discovered that it's 0.
Someone knows how can I recovery the phone's IMEI
Thanks
Click to expand...
Click to collapse
http://lmgtfy.com/?q=qualcomm+recover+imei
I just bought a used sim unlocked HTC 10 Verizon off eBay yesterday, it was shipped with marshmallow firmware and I successfully managed to update it to the 7.0 nougat through htc sync manager, however after updating it to 7.0 sync manager shows that the phone is updated to the latest version and there aren't any further updates available, we all know that verizon released an 8.0 update as well for the htc 10. Also, I tried updating through OTA but whenever I press on check updates it says "Cannot connect, we had trouble checking for the system updates." Can anybody provide me with an SD card backup or anything so that I can update my phone to 8.0 officially without losing data? I just want to update it to 8.0 and nothing else, don't want to root it or anything. So far the device seems amazing.
Some information about my phone:
Model Number: HTC 6545LVW
Current Software Version: 2.41.605.36
whizinc said:
I just bought a used sim unlocked HTC 10 Verizon off eBay yesterday, it was shipped with marshmallow firmware and I successfully managed to update it to the 7.0 nougat through htc sync manager, however after updating it to 7.0 sync manager shows that the phone is updated to the latest version and there aren't any further updates available, we all know that verizon released an 8.0 update as well for the htc 10. Also, I tried updating through OTA but whenever I press on check updates it says "Cannot connect, we had trouble checking for the system updates." Can anybody provide me with an SD card backup or anything so that I can update my phone to 8.0 officially without losing data? I just want to update it to 8.0 and nothing else, don't want to root it or anything. So far the device seems amazing.
Some information about my phone:
Model Number: HTC 6545LVW
Current Software Version: 2.41.605.36
Click to expand...
Click to collapse
https://forum.xda-developers.com/verizon-htc-10/how-to/unlocked-htc-10-verizon-version-wont-t3843549
This will wipe your data though, unfortunately.
Tarima said:
https://forum.xda-developers.com/verizon-htc-10/how-to/unlocked-htc-10-verizon-version-wont-t3843549
This will wipe your data though, unfortunately.
Click to expand...
Click to collapse
Thanks a lot!! Just want to know one thing how can i flash it? through SD card backup or is the RUU which is an .exe file?
whizinc said:
Thanks a lot!! Just want to know one thing how can i flash it? through SD card backup or is the RUU which is an .exe file?
Click to expand...
Click to collapse
It's a zip file so you'll need to rename to 2PS6IMG.zip, put it on the root of your SD card and boot to download mode.
Tarima said:
It's a zip file so you'll need to rename to 2PS6IMG.zip, put it on the root of your SD card and boot to download mode.
Click to expand...
Click to collapse
im fairly new to HTC, this might sound like a noob question: Will it start updating itself as soon as I boot it in the download mode? P.S file being in the SD card on root
whizinc said:
im fairly new to HTC, this might sound like a noob question: Will it start updating itself as soon as I boot it in the download mode? P.S file being in the SD card on root
Click to expand...
Click to collapse
No but it will prompt you to flash it, as long as you named it properly.
Tarima said:
No but it will prompt you to flash it, as long as you named it properly.
Click to expand...
Click to collapse
i dont have an SD card at the moment, can i use internal memory?
whizinc said:
i dont have an SD card at the moment, can i use internal memory?
Click to expand...
Click to collapse
You can't. I think you can flash it using fastboot commands? I don't know how though. I saw @yldlj mention it, maybe he can help?
whizinc said:
i dont have an SD card at the moment, can i use internal memory?
Click to expand...
Click to collapse
You need to download htc_fastboot from HTC dev. I'm not sure the commands tho but im sure if you google it it will come up. Htc_fastboot allows flashing bigger files. Or just go to the shops today and get an SD card which is the easy way.
yldlj said:
You need to download htc_fastboot from HTC dev. I'm not sure the commands tho but im sure if you google it it will come up. Htc_fastboot allows flashing bigger files. Or just go to the shops today and get an SD card which is the easy way.
Click to expand...
Click to collapse
tried googling it, seems like a complex method. I'll get an SD card today to make things easier. Thanks a lot
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?