Phone is Extremely Weirdly Bricked - ONE Q&A, Help & Troubleshooting

So first, I transferred a file to my phone. I was quite low on storage (about 3 gb left) before the transfer, but the file was around 2.4gb, so it fit. I wanted to transfer that file to another computer, so when I plugged it in the other computer, a local disk drive shows up as opposed to mtp. I figure that it was probably a glitch. When I restart the phone, it boots, but instead of having 600 mb of free space left, it has 1134mb left. Somehow the available space just increased, so I decide to reboot again. The bootloader shows up, but then it simply goes to a black screen with no boot logo. When I plug my phone back into the computer, it opens 4 disk drive prompts saying I need to format the drive so that it can be used, and one that shows something. When I go in the "drive", there is one folder called image, and in the folder there is a bunch of files like modem.b00 as shown in the image attached..
It seems that instead of mounting the internal storage, it is mounting the firmware.
I am able to boot into recovery however, but nothing I have done seems to help. I have tried flashing several firmwares again with different recoveries (2.8.7.0.5 and 3.0.0) and restoring the efs partition again. I cannot delete any files off my phone through recovery as it yields an ERROR=1 and through MTP when I delete a file, it appears the file is deleted, but when I unplug and plug the phone back in, the file is back. I can however transfer files from my phone to the computer, but not vice versa.
It is also able to read but not write, meaning that my internal storage may be faulty, or that the file caused a corruption on my phone. If anyone has any ideas on how to fix it or has any experience with this, please let me know.

Can you access fastboot?
Sounds like it may be an issue with the userimage data try a reflash using the link below but edit the bat file (or .sh file) to only include the following line:
Code:
fastboot flash userdata userdata_64G.img (or userdata.img if you have a 16GB model)
you can grab a zip with the entire OS here and you will need to setup fastboot drivers properly (which sounds like you would have already done)
Return OPO to 100% Stock

itechy said:
Can you access fastboot?
Sounds like it may be an issue with the userimage data try a reflash using the link below but edit the bat file (or .sh file) to only include the following line:
Code:
fastboot flash userdata userdata_64G.img (or userdata.img if you have a 16GB model)
you can grab a zip with the entire OS here and you will need to setup fastboot drivers properly (which sounds like you would have already done)
Return OPO to 100% Stock
Click to expand...
Click to collapse
Yep, fastboot works and I already have the drivers set up. Do I only need to restore the userdata?

f41lbl0g said:
Yep, fastboot works and I already have the drivers set up. Do I only need to restore the userdata?
Click to expand...
Click to collapse
Flashing the userdata partition via fastboot will wipe all data so I hope you have your stuff backed up. Best solution now is to fastboot flash COS12.1.1 and see if it turns on
Sent from my A0001 using Tapatalk

Renosh said:
Flashing the userdata partition via fastboot will wipe all data so I hope you have your stuff backed up. Best solution now is to fastboot flash COS12.1.1 and see if it turns on
Sent from my A0001 using Tapatalk
Click to expand...
Click to collapse
I'm currently in the process of backing everything up, but can't I just format /data through recovery since TWRP works?
Tried flashing the userdata_64G.img, here is what I get:
C:\adb>fastboot flash userdata userdata_64G.img
target reported max download size of 1073741824 bytes
erasing 'userdata'...
OKAY [ 3.829s]
sending 'userdata' (56 KB)...
OKAY [ 0.016s]
writing 'userdata'...
FAILED (remote: Bogus size sparse and chunk header)
finished. total time: 3.860s

f41lbl0g said:
I'm currently in the process of backing everything up, but can't I just format /data through recovery since TWRP works?
Click to expand...
Click to collapse
You can try that but no guarantees it will work.
You can either wipe everything (/system /data /internal storage /cache and /dalvik) with advanced wipe for TWRP 2.8.6.0 (recommended version) then transfer the flashable version of COS12.1.1 from link below and flash
http://forum.xda-developers.com/showthread.php?t=2906746
Or you can fastboot flash the entire COS12.1.1 fastboot using commands manually from the previous link the other poster gave you. You will run into some problems if you decide you wanna try some AOSP ROMs after flashing the userdata from COS12.1.1 but if you stick to CM you'll be fine
Sent from my A0001 using Tapatalk

