Database Info

GEM-702L - Partition Table - internal storage - 32 gig showing as 4 gig

Hello,
I just want to thank anyone in advance for taking their time in reading this and trying to assist.
My situation is that I have a Mediapad x2 702L which when I purchased it, it said it was unlocked.
I go to the recovery screen and it shows unlocked but I couldn't flash anything using adb got an error saying "adb failed (remote: command not allowed)"
so I downloaded dc-unlocker, when I used that I only had the option to FBR. well I did that several times after bricking my device and had to pay $15 each time for a flash to work.
I ended up spending like $90 on this and I was able to get my device unbricked flashed back to GEM 702L B003 stock firmware, that was the only way to get it to work.
from there I was able to get root and I attempted to use several flasher .apks to flash recovery to twrp because it would not work using adb, I would have it installed but then
after the reboot it would lose it. Now at this point My internal SD card is showing it only has 4 gig's of memory when it used to have 32gig's of memory.
if I go to terminal and check partitions I have so many
cat /proc/partitions
I am unable to take a screen shot on my phone to post either
but I was wondering if anybody has ever came across this
or could assist with helping me fix my partition table
Thank you again for all your assistance.

Factory Reset?

I'm unable to do that via dc locker gives me an error now due to the partition being off

USB debugging enabled to use ADB?

Thank you very much guys, I was able to put a copy of android 6.0 on the sd and install a local update then I was able to go back to factory settings and the issue was resolved.
Another thing I noticed is that I keep loosing TWRP?
I had it on there for like 10 minutes and flashed root and two different roms
and then when I tried to boot back into recovery it showed me the stock e-recovery
I had the X2-TWRP-3.0-2-BLACK-BLUE.img flashed for my TWRP.
any idea why I keep loosing it?

You Update Local over Stock Recovery,if you want install Twrp to Android 6.0 use this
https://drive.google.com/file/d/0B5I_q70mNuR4bXJTX3JmdzZZTWs/view?usp=sharing
and flash via fastboot

You can flash TWRP to recovery2 partion as well: For example
fastboot flash recovery2 X2-TWRP-3.0-2-BLACK-BLUE.img
Then keep USB connected when rebooting and holding VOLUME UP key.
This starts TWRP.
If you are not USB connected, the standard recovery will start.
This allows to do factory resets and firmware updates without flashing recovery.img for your version again.
A dload will overwrite the recovery2 partition with the "e-recovery". In this case you will have to flash twrp again.
It's not normal that you have to pay more than once for DC-unlocker booloader It's the same code. Maybe you used the option "Get unlock code"
This is a option for SIM locked phone, but not to unlock bootloader.
"Get bootloader code" is the correct one. You can write down it and use it again and again if neccessary. (I never had to unlock twice)
fastboot oem unlock xxxx does the unlocking. That's all.
I would write do DC-unlocker and ask for return the money.

Relocked bootloader while Rooted, mate 9 (SuperSU 2.79).

After trying to flash Superuser-r275 and failing all the time. As a result of error called(No MD5 file were found). i found Super Su 2.79.
i flash my phone with it and then it boot and works perfectly except for one thing, i cannot open the Gallery or access the internal storage in any way. So i tried to get the phone to stock and i failed as im not able to get to the internal storage. so i reboot in recovery and then to bootloader and i put the command "fastboot reboot oem relock xxxxxxxxx" and press yes to lock bootloader and twrp will be removed. i selected yes and the phone reboot into huawei eRecovery mode and never Recover.
i still cant get access to the internal storage and i have lost twrp recovery.
there is any way to get it working again ?

malik11111 said:
After trying to flash Superuser-r275 and failing all the time. As a result of error called(No MD5 file were found). i found Super Su 2.79.
i flash my phone with it and then it boot and works perfectly except for one thing, i cannot open the Gallery or access the internal storage in any way. So i tried to get the phone to stock and i failed as im not able to get to the internal storage. so i reboot in recovery and then to bootloader and i put the command "fastboot reboot oem relock xxxxxxxxx" and press yes to lock bootloader and twrp will be removed. i selected yes and the phone reboot into huawei eRecovery mode and never Recover.
i still cant get access to the internal storage and i have lost twrp recovery.
there is any way to get it working again ?
Click to expand...
Click to collapse
sorry,by saying access internal storage u mean thru system or thru twrp?have u tried to unlock BL again n reflash twrp?

