Develop Bugs

App2SD...????????????????

Sorry Guys if am asking this Question here....i have searched full XDA Forum for this ....got ans too but still have confusions.....
1st of all wanna know what is App2SD....Hope its the application to transfer all your application installation to SD card....
2nd i have tried several methods listed here in forum...but no result.....SD card is having full space and phone memory is just 50 MB left.....
Tried Defrost application and selected all installation to external media....(Hopefully this is the correct method...but didn't figured out for me yet....)
Tried to give EXT3 partition to SD of 512 MB...but here i don't know the full procedure and really confused how to go about.....
Tried for Froyo ROM's as i believe its having inbuilt capability to install all app to SD card....No result yet....
I requet all my frnds here to just giude me to the right path...i am sure i will do the rest ..... really confused with a lot of explanation given in forum....
One more small help needed...i need to have HTC Default dialer application as some of the ROM has removed it with some other application....
Waiting for reply....

pranavd1980 said:
Sorry Guys if am asking this Question here....i have searched full XDA Forum for this ....got ans too but still have confusions.....
1st of all wanna know what is App2SD....Hope its the application to transfer all your application installation to SD card....
2nd i have tried several methods listed here in forum...but no result.....SD card is having full space and phone memory is just 50 MB left.....
Tried Defrost application and selected all installation to external media....(Hopefully this is the correct method...but didn't figured out for me yet....)
Tried to give EXT3 partition to SD of 512 MB...but here i don't know the full procedure and really confused how to go about.....
Tried for Froyo ROM's as i believe its having inbuilt capability to install all app to SD card....No result yet....
I requet all my frnds here to just giude me to the right path...i am sure i will do the rest ..... really confused with a lot of explanation given in forum....
One more small help needed...i need to have HTC Default dialer application as some of the ROM has removed it with some other application....
Waiting for reply....
Click to expand...
Click to collapse
Someone please guide me........please

Instead of bumping your thread have you tried looking at the thread of the chef released rom for your phone as you might realise that others have same issue with the rom or not. I did a quick search of forums and i managed to find the answers within seconds.
We cant support your rom as we dont know what you are using / version and questions regarding that rom need to be posted in the correct forum thread

A|ex said:
Instead of bumping your thread have you tried looking at the thread of the chef released rom for your phone as you might realise that others have same issue with the rom or not. I did a quick search of forums and i managed to find the answers within seconds.
We cant support your rom as we dont know what you are using / version and questions regarding that rom need to be posted in the correct forum thread
Click to expand...
Click to collapse
Sorry M8...But i am really confused with several ROM's and Methods listed here...
I will follow your instructions in future....Sorry Again....

Different roms work differently and you really need to try one, then ask about it in the chefs rom thread and if you dont like try another. Swapping roms and trying to use the same instructions on each may not work so you are only confusing yourself.

A|ex said:
Different roms work differently and you really need to try one, then ask about it in the chefs rom thread and if you dont like try another. Swapping roms and trying to use the same instructions on each may not work so you are only confusing yourself.
Click to expand...
Click to collapse
Thanks Again.....

A2SD is indeed moving apps to the external memory. A lot of custom roms have it. It requires an EXT partition on your memorycard, an easy way to do that is to get rom manager from market
Sent from my HTC Desire using XDA App

Thread moved to Q&A.

judging by your post, you have already rooted your phone
here's an example how to do it with Official Froyo HTC Sense ROM v1.0c, which has built in old A2SD. I think it should work
- backup apps and system data with Titanium Backup Donate
- copy sd card content to pc in disk drive mode (by doing this, you will also copy your backups)
- download rom, radio and put them in root folder of your sd card
- you need to have some sort of recovery (whether it's update.zip in root, or permanent recovery - it's your choice)
- say a little prayer
- enter hboot -> recovery
- wipe all alvailable options (it depends on your current settings): data, cache, davlik cache, ext
- flash radio, it will ask for you to reboot from recovery, do it, it will restart few times, don't interrupt process of instalation.
- flash rom
-after you finish it, don't reboot, instead partition sd card using standard options: swap 0, ext2 512, fat32 rest, sd: ext2 to ext3 (this will format and partition your sd card, you will loose it's content
- reboot your phone, it will last longer than usual
- copy your sd card content from pc back to sd
- install titanium backup donate and restore system data and apps, it should force apps you previously had installed to sd
- reboot phone to finish restore
- install quick system info and check if your A2SD storage is partialy filled with data
-you should have your current apps and settings with A2SD enabled

Finally did it today with ROM manager huh......
Thanking all for support...
Sent from my HTC Desire using XDA App

[Q] Rom guide / SD partition help

Hi all. I'm still running cyanogenmod 7 RC1 on my Desire and decided it's time for the real thing as it's becoming more and more unstable.
1. I guess I'll use ROM Manager to download and install - I assume this will completely wipe the device. Is there a way to upgrade from RC1 to final release?
2. I've never been able to download large apps. I think it's because my SD card isn't partitioned. I cannot find out where to do that, and WHEN to do this in the process. - Any advice would be really good.
Sorry for the numpty questions! Keep up the good work everyone!
Jonny

Hi,
i dont use rom manager for that (i used to download whit the PC and put in the SD and later wipe manually in the recovery and flash the new rom, but if you like to do in the rom manager i think that you also can do)
2º whit the ROM manager you can do a ext 2/3 partition of 512mb whit no swap, but it will formatt all your SD so you need to save your data in the PC, in the other hand i prefer to use Gparted (you need a Cd and download the iso) its very usefull and you can make 1024mb ext4 whit no swap
I hope this will help you
sorry about my english ^^

I cannot find out where to do that ????
There are STICKY COMPLETE GUIDES - Just read them

use MiniTool Patrition Wizard easier thing

noonamer said:
use MiniTool Patrition Wizard easier thing
Click to expand...
Click to collapse
This is a bit of a joke. You resurrect a 7 month old thread to give bad advice IMHO (See My signature) which I notice you were thanked by evgen-baton for. I remembered seeing that user thank you in another post I quoted earlier.
I thought this was quite suspicious so I looked and sure enough, all of your thanks are from this person, today. His account has been following you around all day, thanking your posts.
Is evgen-baton your alter ego? If not, you have a stalker.

Please use the Q&A Forum for questions &
Read the Forum Rules Ref Posting
Moving to Q&A

[Q] Time for Warranty claim

Unfortunately today on my display appeared a yellow vertical line from the battery icon up to the very top. This has to be a dead screen.
Since I have bought the device my GPS does not respond at all no-mater what I do...
Therefore I decided it is time to return it to ACER for a warranty repair. Of course I have unlocked my device and installed every possible tweak that exist here in the dev forum. So I want to ask if there is a way to return the device totally stock as it was out of the box or if the unlocking and rooting does void the warranty?
Thank you
HOW TO GUIDE:
1. USB Driver Acer A100 http://global-download.acer.com/GDFiles/Driver/USB/USB_Acer_1.000_A32H_A.zip?acerid=634486286202185014&Step1=Tablet&Step2=ICONIA%20TAB&Step3=A100&OS=a08&LC=en&BC=Acer&SC=PA_6
2. Unlock mode + Recovery required (search for this in dev Forum)
3. Download Official ICS (also in dev forum - use the 300MB version, for me the 250MB didn't work)
4. Copy the file to the Integrated memory of your A100
5. Enter recovery(HOLD power & Vol+ > after vibrate release Power and wait) and install the update.zip by scrolling to it (if you are not sure what to do just read or watch youtube on "how to navigate in recovery")
6.Wait until extracted and then reboot system
7. Wait until everything is brought back to stock

I really need some help because I have to return it soon...I just want to wipe it clean as it came from the factory, without anything on it.
Please help me

SlavPala4a said:
I really need some help because I have to return it soon...I just want to wipe it clean as it came from the factory, without anything on it.
Please help me
Click to expand...
Click to collapse
Supposedly the stock ics official update.zip will relock it and put back to Acer factory status.
Tapatalked from my Galaxy S II.

Could you be a little bit more specific? I mean if you do have a couple of minutes to write a guide for me, I could than structure it, add tags and afterwards it could help a lot of people in my situation...
I would be very pleased to get help from you!

nandroid in the beginning!
I want to add that after I updated to the official ics, as by many guides, I made a nandroid backup. So it was in the very beginning before I began optimizing! Should I just restore this backup?

SlavPala4a said:
I want to add that after I updated to the official ics, as by many guides, I made a nandroid backup. So it was in the very beginning before I began optimizing! Should I just restore this backup?
Click to expand...
Click to collapse
You can but you'll still have an unlocked bootloader and custom recovery. I'll try to find some time but right now I'm short and 13% battery lol
Tapatalked from my Galaxy S II.

SlavPala4a said:
Unfortunately today on my display appeared a yellow vertical line from the battery icon up to the very top. This has to be a dead screen.
Since I have bought the device my GPS does not respond at all no-mater what I do...
Therefore I decided it is time to return it to ACER for a warranty repair. Of course I have unlocked my device and installed every possible tweak that exist here in the dev forum. So I want to ask if there is a way to return the device totally stock as it was out of the box or if the unlocking and rooting does void the warranty?
Thank you
Click to expand...
Click to collapse
I think you can use ad to wipe the recovery and lock the bootloader-
Sent from my A100 using XDA

I truly thank you about trying to help me and giving me suggestions but what is "ad". I am as much of a "hacker" as I could follow the guides in this forum. I am not familiar with the basics and all the hard work behind every new ROM, Kernel, tweak etc... Therefore I really need some kind of a guide or few steps.
For example: if I download the official ics from the dev forum > run the recovery > wipe clean(as by the books) > install the official .zip would that be a true factory reset - locked, no root , no "NASA" stuff
thank you

SlavPala4a said:
I truly thank you about trying to help me and giving me suggestions but what is "ad". I am as much of a "hacker" as I could follow the guides in this forum. I am not familiar with the basics and all the hard work behind every new ROM, Kernel, tweak etc... Therefore I really need some kind of a guide or few steps.
For example: if I download the official ics from the dev forum > run the recovery > wipe clean(as by the books) > install the official .zip would that be a true factory reset - locked, no root , no "NASA" stuff
thank you
Click to expand...
Click to collapse
Sorry, XD. That was spell check in ice cream sandwich. Meant adb.
Sent from my A100 using XDA

Put the update.zip on your SD, hold volume down and power, it restores to stock ics.
The stock official update.zip is around the forum someplace. Maybe in the dev forum.
Tapatalked from my Galaxy S II.

For example: if I download the official ics from the dev forum >copy it to the external sd> run the recovery > wipe clean(as by the books) > install the official .zip would that be a true factory reset?
P.S. I just do NOT want to brick my device, better ask first

Another question/problem: I went to recovery and prepared to run the >>>System Nullify: Nullifies /cache /data /system. THIS DELETES INTERNAL SD!<<<
When I choose to use a zip from SD card it opens the devices integrated memory, BUT when I use a zip from Internal SD it opens the micro SD card. So does that mean it will erase everything from my INTERNAL SD = micro SD(external), dew to recovery internal sd is the external sd....very confusing!

So what happend, I ran the script than I applied the update.zip(from external SD, extracted successfully) from here http://forum.xda-developers.com/showthread.php?t=1307046 FULL PACKAGE
and now I am stuck at ACER logo with bootloader still UNLOCKED!
What are my options?
P.S. I have tried the http://support.acer.com/acerpanam/tablets/2011/Acer/ICONIATab/ICONIATabA100/ICONIATabA100faq9.shtml FACTORY RESET but as soon as it started to "Erasing Userdata..." , reboots and I am again stuck at ACER UNLOCKED MODE logo...

I am now with wiped clean FlexR but I do not know how to install the official ICS?! What should I do?

SlavPala4a said:
Another question/problem: I went to recovery and prepared to run the >>>System Nullify: Nullifies /cache /data /system. THIS DELETES INTERNAL SD!<<<
When I choose to use a zip from SD card it opens the devices integrated memory, BUT when I use a zip from Internal SD it opens the micro SD card. So does that mean it will erase everything from my INTERNAL SD = micro SD(external), dew to recovery internal sd is the external sd....very confusing!
Click to expand...
Click to collapse
My nullifier only does internal no matter what's mounted. Its hard coded to do /data which contains /data/media which is internal. It does not do sdc or external or any other partitions besides /cache /data /system. So basically no, it couldn't unless your recovery mounts external to one of those mount points, which none do unless its been changed.
Tldnr doesn't do external no matter what.
Tapatalked from my Galaxy S II.

Phone no longer has anything in 'Internal Storage', can't download files

A while ago my SD card apparently stopped working and my phone asked me to format it to be used as internal storage, wiping all of the data on the card. I was pretty annoyed but after that I had no problems. Recently I removed the SD card as I was going to root my phone with the All in One Toolkit and it seemed to work until I opened SuperSU and was told I had no SuperSU binaries. (I'm not sure if this is relevant but I thought I would mention it just in case).
I then went onto Google Chrome and tried to save a random image and was prompted to overwrite *completely random image name* in documents. No matter which option I hit (overwrite or create new file) I am given the notification it has downloaded but if I tap it then I'm just taken to a black screen with a triangle and an exclamation mark. When I go into the file manager and go to internal storage there is absolutely nothing in there.
I thought this might have something to do with the SD card so I put it back in but was again prompted to format it, so this time I did it as removable storage and it hasn't made a difference. Any ideas?
Android Version 6.0
Software Number 6.13.206.5
If you need any more info let me know.
Thanks!

dezzybird said:
A while ago my SD card apparently stopped working and my phone asked me to format it to be used as internal storage, wiping all of the data on the card. I was pretty annoyed but after that I had no problems. Recently I removed the SD card as I was going to root my phone with the All in One Toolkit and it seemed to work until I opened SuperSU and was told I had no SuperSU binaries. (I'm not sure if this is relevant but I thought I would mention it just in case).
I then went onto Google Chrome and tried to save a random image and was prompted to overwrite *completely random image name* in documents. No matter which option I hit (overwrite or create new file) I am given the notification it has downloaded but if I tap it then I'm just taken to a black screen with a triangle and an exclamation mark. When I go into the file manager and go to internal storage there is absolutely nothing in there.
I thought this might have something to do with the SD card so I put it back in but was again prompted to format it, so this time I did it as removable storage and it hasn't made a difference. Any ideas?
Android Version 6.0
Software Number 6.13.206.5
If you need any more info let me know.
Thanks!
Click to expand...
Click to collapse
Did you update the binaries?

xunholyx said:
Did you update the binaries?
Click to expand...
Click to collapse
I was never given an option, it said they couldn't be installed by the app. I was going to try the fix where you install them directly by saving a zip to your phone's internal storage and then installing it but then I noticed the problem with my internal storage.

dezzybird said:
A while ago my SD card apparently stopped working and my phone asked me to format it to be used as internal storage, wiping all of the data on the card. I was pretty annoyed but after that I had no problems. Recently I removed the SD card as I was going to root my phone
Click to expand...
Click to collapse
When you chose to make the SD a part of internal storage (known as the new "adoptable storage" option in Marshmallow), you merged it (with the phone's internal storage) as part of the data partition. Then you yanked out a part of that partition, by removing the SD (and why you did that in order to root, I don't know).
I'm not too familiar with what happens (or is supposed to happen, anyway) when you choose adoptable storage, then remove the SD. But I think its safe to say, that resulting storage issues is not a surprise.
dezzybird said:
I was going to root my phone with the All in One Toolkit and it seemed to work until I opened SuperSU and was told I had no SuperSU binaries. (I'm not sure if this is relevant but I thought I would mention it just in case).
Click to expand...
Click to collapse
The toolkit hasn't been updated in over a year, and causes many issues for that reason. It hasn't been updated for Marshmallow (Android 6) and therefore can't root MM. Toolkit also contains an obsolete version of TWRP which will also cause some issues.
Good rule of thumb: whenever rooting an Android device, you should be sure to use updated methods; and verify the method works with your Android version.
Since you have TWRP installed, try going to the Wipe section in TWRP. Then select the button that says "Format Data" and see if that helps your issue with writing to internal storage. Do not select to wipe any other things in the Advanced section of Wipe (another rule of thumb - if you don't know what it is don't wipe it. For instance wiping "System" will delete the OS entirely).
Of course, formatting data will cause any data to be lost. So backup accordingly (if there is anything left) before you format data.
Once you have the storage issue sorted out (hopefully the above helps), ditch the toolkit, and do the following steps manually:
1) Unlock bootloader (should already be done)
2) Flash TWRP 3.0 with fastboot
3) Flash SuperSU 2.65 in TWRP, to properly root

Aye, I couldn't find an alternative to the toolkit so I just ran with it but I guess I've learned that lesson.
I've managed to sort the issue now so I'll post what I did here for any people who may happen upon the thread in future. I'm still not sure what caused the issue in the first place; maybe it was the memory card, maybe I selected the wrong thing to wipe in TWRP, maybe it was the toolkit or maybe a bit of everything because I'm stupid.
Before I discovered the issue I was going to install the SuperSU binaries manually (since they didn't install for some reason) and install a custom ROM, so I decided to just go ahead with it. After flashing the ROM and then SuperSU.zip everything worked fine and I had a fully rooted phone running Cyanogenmod. According to the guide I was reading I had to wipe a number of things (the Dalvik Cache, System, Cache, and Data) anyway so I don't think it mattered that I had somehow erased the internal memory as it seemed to be reinstalled with the ROM. This is just a guess though, all I know for sure is it's fine now (fingers crossed).
So next time I'd just use the toolkit to help unlock the bootloader and maybe flash a recovery as that seemed to work fine, but manually flash SuperSU.zip to root yourself in case the toolkit is what broke it.
Thanks for your help!

dezzybird said:
Aye, I couldn't find an alternative to the toolkit so I just ran with it but I guess I've learned that lesson.
Click to expand...
Click to collapse
The best way to achieve bootloader unlock and root is to just do the steps manually.
You don't need a toolkit to do these things. Anyone that can follow instructions and type a few fastboot commands can do it.
All that folks need to do it manually is here. Everything in Section 1 is valid, with the exception that the TWRP version number in the command needs to (obviously) match the number you are trying to install (the example given in the guide is an older version). Some things in Section 2 and 3 are obsolete (s-off method, firmware version) but that's irrelevant in this case (and for most folks) since those things aren't necessary to unlock the bootloader, root, or flash custom ROMs.
dezzybird said:
Before I discovered the issue I was going to install the SuperSU binaries manually (since they didn't install for some reason)
Click to expand...
Click to collapse
What do you mean "for some reason"? I told you the reason. The toolkit uses an old, long obsolete version of SuperSU that existed before MM. It therefore can't root MM, and there is no reason to believe it would. New Android builds often (almost always) require new root methods, and old versions of SuperSU are usually going to cause you trouble. That is why you should always research the current root methods, when trying to root.
dezzybird said:
After flashing the ROM and then SuperSU.zip everything worked fine and I had a fully rooted phone running Cyanogenmod.
Click to expand...
Click to collapse
You don't need to root after flashing a custom ROM, they are already rooted.
You also don't need to root in order to flash a custom ROM. Unlocked bootloader and custom recovery is all you need to flash custom ROMs.
dezzybird said:
According to the guide I was reading I had to wipe a number of things (the Dalvik Cache, System, Cache, and Data) anyway so I don't think it mattered that I had somehow erased the internal memory as it seemed to be reinstalled with the ROM. This is just a guess though, all I know for sure is it's fine now (fingers crossed).
Click to expand...
Click to collapse
These are not correct assertions. Doing the default wipe in TWRP (it says most of the time, this is all that is needed, and it means it!) doesn't touch internal storage.
On a similar note, flashing a ROM doesn't touch internal storage, either. It just flashes system partition and boot.img partition.
dezzybird said:
So next time I'd just use the toolkit to help unlock the bootloader and maybe flash a recovery as that seemed to work fine, but manually flash SuperSU.zip to root yourself in case the toolkit is what broke it.
Click to expand...
Click to collapse
I'd strongly advise against using the toolkit at this point, or suggesting to others to use it. As I've already tried to explain (but you seem to be ignoring) the components of the toolkit are woefully obsolete. By the time you flash recovery manually (with fastboot) and manually flash the proper version SuperSU, there isn't much of value that the toolkit does. The bootloader unlock procedure via HTCDev.com is pretty self-explanatory (and the guide I've posted explains whatever isn't already obvious). And is justifiable to say that if you can't handle doing these things manually, you probably shouldn't have root.

I was just stating what I did to fix the issue and what I would have done instead with the same amount of knowledge I had when I started. I did search for stuff like "how to root HTC One M8 2016" and whatnot and the toolkit showed up in like the first 4 results, plus it was linked in the sidebar of the Android subreddit as the go-to option so I assumed I'd be good to go but apparently not.
After I flashed the ROM I didn't see SuperSU which I had been led to believe was what signified if the phone was rooted (if you had SuperSU > Rooted. If not > Not rooted) but apparently not. Like I mentioned, this was my first time rooting a device and I was kinda winging it as a learning experience, hence not doing things optimally (or particularly right)
Thanks for the info, that'll definitely make things easier next time!

dezzybird said:
I was just stating what I did to fix the issue and what I would have done instead with the same amount of knowledge I had when I started.
Click to expand...
Click to collapse
And what I am saying is: what you stated you "would have done instead" (or do "next time") is in fact not the correct thing to do.
Also, when you say "this is what I would have done" it read strongly like a suggestion to others what "they should do".
Just trying to prevent obvious pitfalls for both you and others in the future.
dezzybird said:
I did search for stuff like "how to root HTC One M8 2016" and whatnot and the toolkit showed up in like the first 4 results, plus it was linked in the sidebar of the Android subreddit as the go-to option so I assumed I'd be good to go but apparently not.
Click to expand...
Click to collapse
My advice would be to stick to XDA, and just use the search function here; or simply browse the forums. Reason being, randomly Googling for root methods will often yield random "root" websites with poorly organized, outdated information; which is often just stolen from XDA in the first place.
The question (and answer) of rooting this device pops up pretty frequently; as well as common pitfalls, solutions, etc. While the forums may be a bit intimidating to work through, the answers are all here; and not hard to find, once you become accustomed to how the forum is organized.
dezzybird said:
After I flashed the ROM I didn't see SuperSU which I had been led to believe was what signified if the phone was rooted (if you had SuperSU > Rooted. If not > Not rooted) but apparently not.
Click to expand...
Click to collapse
The knowledge in the following 2 paragraphs are fairly esoteric, but proboably could have been found in the CM thread or other threads:
CM has a slight oddity to it (and I'm sure its devs have there reasons) versus many other ROMs (but you may find a similar thing in other AOSP based ROMS) in that the ROM is pre-rooted, but root access is toggled "off" by default. To turn it on, do to phone's Settings>Developers Options, and there you find the option to toggle root on or off (default is off).
If you don't see Developer Options in Settings, its a bit of a quirky Android trick to make it appear. Go to Settings>About>Software information>More, then tap the "Build number" 7 times, and you will see a toast message that "You are now a developer" (yeah, that is what it really says!) and the option is now available in Settings.

Unending trouble with system partition for hydrogen

hi guys, I am having trouble with my MI Max having 32GB internal memory.
From it's behaviour for last few days I have inferred it's system partition is the culprit.
On stock miui rom, it gives msg that encryption unsuccessful and I need to factory reset it. But even after doing factory reset it shows the same msg.
Its with locked boot loader but referring one thread I could install twrp latest version on it by replacing recovery image in stock rom and flashing with mi flash tool in edl mode.
So with two I tried installing few vision rooms like miui eu ROM, RR and crdroid based on Oreo. All the rooms while flashing fine error E1001, saying system image not updated and flashing failed.
I even tried repairing file system, fixing file system, Channing file system to fat, exfat, ext2, ext3, ext4 and f2fs several times (from advanced wipe menu) but things are not improving. Even tried formatting data partition as it's suggested at few places.
I am out of ideas after spending few days trying to fix it by flashing several times.
So please if some one can assist in resolving the issue, I would really appreciate.
Thank you in advance.

You need to format data not wipe . Go to twrp choose wipe , format data and type yes . Note, by doing this you will lose all of your data if you want to keep it make sure to save it to your PC or USB drive.

Zasnizas said:
You need to format data not wipe . Go to twrp choose wipe , format data and type yes . Note, by doing this you will lose all of your data if you want to keep it make sure to save it to your PC or USB drive.
Click to expand...
Click to collapse
Have already done it several times by now. Didn't make any difference.

harpy.eagle said:
Have already done it several times by now. Didn't make any difference.
Click to expand...
Click to collapse
As discussed yesterday on unofficial LineageOS (nijel8) thread the nand is damaged. You need to delate partition, compact unallocated space & then recreate the exactly the same partition. That way it won't be on the same spot & it will work.
Use a PC with an partition manager.
https://gparted.org/

Zola III said:
As discussed yesterday on unofficial LineageOS (nijel8) thread the nand is damaged. You need to delate partition, compact unallocated space & then recreate the exactly the same partition. That way it won't be on the same spot & it will work.
Use a PC with an partition manager.
https://gparted.org/
Click to expand...
Click to collapse
Tks a lot for the reply. It gave a ray of hope to me. Though I am hearing modifying partition on android device for the first time to fix it. That too for bricked device and to do it on PC. Is there any thread guiding about it? Would read a bit about how to do it in order to not mess things up even more.

harpy.eagle said:
Tks a lot for the reply. It gave a ray of hope to me. Though I am hearing modifying partition on android device for the first time to fix it. That too for bricked device and to do it on PC. Is there any thread guiding about it? Would read a bit about how to do it in order to not mess things up even more.
Click to expand...
Click to collapse
It's still ain't bricked so you can do this relatively easy. When it's bricked EDL programmer for used NAND chip used is needed.
So take a deep breath, see the exact size & type of the partition, delate it, create a new one exactly the same (type, size & name).
https://s10629.pcdn.co/wp-content/pictures/2010/01/captured_Image1.png51.png
https://helpdeskgeek.com/wp-content/pictures/2010/01/captured_Image1.png111.png
The tool I gave you URL is very good documented and with plenty examples & user guides available all which can be found on the site, it uses graphics GUI so it's as easy as it can be. So if you are inexperienced read/watch first how it's done. After you are done flash what you want in TWRP.
Best regards.

What I meant to ask is, how to access partitions of mobile on PC? I have used partitioning app on windows but never for android device. Anyway, as u have clued, I shall try accessing partitions with mobile connected in edl mode.