Renosh said:
You can try that but no guarantees it will work.
You can either wipe everything (/system /data /internal storage /cache and /dalvik) with advanced wipe for TWRP 2.8.6.0 (recommended version) then transfer the flashable version of COS12.1.1 from link below and flash
http://forum.xda-developers.com/showthread.php?t=2906746
Or you can fastboot flash the entire COS12.1.1 fastboot using commands manually from the previous link the other poster gave you. You will run into some problems if you decide you wanna try some AOSP ROMs after flashing the userdata from COS12.1.1 but if you stick to CM you'll be fine
Sent from my A0001 using Tapatalk
Click to expand...
Click to collapse
Ok I had to fastboot flash the entire COS2.1.1, and it is working well now. Why is there an issue with AOSP roms after flashing the userdata?

f41lbl0g said:
Ok I had to fastboot flash the entire COS2.1.1, and it is working well now. Why is there an issue with AOSP roms after flashing the userdata?
Click to expand...
Click to collapse
I don't know what is up with the userdata image for COS12.1.1 but its corrupted in some way and you cannot flash ROMs like Omni and OxygenOS. It acts as if you've encrypted the OS when you haven't, solution is to wipe using an older userdata partition like the one from COS12.1 or earlier.
Sent from my A0001 using Tapatalk

Renosh said:
I don't know what is up with the userdata image for COS12.1.1 but its corrupted in some way and you cannot flash ROMs like Omni and OxygenOS. It acts as if you've encrypted the OS when you haven't, solution is to wipe using an older userdata partition like the one from COS12.1 or earlier.
Sent from my A0001 using Tapatalk
Click to expand...
Click to collapse
Do you have a link to an old userdata partition?

f41lbl0g said:
Do you have a link to an old userdata partition?
Click to expand...
Click to collapse
Sorry I don't you'll have to download from the link I shared earlier an entire fastboot zip to be able to do it
Sent from my A0001 using Tapatalk

Related

flash recovery by fastboot

I got twrp recovery installed, but i accidently flash over system now it whot boot . i tryeed writing another one but i got this error .img
sending 'system' (262144 KB)... OKAY [ 27.641s]
writing 'system'... FAILED (remote: (00120000)).. i can still get into twrp. but no sdcard. so i can put rom on sdcard to install. anyone got the system i need to write
Try putting a ROM on the external SD card and flash a ROM from there.
Could try flashing another recovery, try CWM maybe?
No worries, try flashing the recovery again and delete your system partition with this:
Code:
fastboot erase system
Then try flashing the system another time, if not work try doing what @matt4321 recommended :thumbup:
XxLordxX said:
No worries, try flashing the recovery again and delete your system partition with this:
Code:
fastboot erase system
Then try flashing the system another time, if not work try doing what @matt4321 recommended :thumbup:
Click to expand...
Click to collapse
I don't have a externail sd card. thats the problem. i have cwm on it now. but it not letting flash the system i kept getting errors.
james89beggs said:
I don't have a externail sd card. thats the problem. i have cwm on it now. but it not letting flash the system i kept getting errors.
Click to expand...
Click to collapse
grab the sdcard from your phone (if you have an sdcard in your phone, if not borrow one out of a buddies phone)

Accidentally wiped internal storage..need help adb pushing rom!