malik11111 said:
After trying to flash Superuser-r275 and failing all the time. As a result of error called(No MD5 file were found). i found Super Su 2.79.
i flash my phone with it and then it boot and works perfectly except for one thing, i cannot open the Gallery or access the internal storage in any way. So i tried to get the phone to stock and i failed as im not able to get to the internal storage. so i reboot in recovery and then to bootloader and i put the command "fastboot reboot oem relock xxxxxxxxx" and press yes to lock bootloader and twrp will be removed. i selected yes and the phone reboot into huawei eRecovery mode and never Recover.
i still cant get access to the internal storage and i have lost twrp recovery.
there is any way to get it working again ?
Click to expand...
Click to collapse
Unlock bootloader, flash stock recovery, relock bootloader. I don't see how this will help you get stock back though. Or do you mean you can't access download mode again?
Anyway, relocking bootloader won't make your phone stock.
And did you decrypt before flashing SuperSU (Format Data in Twrp)?

ante0 said:
Unlock bootloader, flash stock recovery, relock bootloader. I don't see how this will help you get stock back though. Or do you mean you can't access download mode again?
Anyway, relocking bootloader won't make your phone stock.
And did you decrypt before flashing SuperSU (Format Data in Twrp)?
Click to expand...
Click to collapse
first of all i cant access the internal storage from the operating system. or from a computer.
if i open Gallery or Music in my phone i would get a massage saying "insufficient storage free some space blah blah blah" and it take to clean memory. and if i try that through a computer it says that the devices has been disconnected or no is unavailable.
Secondly, how can i get to bootloader again? the device show up when i plug it to my computer but i can't see it in terminal when i use adb. there is a way to access the device in this situation ?

malik11111 said:
first of all i cant access the internal storage from the operating system. or from a computer.
if i open Gallery or Music in my phone i would get a massage saying "insufficient storage free some space blah blah blah" and it take to clean memory. and if i try that through a computer it says that the devices has been disconnected or no is unavailable.
Secondly, how can i get to bootloader again? the device show up when i plug it to my computer but i can't see it in terminal when i use adb. there is a way to access the device in this situation ?
Click to expand...
Click to collapse
if there is a way and i get the bootloader unlocked again, can someone explain how to "decrypt before flashing SuperSU (Format Data in Twrp)?"
Thank you guys.