as the title states..in a rush i accidentally wiped my internal storage and everything else..i can get into recovery and fastboot mode
i have all the adb drives and stuff installed from when i previously used it (months ago)
when i plug my phone into my pc in fastboot it doesnt not connect and adb devices does not list it as connected
please PM me and help me..i just need to push a rom onto the phone so i can flash it
jdiddy_ub said:
as the title states..in a rush i accidentally wiped my internal storage and everything else..i can get into recovery and fastboot mode
i have all the adb drives and stuff installed from when i previously used it (months ago)
when i plug my phone into my pc in fastboot it doesnt not connect and adb devices does not list it as connected
please PM me and help me..i just need to push a rom onto the phone so i can flash it
Click to expand...
Click to collapse
That's ironic, the very same thing happen to me yesterday except in my case I undervolted too low and corrupted the data, had to format everything.
Which recovery are you using? PhilZ Touch allows you to push stuff onto the internal storage.
The command would be "adb push (name of your folder) /sdcard/"
thanks for the response...im using TWRP...i just decided to flash the stock images and start from scratch
adb doesn't work in fastboot mode. Only fastboot works in fastboot mode. adb works only in recovery mode or Android mode. adb and fastboot are NOT the same thing. They are not synonymous
Sent from my Nexus 5 using Tapatalk
Get fastboot and adb exes for windows.
Add them to your PATH to make them available from everywhere.
If you dont know from where to get fastboot and adb and you dont know how to add them to the PATH, then this is for you.
If you choose TWRP to flash new rom:
If you are on windows 8 or 8.1 then disable driver signature enforcement.
You need universal naked drivers.
Open CMD window on your PC.
Go to that directory where the rom.zip is. (The commands you need to navigate between folders: dir and cd)
For adb push:
Type this in the CMD window and flash it in TWRP:
Code:
adb push rom.zip /sdcard
For adb sideload:
In twrp: Advanced->ADB Sideload->Swipe to Start Sideload
Then type this in the CMD window:
Code:
adb sideload rom.zip
If you ends up in boot loop do a factory reset.
For flashing factory images:
Enter the phone to fastboot mode and connect it to the PC
Install usb drivers from google.
Download factory images for nexus 5 and extract it.
Run flash-all.bat.
If you are still lost I recommend you these threads:
[TUTORIAL] How to flash a factory image | Return to stock | Unroot/SAVE your Nexus 5
[Tutorial] How to flash factory images with LG Flashtool
I've been having trouble with this..... When I wipe data in twrp it also wipes internal storage. How are people wiping their device for a clean rom install?
Sent from my Nexus 5 using Tapatalk
toprunner2786 said:
I've been having trouble with this..... When I wipe data in twrp it also wipes internal storage. How are people wiping their device for a clean rom install?
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
For me, by not using TWRP
rootSU said:
For me, by not using TWRP
Click to expand...
Click to collapse
Oh.... Interesting I guess I never thought that it could be an issue with the recovery itself.... I just assumed it was operator error.
So I would assume CWM is the obvious alternative.... Is there anything else that is recommended?
Sent from my Nexus 5 using Tapatalk
Link in signature
Sent from my Nexus 5 using Tapatalk
toprunner2786 said:
I've been having trouble with this..... When I wipe data in twrp it also wipes internal storage. How are people wiping their device for a clean rom install?
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
What do you mean by internal storage? Wiping data will wipe your apps but anything on your internal sdcard should not be wiped. Backups, etc
Sent from my Nexus 5 using XDA Free mobile app
toprunner2786 said:
I've been having trouble with this..... When I wipe data in twrp it also wipes internal storage. How are people wiping their device for a clean rom install?
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
What I do is reboot to twrp. Select wipe then swipe that thing which tells me "swipe to factory reset".
This does wipes /cache and /data without deleting /data/media. The files on the internal storage is in /data/media/0
What I do not do is selecting Format data and type yes for format or going into the advanced wipe and select /sdcard to format too.
hey
jdiddy_ub said:
as the title states..in a rush i accidentally wiped my internal storage and everything else..i can get into recovery and fastboot mode
i have all the adb drives and stuff installed from when i previously used it (months ago)
when i plug my phone into my pc in fastboot it doesnt not connect and adb devices does not list it as connected
please PM me and help me..i just need to push a rom onto the phone so i can flash it
Click to expand...
Click to collapse
hey i have the same problem dude can you please help me with this
Hi, can anyone help me, I got problem.
I have Lenovo A526 phone stuck in logo. First time I used Sp Flash Tools & Stock Rom to fix, after all done the popup said "Download OK" but after restart it still hang in logo. I tried few time.
Stock ROM from this site: http://firmwarefile.com/lenovo-a526 And I use SP_Flash_Tool_v5.1628 from that site too.
Then I use this rom: http://www.symbianize.com/showthread.php?t=1184121 With the same SP_Flash_Tool_v5.1628. I use " [Custom ROM] A526 is based on a sink firmware ROW_031 for Lenovo a526 " from FoxtrotKZ, result still same.
Later I've used ADB & TWRP recovery to install a custom rom. With this custom rom:
http://www.needrom.com/download/miui...v5-5-01-16-ru/
https://filosofipohonkelapa.wordpres...n-ke-lollipop/
http://www.mastahdroid.com/2015/08/c...novo-a526.html
I tried via adb sideload and via sdcard too. Same result.
On TWRP recovery the message said "Installation Done ! Please Reboot ! Successful".
But at the end of line of installation, it's written:
Updating partition details...
E:Unable to mount '/cache'
E:Unable to mount '/data'
E:Unable to mount '/system'
Then I reboot and it still hang in logo
https://postimg.org/image/6tlj5nem7/
I boot to recovery and tried "wipe" option, Same result.
https://postimg.org/image/oibdy3b7f/
Dont know the meaning of that and fix this. Can anyone help? Thank you.
Can i recover files pictures after swiping/format on twrp?
danarama said:
adb doesn't work in fastboot mode. Only fastboot works in fastboot mode. adb works only in recovery mode or Android mode. adb and fastboot are NOT the same thing. They are not synonymous
Click to expand...
Click to collapse
omg you saved me, thank you so much for this info!
I'm using nexus 6p and when I try to install new pie Ron with FBE instead of FDE, I use a USB OTG adapter and install the zip from USB storage then completely format internal storage.
So if you have USB OTG then you can mount the USB storage into TWRP and install from there

Problem with partition sdcard after fail flash

Hello,
That last night I wanted to flash a new ROM from 4.4 to 5.0.1.
I had some bugs, like my full SD card, therefore i installed nothing like apps or pictures .
So I try to re-flash the ROM again after a factory reset.
But, i can not reflash since it has wipe my SD card ..
So I managed to reconnect my phone and flash a recovery.
However, when I install a ROM (official google, or custom), it no longer detects my SD card
when the flash rom: E: unknown volume for path / sd-ext.
I try everything, I do not know how to repartition as originally my SD card.
I hope she is not dead as impossible to get out of my phone ...
I manage to mount the SD card, but still the sd-ext partition that does not exist ...
I just followed here: http://forum.xda-developers.com/goo...o-repairing-corrupted-data-partition-t2577447
everything works, but again, the sd-ext partition ..
I manage to get to the bootloader, recovery, I can flash a ROM anyway!
However, when I want to take a picture / install / sms .... I get an error "No SD card" or not avaialble space.
I need your help, since yesterday I have no phone ..
Best Regards,
sleakerz said:
Hello,
That last night I wanted to flash a new ROM from 4.4 to 5.0.1.
I had some bugs, like my full SD card, therefore i installed nothing like apps or pictures .
So I try to re-flash the ROM again after a factory reset.
But, i can not reflash since it has wipe my SD card ..
So I managed to reconnect my phone and flash a recovery.
However, when I install a ROM (official google, or custom), it no longer detects my SD card
when the flash rom: E: unknown volume for path / sd-ext.
I try everything, I do not know how to repartition as originally my SD card.
I hope she is not dead as impossible to get out of my phone ...
I manage to mount the SD card, but still the sd-ext partition that does not exist ...
I just followed here: http://forum.xda-developers.com/goo...o-repairing-corrupted-data-partition-t2577447
everything works, but again, the sd-ext partition ..
I manage to get to the bootloader, recovery, I can flash a ROM anyway!
However, when I want to take a picture / install / sms .... I get an error "No SD card" or not avaialble space.
I need your help, since yesterday I have no phone ..
Best Regards,
Click to expand...
Click to collapse
Easiest way to solve is just to flash a factory image - follow ALL the instructions on this page: https://developers.google.com/android/nexus/images
Have a read of RootSU's post about file system issues after updating - explains how and why this happens, and how to fix. I would just do the above though, just so you know you're totally back to stock.
http://forum.xda-developers.com/google-nexus-5/general/sdcard-problems-upgrading-android-t2938749
it looks run, I can now see my sd card, install applications ...
However, some problem:
- In aborescence I have : sdcard, then 0 / legacy / OBB
Is it the same for you? Is like this for 5.0?
- When flash: E unknown volume to path sd-ext. Unable to unmount or mount /system, but I was able to boot; and it seems to work ..
- Clean master does not detect anything (unnecessary file or anything ..) Why?
- What recovery do you recommend?
- In storage: Various weighs 5.68gb, but there is nothing on it, how to clean?
sleakerz said:
it looks run, I can now see my sd card, install applications ...
However, some problem:
- In aborescence I have : sdcard, then 0 / legacy / OBB
Is it the same for you? Is like this for 5.0?
- When flash: E unknown volume to path sd-ext. Unable to unmount or mount /system, but I was able to boot; and it seems to work ..
- Clean master does not detect anything (unnecessary file or anything ..) Why?
- What recovery do you recommend?
- In storage: Various weighs 5.68gb, but there is nothing on it, how to clean?
Click to expand...
Click to collapse
- go to general > stick roll-up and find my data loss/recovery thread it explains all the /sdcard quirks
- you don't have sd-ext, that's why. you can't mount /system if its already mounted
- who knows?
- TWRP
- again check my recovery /loss thread and also my "sdcard problems" thread in general. particularly the part about lost Nandroid backups
Your best bet is to read those threads, find any lost backups and wipe storage via TWRP
"you don't have sd-ext, that's why. you can't mount /system if its already mounted"
It is normal ? Or it's a problem ? How can i fix it ?
I don't have any Nandroid backup, mine didn't worked ..
sleakerz said:
"you don't have sd-ext, that's why. you can't mount /system if its already mounted"
It is normal ? Or it's a problem ? How can i fix it ?
I don't have any Nandroid backup, mine didn't worked ..
Click to expand...
Click to collapse
Its normal.
Please find and read those threads.
I'm french, and so i didn't understand all , i'm in which case ?
If i understand well, i just have to wipe "data" partition ?
As you say, i have sdcard\0\0\0
Which one i have to moove ?
sleakerz said:
I'm french, and so i didn't understand all , i'm in which case ?
If i understand well, i just have to wipe "data" partition ?
As you say, i have sdcard\0\0\0
Which one i have to moove ?
Click to expand...
Click to collapse
Go to /data/media/0. That's where everything should be. When you're in /data/media/0, you shouldn't see any more "0" folders. If you do, take everything out of those "0" folders and put it all in /data/media/0
So for example you should have your photos in /data/media/0/DCIM. If you have /data/media/0/0/0/0/DCIM, obviously that is wrong.
Sometimes its easiest to wipe everything a d start fresh so copy any data you want to keep to PC, then flash the 5.0.1 full factory image, wiping your device back to default completely.
I just did this, i flashed a full factory image this morning, it was the same ..
I made a factory, wipe a new ROm, always the same, i made everything, nothing work .
the sdcard is boring me ..
I don't know what to do ..
sleakerz said:
I just did this, i flashed a full factory image this morning, it was the same ..
I made a factory, wipe a new ROm, always the same, i made everything, nothing work .
the sdcard is boring me ..
I don't know what to do ..
Click to expand...
Click to collapse
It can't be the same if you flash the full factory image. Please explain the exact steps you took to flash full factory image.
I downloaded : hammerhead-lrx22c-factory-0f9eda1b.tgz
I unzipped , to get the flash-all.bat script (http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701)
I make a factory reset
-- E : unknown volume for path [/sd-ext]
I launch the script : http://i.gyazo.com/177625d0c7f9ba60bc207e39536b0b31.png i've got this ..
What i can do now ?
sleakerz said:
I downloaded : hammerhead-lrx22c-factory-0f9eda1b.tgz
I unzipped , to get the flash-all.bat script (http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701)
I make a factory reset
-- E : unknown volume for path [/sd-ext]
I launch the script : http://i.gyazo.com/177625d0c7f9ba60bc207e39536b0b31.png i've got this ..
What i can do now ?
Click to expand...
Click to collapse
Unpack all the .img files and do this
fastboot erase system
fastboot flash system system.img
fastboot erase userdata
fastboot flash userdata userdata.img
fastboot flash boot boot.img
Read general > sticky roll-up> adb and fastboot.... If you get stuck with that
fastboot flash bootloader C:/image-hammerhead-krt16m/bootloader.img
fastboot reboot-bootloader
fastboot flash radio C:/image-hammerhead-krt16m/radio.img
fastboot reboot-bootloader
fastboot flash system C:/image-hammerhead-krt16m/system.img
fastboot flash userdata C:/image-hammerhead-krt16m/userdata.img
(Note: this command will wipe your device (including /sdcard), EVEN if your bootloader is already unlocked.)
fastboot flash boot C:/image-hammerhead-krt16m/boot.img
fastboot flash recovery C:/image-hammerhead-krt16m/recovery.img
fastboot erase cache
And it's seems to work, like you can see : http://i.gyazo.com/f84948dd6d444a47b114437b8878a314.png
Now i have a factory image, what can i do to use a new ROM / get root and unlock bootloader (if it's not done ?)
sleakerz said:
fastboot flash bootloader C:/image-hammerhead-krt16m/bootloader.img
fastboot reboot-bootloader
fastboot flash radio C:/image-hammerhead-krt16m/radio.img
fastboot reboot-bootloader
fastboot flash system C:/image-hammerhead-krt16m/system.img
fastboot flash userdata C:/image-hammerhead-krt16m/userdata.img
(Note: this command will wipe your device (including /sdcard), EVEN if your bootloader is already unlocked.)
fastboot flash boot C:/image-hammerhead-krt16m/boot.img
fastboot flash recovery C:/image-hammerhead-krt16m/recovery.img
fastboot erase cache
And it's seems to work, like you can see : http://i.gyazo.com/f84948dd6d444a47b114437b8878a314.png
Now i have a factory image, what can i do to use a new ROM / get root and unlock bootloader (if it's not done ?)
Click to expand...
Click to collapse
You didn't do the commands I said. The erase was important
You would need to fastboot flash a custom recovery and either flash a custom ROM from that recovery or flash SuperSU from recovery depending if you want a new ROM or just root
i didn't do the command, but as you can see in the screen, just after "fastboot flash system C:/image-hammerhead-krt16m/system.img"
there is : "erasing system.. OKAY"
So i think it's good no ?
sleakerz said:
i didn't do the command, but as you can see in the screen, just after "fastboot flash system C:/image-hammerhead-krt16m/system.img"
there is : "erasing system.. OKAY"
So i think it's good no ?
Click to expand...
Click to collapse
I just wanted you to do it manually yourself, for userdata
Really thank for your help rootSU !
Now, everything works like a charm : )
sleakerz said:
Really thank for your help rootSU !
Now, everything works like a charm : )
Click to expand...
Click to collapse
Great news. Thanks for letting us know
No SD Card
Sorry if wrong thread but, my problem is:
If I'm in twrp it sees the sdcard and all things on it.
In system it doesn't see the things on the SD card.
Please don't return that I have to do a factory reflash.
If I try to download sth. It gives a toast "No Sd Card" .
I can't take it out because I've got a Nexus 4.
Pls. Help me.