malik11111 said:
first of all i cant access the internal storage from the operating system. or from a computer.
if i open Gallery or Music in my phone i would get a massage saying "insufficient storage free some space blah blah blah" and it take to clean memory. and if i try that through a computer it says that the devices has been disconnected or no is unavailable.
Secondly, how can i get to bootloader again? the device show up when i plug it to my computer but i can't see it in terminal when i use adb. there is a way to access the device in this situation ?
Click to expand...
Click to collapse
First (If you don't have Developer Settings in Settings) go to Settings - About and tap on Build Number a few times until it says "You're now a developer". Go back and tap on Developer settings and turn on usb debugging. Now see if adb wants to work. If it does use "adb reboot bootloader", else hold Vol Down + Power, release power when phone has rebooted and vibrated again. Download mode should display kind of instantly. Try if fastboot works.
For root, follow this: https://forum.xda-developers.com/mate-9/how-to/guide-how-to-root-mate-9-decrypt-data-t3569986

i tried the to connect the phone to my computer and hold the power down. and i got into the bootloader mode but i could not flash twrp again or flash the phone to stock.. alos i found that FRP is locked. what to do in this case guys.

Enable oem unlock in developer settings, to disable FRP LOCKED in fastboot mode

the device does not boot at all
im stuck on the eRecovery page.

ok guys i have found a way out of the problem that i was stuck at, i open the phone through a an application called DC phoenix and i could boot the device
but now i would like to get my phone back to its stock Rom. how can i do that? i tried couple of different ways but i get error when it come to install the package|_type? any idea?
Please note that dc phonix has deleted the IMEI for the device and Serial Number
now i have like IMEI:000000000000 and serial number :0123456789ABCDE
please if anyone know a way let me know guys.

Moto G XT1033 - SDCARD read only

Hi all,
Last week my MOTO G gone... It was locked in Motorola screen. I let it discharger 0% so many times last week.
My device was bootloader locked, with no USB debugging.
Ok, i search a lot and found some information. I used the bellow link:
https://forum.xda-developers.com/moto-g/help/moto-g-bootup-problem-recovery-mode-t3122492/
I ran bootloader and try recovery option, but got "Boot up failed message"
I did the some steps: unlock bootloader and then I tried flash a rom in fastboot. No error message returns, but the device always stay in unlocked bottloader screen. I used XT1033 5.02, 5.1 roms but without success.
Then... Tried command:
mfastboot flash recovery twrp-3.2.1-0-falcon.img
But when I reboot phone and entered recovery, got "no command" error.
Following my link guide above, I tried the command:
mfastboot boot twrp-3.2.1-0-falcon.img
And success! I finally could enter in TWRP and backup all my data. Good!
But my sdcard is appearing as read only!
I tried:
WIPE option (Wipes Data, Cache and Dalvik),
Advanced WIPE option (the partitions before and Data and Internal Storage ),
and Format Data option - No success
I did all the steps with partition Data mounted and repeated it again unmounted, booting the device in each try.
I tried the option Repair or Change File System (/data is F2fs) and tried to change the partition to EXT4 - no success.
I tried the same commands described in page 7:
https://forum.xda-developers.com/moto-g/help/moto-g-bootup-problem-recovery-mode-t3122492/page7
and got the same results - no success.
I tried to use PUSH command, but it returns error failed to copy <filename> - read only file system.
Please, could you help me? Thanks in advance.

Your phone's eMMC chip probably died. You have no choice but to do a motherboard replacement. Or get just the chip replaced, but it's risky, since it involves resoldering and reballing BGAs.
Those frequent full discharges killed the chip, I suspect.
Since you've got your data backed up, I suggest you try either of these options.

Can't boot

I went through the process of using Smali and Magisk on my phone. Everything was good. Since I was doing this for PoGo, I decided to "clean-up" by disabling some of the settings. I turned off OEM unlocking, reboot the phone in to the bootloader and did a adb flashing lock. I rebooted the phone and not get the error "Can't find a valid operating system". I can boot in to the bootloader with the power button + down volume but I can't unlock the bootloader with ADB and fastboot.
Am I screwed?

I'm also not able to boot in to recovery. I also get the error "Can't find valid operation system"

Well probably too late to reply.
I'm not an expert, i'm newbee but when i installed my custom rom i met some problems to reboot. I solved them by re-installing firm operating system. You can do it by connecting your device with a good usb cable and go to google website : android flash tool
This will reinstall a new an clean system (but erase your data if not saved before).
After that you can install a custom rom from the begining.

Question Rebooting error after flashing firmware with Odin

Hello everyone,
I need some help with the following situation:
Using Odin I successfully flashed my Galaxy A32 5G with Android 13 (as indicated by the green PASS in Odin).
When the phone tries to reboot, I get the dreaded error message, "Can't load Android system. Your data may be corrupt....."
On my PC I issued the command, >adb devices, but no devices were found.
This is probably because I did not enable USB debugging, when the phone was still working.
I'm trying to avoid doing a factory reset, because I don't want all my data wiped.
According to the following article, you can flash an OTA file using "adb sideload" command, even without enabling USB debugging.
However, everything else I've read says that adb commands work only when USB debugging is enabled.
Fix “Can’t Load Android System Your Data May Be Corrupt” Without Reset​https://www.droidwin.com/fix-cant-load-android-system-your-data-may-be-corrupt-without-reset/
Can someone perhaps clarify whether or not USB debugging is required for using adb commands?
Thank you very much,
Peter

plee12 said:
Hello everyone,
I need some help with the following situation:
Using Odin I successfully flashed my Galaxy A32 5G with Android 13 (as indicated by the green PASS in Odin).
When the phone tries to reboot, I get the dreaded error message, "Can't load Android system. Your data may be corrupt....."
On my PC I issued the command, >adb devices, but no devices were found.
This is probably because I did not enable USB debugging, when the phone was still working.
I'm trying to avoid doing a factory reset, because I don't want all my data wiped.
According to the following article, you can flash an OTA file using "adb sideload" command, even without enabling USB debugging.
However, everything else I've read says that adb commands work only when USB debugging is enabled.
Fix “Can’t Load Android System Your Data May Be Corrupt” Without Reset​https://www.droidwin.com/fix-cant-load-android-system-your-data-may-be-corrupt-without-reset/
Can someone perhaps clarify whether or not USB debugging is required for using adb commands?
Thank you very much,
Peter
Click to expand...
Click to collapse
I think, In stock recovery only the adb sideload command works so it don't need USB Debugging to be turned ON.

aiSanaul said:
I think, In stock recovery only the adb sideload command works so it don't need USB Debugging to be turned ON.
Click to expand...
Click to collapse
Thanks for your input. Encouraged by your input, I read the article again and realized that I have to put the phone in sideload mode first.
So, I went back to the stock recovery mode and selected the menu item, "Apply update from ADB". Then I see the message on the phone, "Now send the package you want to apply....with adb sideload <filename>". Now that I thought the phone was in sideload mode, on the PC I entered ">adb devices". This time it recognized the device and displayed the device name. However, it also displayed the word, "unauthorized", after the device name. According to the article, if sideload is properly entered, it should display the word, "sideload".
Anyway I tried entering ">adb sideload update.zip", and I got the error message, "device unauthorized".
So, any idea how to get the phone to be authorized?
If this is not possible, I was thinking of replacing the stock recovery with a custom recovery like TWRP. This way I can at least back up all my data first before doing a factory reset. However, I believe installing TWRP requires the bootloader to be unlocked, which automatically wipes all data. So, this defeats the purpose of installing TWRP in the first place
Is there some trick to install TWRP without unlocking the bootloader?
Thank you

plee12 said:
Thanks for your input. Encouraged by your input, I read the article again and realized that I have to put the phone in sideload mode first.
So, I went back to the stock recovery mode and selected the menu item, "Apply update from ADB". Then I see the message on the phone, "Now send the package you want to apply....with adb sideload <filename>". Now that I thought the phone was in sideload mode, on the PC I entered ">adb devices". This time it recognized the device and displayed the device name. However, it also displayed the word, "unauthorized", after the device name. According to the article, if sideload is properly entered, it should display the word, "sideload".
Anyway I tried entering ">adb sideload update.zip", and I got the error message, "device unauthorized".
So, any idea how to get the phone to be authorized?
If this is not possible, I was thinking of replacing the stock recovery with a custom recovery like TWRP. This way I can at least back up all my data first before doing a factory reset. However, I believe installing TWRP requires the bootloader to be unlocked, which automatically wipes all data. So, this defeats the purpose of installing TWRP in the first place
Is there some trick to install TWRP without unlocking the bootloader?
Thank you
Click to expand...
Click to collapse
As you already know this is not possible without unlocking bootloader, I will explain further more to make it easy to understand.
If you don't unlock your bootloader and try flashing TWRP on your phone using ODIN Flash Tool then maybe your phone get into an veification error and your phone will end up in a softbrick. You can repair your phone by flashing your phone's stock firmware using ODIN Flash Tool, eventually you will wnd up loosing all your data.
Also unlocking bootloader in Samsung devices is so easy by turning OEM Unlocking in Developer options, but you don't seem to have access to your phone.
An Unlocked Bootloader is the PASS, which allows you to do custom thing to your phone. So without it, this won't work, maybe that is why you got that error “Can’t Load Android System Your Data May Be Corrupt”.
ALTERNATIVELY you can try flashing your phone's OLD original Stock Firmware using ODIN Flash Tool and see what happens. You can also try flashing TWRP through ODIN Flash Tool. Only flash OFFICIAL TWRP made for your device (if any), otherwise you don't have options I guess.
also Why didn't you Unlocked Bootloader before flashing a custom rom? because of warranty?

aiSanaul said:
As you already know this is not possible without unlocking bootloader, I will explain further more to make it easy to understand.
If you don't unlock your bootloader and try flashing TWRP on your phone using ODIN Flash Tool then maybe your phone get into an veification error and your phone will end up in a softbrick. You can repair your phone by flashing your phone's stock firmware using ODIN Flash Tool, eventually you will wnd up loosing all your data.
Also unlocking bootloader in Samsung devices is so easy by turning OEM Unlocking in Developer options, but you don't seem to have access to your phone.
An Unlocked Bootloader is the PASS, which allows you to do custom thing to your phone. So without it, this won't work, maybe that is why you got that error “Can’t Load Android System Your Data May Be Corrupt”.
ALTERNATIVELY you can try flashing your phone's OLD original Stock Firmware using ODIN Flash Tool and see what happens. You can also try flashing TWRP through ODIN Flash Tool. Only flash OFFICIAL TWRP made for your device (if any), otherwise you don't have options I guess.
also Why didn't you Unlocked Bootloader before flashing a custom rom? because of warranty?
Click to expand...
Click to collapse
Thanks very much for your detailed explanations and for your continued support.
Let me answer your question first about why I didn't unlock the bootloader before flashing a custom ROM. Let me backtrack and explain how this problem came about in the first place. My phone was doing an automatic system update two weeks ago (Android 13). After downloading and installing, it tried to boot up. That's when it got stuck in an infinite rebooting loop. At that point, I had no way to change any settings on the phone.
Also, to clear up any confusion, I was not trying to flash a custom ROM. I was simply trying to flash the stock ROM (Android 13), supposedly the same firmware version as the OTA that broke my phone after the automatic system update. I was thinking that perhaps there was an internet glitch during the automatic system update process, which corrupted the OS. So, I was just trying to re-install the same version as the OTA to see if that would solve the problem.
I had also thought about flashing the original version that came with the device (Android 11). But, I think I read somewhere that either Samsung phones do not allow the user to downgrade, or even if it does allow you do so, the downgrading process will wipe out the existing data on the phone. Perhaps you can confirm that or not?
In the meantime, as you suggested, I will look into how to flash TWRP.
Thank you