[Q] Help i may have doomed my tablet.

So here's my situation.
I was trying to move a file from my internal storage to my microsd using the twrp file manager, it was successful but file remained in the internal storage at the sametime the file was in my microsd. So i thought it might be a glitch so I rebooted and entered to twrp again, but suddenly the splash screen flashed and froze. So i rebooted it again and tried again, the samething happened. It just flashed and then frozed at the twrp splash screen. I tried to drain my tablet and then turned it on and tried to go to the twrp, but the samething happened. I tried booting to android but it wont boot, i'm using grimlock 4.0 and I'm on data2sd. It's stuck at the pre.init screen. I can use fastboot, i tried to reflash twrp with the lastest one, i erased the previous one and flashed the latest one using fastboot, it worked but it cannot mount any partitions except my microsd card and whenever you reboot it and go back to recovery the twrp screen flashes and freezes. I need help i think i may have doomed my tablet.
P.s i erased the boot, system, partitions in hopes that i can reset everything but apparently it doesn't work.
supernova0 said:
So here's my situation.
I was trying to move a file from my internal storage to my microsd using the twrp file manager, it was successful but file remained in the internal storage at the sametime the file was in my microsd. So i thought it might be a glitch so I rebooted and entered to twrp again, but suddenly the splash screen flashed and froze. So i rebooted it again and tried again, the samething happened. It just flashed and then frozed at the twrp splash screen. I tried to drain my tablet and then turned it on and tried to go to the twrp, but the samething happened. I tried booting to android but it wont boot, i'm using grimlock 4.0 and I'm on data2sd. It's stuck at the pre.init screen. I can use fastboot, i tried to reflash twrp with the lastest one, i erased the previous one and flashed the latest one using fastboot, it worked but it cannot mount any partitions except my microsd card and whenever you reboot it and go back to recovery the twrp screen flashes and freezes. I need help i think i may have doomed my tablet.
P.s i erased the boot, system, partitions in hopes that i can reset everything but apparently it doesn't work.
Click to expand...
Click to collapse
As long as you can fastboot, you have not 'doomed' your tablet.
Flash newest stock ROM from ASUS site and you will be set:
1. Unzip stock ROM zip file twice and you will get a file 'blob'
2. Put blob file into fastboot folder.
3. Fastboot ROM using:
Code:
fastboot -i 0x0b05 flash staging blob [enter]
fastboot -i 0x0b05 reboot [enter]
4. Let blue progressbar finish (will need a long, long time) and tab will reboot itself.
5. Now you should be on working stock ROM and can flash custom TWRP (2.8.x.x).
Good luck!
das chaos said:
As long as you can fastboot, you have not 'doomed' your tablet.
Flash newest stock ROM from ASUS site and you will be set:
1. Unzip stock ROM zip file twice and you will get a file 'blob'
2. Put blob file into fastboot folder.
3. Fastboot ROM using:
Code:
fastboot -i 0x0b05 flash staging blob [enter]
fastboot -i 0x0b05 reboot [enter]
4. Let blue progressbar finish (will need a long, long time) and tab will reboot itself.
5. Now you should be on working stock ROM and can flash custom TWRP (2.8.x.x).
Good luck!
Click to expand...
Click to collapse
I was able to that, but the filesystem that I was using was f2fs so when I booted to the stockrom it said" encryption unsuccessful" so i had to format my data partition to a compatible format. so i flash twrp recovery, but I had the same problem, the screen flashes and then it stays at the twrp splash screen. then I thought it might be a problem with my data partition, so I erased my whole data partition using fastboot, with the command
fastboot format userdata
it worked and the recovery is working also, but my filesystem is on ext3 and I know ext 4 is better than ext 3, so using the twrp recovery I formatted my data partition to ext4 but suddenly the recovery hangs and doesn't finish the format. it there a way that this could be fixed? I really want to use a better file system.
supernova0 said:
..... I formatted my data partition to ext4 but suddenly the recovery hangs and doesn't finish the format. it there a way that this could be fixed? I really want to use a better file system.
Click to expand...
Click to collapse
Probably it didn't hang but you didn't have the patience! Formatting a /data partition to ext4 can last a long, long time. People reportet as much as 90 min. In my case it was 30 min. So, be patient!
das chaos said:
Probably it didn't hang but you didn't have the patience! Formatting a /data partition to ext4 can last a long, long time. People reportet as much as 90 min. In my case it was 30 min. So, be patient!
Click to expand...
Click to collapse
Thanks it worked!!! thank you very much
The file system is now on ext4 but whenever I try to flash it to f2fs it gives me:
Unknown mtp message type 1
And then its unable to format to f2fs.
supernova0 said:
Thanks it worked!!! thank you very much
The file system is now on ext4 but whenever I try to flash it to f2fs it gives me:
Unknown mtp message type 1
And then its unable to format to f2fs.
Click to expand...
Click to collapse
1. You reasonably can only format /data with f2fs
2. Reliable formatting f2fs is possible with newest TWRP 2.8.5.0; Goto tab 'Wipe'=> check only /data=>Change File System=>check f2fs
3. Depending on what ROM you are actually, there might be a command 'mkfs.f2fs' in /system/bin; you can format manually by opening Terminal Emulator typing:
Code:
su [enter]
mkfs.f2fs /dev/block/mmcblk0p8 [enter]
be carefully, what you type! Mistyping can render your tab bricked.
das chaos said:
1. You reasonably can only format /data with f2fs
2. Reliable formatting f2fs is possible with newest TWRP 2.8.5.0; Goto tab 'Wipe'=> check only /data=>Change File System=>check f2fs
3. Depending on what ROM you are actually, there might be a command 'mkfs.f2fs' in /system/bin; you can format manually by opening Terminal Emulator typing:
Code:
su [enter]
mkfs.f2fs /dev/block/mmcblk0p8 [enter]
be carefully, what you type! Mistyping can render your tab bricked.
Click to expand...
Click to collapse
Ok, I found myself here as well. I recovered and have KatKiss 5.0.2 #18 installed and running. I do have TWRP 2.8.5 and it will not convert my /data to f2fs with the same error above. It worked once but then I got hungup on a Google restore and it corrupted everything forcing me to Asus restore. This ROM doesn't have mkfs.f2fs.
How else can I convert to f2fs? Is there another way to do this via ADB or getting the mkfs.f2fs command to drop in /system/bin/?
Thanks--
bretzke said:
Ok, I found myself here as well. I recovered and have KatKiss 5.0.2 #18 installed and running. I do have TWRP 2.8.5 and it will not convert my /data to f2fs with the same error above. It worked once but then I got hungup on a Google restore and it corrupted everything forcing me to Asus restore. This ROM doesn't have mkfs.f2fs.
How else can I convert to f2fs? Is there another way to do this via ADB or getting the mkfs.f2fs command to drop in /system/bin/?
Thanks--
Click to expand...
Click to collapse
Try that mkfs.f2fs command from recovery in a shell from a PC
Or after it fails pull a recovery log .....
Code:
adb pull /tmp/recovery.log
paste it on pastebin or upload it to xda .....
Thx Josh
lj50036 said:
Try that mkfs.f2fs command from recovery in a shell from a PC
Or after it fails pull a recovery log .....
Code:
adb pull /tmp/recovery.log
paste it on pastebin or upload it to xda .....
Thx Josh
Click to expand...
Click to collapse
Thanks for helping...here's the log: http://pastebin.com/Fr5q88PH
Here is the error:
Formatting Data using mkfs.f2fs...
mkfs.f2fs: invalid option -- r
I:mkfs.f2fs -t 1 -r 16384 /dev/block/mmcblk0p8 process ended with ERROR=1
bretzke said:
Thanks for helping...here's the log: http://pastebin.com/Fr5q88PH
Here is the error:
Formatting Data using mkfs.f2fs...
mkfs.f2fs: invalid option -- r
I:mkfs.f2fs -t 1 -r 16384 /dev/block/mmcblk0p8 process ended with ERROR=1
Click to expand...
Click to collapse
Thanks for your assistance Josh. It turns out 2.8.5 has a bug for f2fs conversion on many/most devices. Loaded 2.8.4 and it worked perfectly.
bretzke said:
Thanks for your assistance Josh. It turns out 2.8.5 has a bug for f2fs conversion on many/most devices. Loaded 2.8.4 and it worked perfectly.
Click to expand...
Click to collapse
See you found your own answer and I like that ..... :good:
Thx Josh

Data partition shows 0mb. Help.

I flashed a stock rom (replaced the stock recovery with twrp though), it was stuck at the Alcatel screen, so I went into twrp. I tried reparing, resizing, changing file system of data, system, and cache (which all showed 0 mb), then cache and system got fixed and it said ext4. However, data still shows 0 mb and despite trying all kinds of fixes (like wiping, doing a factory reset, changing file system to ext2, ext3, ext4, fat etc. which all fail) I found online it's still the same. When I tried flashing userdata using SP Flash Tool, it said "not enough space". I found two scatter files (attached to this post) but they seem to differ.
What should I do?
Hint: Add TWRP to this thread's title because it's a TRWP related issue.
jwoegerbauer said:
Hint: Add TWRP to this thread's title because it's a TRWP related issue.
Click to expand...
Click to collapse
How is it TWRP related? SP Flash Tool says it can't flash user data because there is no space because /data is seen as a 0mb partition.
tesiz22 said:
How is it TWRP related? SP Flash Tool says it can't flash user data because there is no space because /data is seen as a 0mb partition.
Click to expand...
Click to collapse
My guess is /data got encrypted by TWRP, hence it actually can't get mounted. But I may err ...
jwoegerbauer said:
My guess is /data got encrypted by TWRP, hence it actually can't get mounted. But I may err ...
Click to expand...
Click to collapse
That makes sense, I'll try adding the tag. Do you have any idea how I can check that or decrypt the partition? It looks like not only data but many other partitions aren't visible as well like /system.
...
It looks like I can't edit tags afterwards.
Looks like there's a problem with userdata
You have to format it, and then reflash the stock rom
Open sp flash tool
Load your scatter file
Go to the format section at the top of spflash tool
Select manual format flash
Select emmc user.
As the begin address of userdata is
0xABD80000
Input it in begin address box
As the size of userdata is
0x124D80000
Input this is the format length box
Click start
Flash the stock rom and reboot
I got these values form your scatter file
Tab E said:
Looks like there's a problem with userdata
You have to format it, and then reflash the stock rom
Open sp flash tool
Load your scatter file
Go to the format section at the top of spflash tool
Select manual format flash
Select emmc user.
As the begin address of userdata is
0xABD80000
Input it in begin address box
As the size of userdata is
0x124D80000
Input this is the format length box
Click start
Flash the stock rom and reboot
I got these values form your scatter file
Click to expand...
Click to collapse
Thank you! Which scatter did you use? I uploaded two different ones for the same device but I used the one named "mt8127_android_scatter.txt" to flash the stock rom.
tesiz22 said:
Thank you! Which scatter did you use? I uploaded two different ones for the same device but I used the one named "mt8127_android_scatter.txt" to flash the stock rom.
Click to expand...
Click to collapse
I got the begin address and format length from Mt8127

Categories

Resources