My A830K has got its /data partition corrupted. I need your help to restore my phone.
Phone can go to recovery but shows various error in mounting /cache partition
Phone can go into download mode
I have tried online as well as offline update of stock ROM but it doesn't work.
OEM unlock work to the extent of selecting YES but after that phone restarts and nothings happens.
I have tried to delete and recreate the partition but it doesn't work (might be the OEM unlock coming into play)
My phoen is just sitting there since 3 weeks and I cannot restore it. Please Help!!!
PS: I tried posting in the general thread of A830 but did not get any reply.
Bumped
glance00 said:
My A830K has got its /data partition corrupted. I need your help to restore my phone.
Phone can go to recovery but shows various error in mounting /cache partition
Phone can go into download mode
I have tried online as well as offline update of stock ROM but it doesn't work.
OEM unlock work to the extent of selecting YES but after that phone restarts and nothings happens.
I have tried to delete and recreate the partition but it doesn't work (might be the OEM unlock coming into play)
My phoen is just sitting there since 3 weeks and I cannot restore it. Please Help!!!
PS: I tried posting in the general thread of A830 but did not get any reply.
Click to expand...
Click to collapse
BUMMER
Related
Hi!
I try to tell my lovely story, let's hope someone can help me, because i am in a huge trouble.
Today i installed WIFIunlocker on my device, and unfortunately, i gave access to the device administrator right to the application, plus i set up a password. Using the app i realised this is not that iam looking for, so i decided to remove it. Tryed to uninstall it, but for the first try i got an error, later on i realised that i need to turn off the device administrator mode inside the app, everything is fine, i was able to unintall it. Now the nightmare starts...
After uninstalling the app, locking the screen then unlocking the phone, it asks for password. I was a bit surprised because i just removed the related app. Nvm, i just entered my "password", but it was wrong. Before the uninstall it worked, now, after the uninstall it doesn't. At this point i can't do anything with the phone, because iam stucked on the "password screen".
What i did today:
- started from Litening rom v2.0
- i was hopeless, so wiped data/factory reset, wiped cache + darvik cache, formated system+data+cache
- installed LeoMar v2.5
- After the boot the it still asked for the password, i removed the sim-card, and somehow was able to access the phone, but unfortunately it locked itself, the "password screen" popped up again.
- My last try was flashing stock KG6 rom then later on CF-Root, but now i can't boot the phone into recovery mode. Download still works.
- What happends when i try to boot it to recovery, the Samsung Galaxy S 2 title shows up, but after that immediately asking for the "password". Before this, the phone booted fully / i was able the access the recovery mode.
So my question is, what can i do now? How can i get rid of this "password screen?"
Youtube video
Same problem
But I switched off administrator mode before uninstalled
and i used only one password so it can not be wrong.
I think that the app is a joke or a prank?
DID you managed to fix that?
Well I managed to make my phone the same brick as yours.
What now.
Did g4rb4g3 = Garbage did in purpose?
I think using download mode to restore your efs partition backup will fix this since password and pin info is saved on it.
Volume DOWN + Home + Power.
Do you have a custom recovery?
Wipe everything. All of it. Flash a new rom. How the hell is this impossible to remove? Flashing a rom wipes all crap right? Wth..
---
Edit: Seems the app is known for this bug with many others. Mods should take the app down, it's killing devices, turning them unusable. If the dev can reproduce the problem or if someone smart enough could come up with a fix..
prodygee said:
Volume DOWN + Home + Power.
Do you have a custom recovery?
Wipe everything. All of it. Flash a new rom. How the hell is this impossible to remove? Flashing a rom wipes all crap right? Wth..
Click to expand...
Click to collapse
Wrong the password/pin is on the efs partition which is NEVER touched during flashes or wipes.
Or flash a AOSP rom like cm7 or MIUI since they don't use the efs partition for lock settings.
ANd i fixed it again from the brick
Just go to download mode
flush it with stock
after restart try to go to recovery it will ask you about the password
type anything as many timea as it will tell you that if you will try again it will wipe out your internall sd card
of course try once more it will wipe out your sd card and ask you again for password
type anything again and again and it will warn you again that if you try again it will wipe the internal sd card and after that you will see red info that your pass was changed to NULL
restart
and you are in and all is back to normall
mahatma said:
Well I managed to make my phone the same brick as yours.
What now.
Did g4rb4g3 = Garbage did in purpose?
Click to expand...
Click to collapse
You can blame him same as yourself. This story shows that you need to be really careful when you mess with your phone. This true from the developer side and from the user side. At least we have some information about this for the future and we can help people out.
Hello, after playing with a tablet I got boot loop so below is solution for this.
This is what I wrote first:
I purchased Chinese tablet called CyberNav, there is link to the website with specs http://www.dracotek.com/cybernav-7-...ps-navigator-ultra-slim-wifi-8gb-gps70yw.html It works great and is worth the money. I received- on request- firmware for it, but it is with .img extension and I have no idea how to get to the files. Attached application PhoenixCard should install it on sd card but it does nothing. So there is my question- can anyone help me with it? Possibly root it? Or update to newer firmware version? I'll post a link to, just need to upload it to my dropbox on my next break at work.
Sek
im pretty sure you need a 3rd party application to flash that firmware, i think you load the .img file into the software on your pc, connect tablet in flash/recovery mode then flash it that way, dont know which software you would need to use though , sorry i cant help further
There is link to rar package http://db.tt/jm7eHfbq
If there is someone who wants to spend some time... Please help.
Bump
Some new infos:
As far I found out tablet is detectable during boot in adb, but it stays in boot loop. I think I've got right usb drivers.
I tried unyaffs the .img file using C:/unyaffs/unyaffs pw08.img but it shows file corrupted (might be wrong method?).
Logcat attached.
Maybe there is someone who will find what it's missing...
I see there is nobody who can help me, so... If some of u have similar problem with chinese tablet- bootloop, can't flash it with LiveSuit our update from sdcard, I found solution which worked for me. Using adb, pulled catalog /dev/data/ to hard disk, then deleted all dalvik cache, installed by me apps and almost every other file from /data on my hard disk. Then typed adb remount, then adb shell rm -r /dev/data/* to delete all data catalog on tablet. Then pushed /data catalog from my hard disk to tablet, and finally adb reboot. And it WORKS! Booting without problems. I wasted 4 days on research how to turn it in flash mode etc. But it was very simple.
Cheers
Sek
Hi, sek111
It was necessary to use the LiveSuite to flash through usb.
Thank you very much, from your post, I found the firmware for my tablet.
An experience with another low cost tablet with Bootloop
I happen to got my tab (Wammy from WickedLeak.org) stuck in BootLoop and was struggling to get a way out for the past 3 days, checking almost all of the posts for this issue!
The tab would stuck on the android loading animation despite running for 2-3 hours and after several hard reboots, it throw-ed following error-
Encryption Unsuccessful
encrytion was interupted and cant complete. as a result the data on your tablet is no longer accessible
to resume using your tablet, you must perform a factory reset. when you set up your tab after the reset, u'll hav an opportunity to restore any data that was backed up to ur google account
Click to expand...
Click to collapse
Despite going for the factory reset, it still didn't workout as the reset activity never completed or proceeded. I happen to be a beginner/noob and was trying my luck with possible solution but was comfortable with ADB stuff and workaround. Well i checked the solution which sek111 offered in this post and it was most closely helped me out. So i would like to Thank him a ton for sharing his solution.
Another method for few others if you don't get through the technical stuff and handling all the flashing tools, i was successful in bringing up the setting window of my tab and chose to do Reset via GUI which worked. Actually my battery got drained out to 7% and a popup message for same displayed while i was on the above error page. I selected the "check battery" option from that pop up and got my way out via factory "Backup and Reset" option under settings.
I hope this might help few people if not all! But the XDA forum is great and everyone will find a solution here. Cheers!!!
So I got this wm8850 chinese generic tablet. The camera is in the front in the middle (wide). It was shipped to me with 4.0.3 in boot loop. I soon found out that it boots into safe mode when I usb to pc. This is the furthest I've gotten with it so far. I can adb into it and have already tried to wipe data. It seems like since its from factory screwed up that a may need to reload the firmware or the os or something. Im kind of a noob because I only have my droid x. I've gotten it out of a boot loop before but I also knew what I had done to cause it so I fixed it. I tried to follow seks adb commands but im too noob to do it I guess. I was able to wipe data and dalvik-cache. Issue still occurs . If anybody can give me some adb commands than can help I would greatly appreciate it. Im fairly sure that I found the firmware elsewhere on xda. I thank you guys for any help at all you can give. I don't wanna send it back without trying everything software related as I can, but ill send it back if I can't fix it or if I brick it
Sent from my DROIDX using xda app-developers app
i have same problem in my china mobile.. dupad k1 ... after in installed new boot screen, device stuck in boot... please help to recover my device in step by step....
Hello,
i have a strange problem with my FireHDX 7.
Tablet will load the boot image then after a few seconds reboots.
It happened on CM 13.1 (i have unlocked bootloader).
I tried everything put on Stock Recovery. Factory Reset. Put on CM 12.1,
put on Stock Amzazon.
No matter what after a few seconds tablet always reboots again.
In TWRP i can see /data having errors. That i can fix with format data.
Once i flash ROM again same loop happens again.
What can that be, faulty emmc? Is there any chance of fixing it?
Unfort. it happened 6 days after the 1 year amazon garantee ran out...
Thanks for any help
andPS2 said:
Hello,
i have a strange problem with my FireHDX 7.
Tablet will load the boot image then after a few seconds reboots.
It happened on CM 13.1 (i have unlocked bootloader).
I tried everything put on Stock Recovery. Factory Reset. Put on CM 12.1,
put on Stock Amzazon.
No matter what after a few seconds tablet always reboots again.
In TWRP i can see /data having errors. That i can fix with format data.
Once i flash ROM again same loop happens again.
What can that be, faulty emmc? Is there any chance of fixing it?
Unfort. it happened 6 days after the 1 year amazon garantee ran out...
Thanks for any help
Click to expand...
Click to collapse
No need to double post. Regular HDX contributors will have seen your issue in the development thread. Well...at least those with some knowledge of your hardware. Unfortunately, there's not a lot of commonality with other android devices. Tough to get help elsewhere. Sorry this happened to you.
thanks for the answer
well i guess i have a device that could be used for some research now
i turned it off and can charge it
anything can be tried in fastboot mode or TWRP mode or stock recovery mode
anyone wants to try out something?
p.s. i still dont understand how it can work in TWRP mode and fastboot without rebooting
but crashes or reboots when any image is loaded
andPS2 said:
thanks for the answer
well i guess i have a device that could be used for some research now
i turned it off and can charge it
anything can be tried in fastboot mode or TWRP mode or stock recovery mode
anyone wants to try out something?
p.s. i still dont understand how it can work in TWRP mode and fastboot without rebooting
but crashes or reboots when any image is loaded
Click to expand...
Click to collapse
TWRP operates (loads) from the recovery portion. The symptoms suggest damage to another partition. The reboot likely occurs when a write operation fails or attempts to put data in a protected area. With a second (working/unlocked) device you might be able to compare storage layouts, determine differences and take corrective action...assuming it is not a HW issue. I realize that's unlikely to happen. Not even sure what to look for and the commands needed to reveal low level storage/partition details.
There is no low-level formatting available for HDX.
Since you have an error with /data there is a good reason to check this partition.
Load into TWRP recovery, attach the tablet to a PC with ADB and driver installed, unmount the data using the interface, launch the adb shell,
then try e2fsck -fpv /dev/block/platform/msm_sdcc.1/by-name/userdata
However I'm not sure that any issues with /data can cause the reboots.
Check the system partition too.
On my device Wi-Fi can't be turned on, this can be NAND issues.
thanks for the help
i can try on monday since my half brick fire hdx is at work
merry x-mas !
p.s.
checking the filesystem for userdata and system indeed showed no errors
still have the reboot problem
guess it is a nand problem then...
I have a samsung galaxy k zoom, actually its my friend's phone. Few days ago he stuck on samsung logo and he went to a mobile shop. I dont know what he did, he just erased everthing, now when i try to flash any firmware or recovery, i got red line saying that ( unable to mount sys partition, E: cant mount sys partition). Is there any way to fix this
No response from adb before/during/after all this? If I get time off from battling kernel_restart_prepare I can look but there used to be a complete K Zoom M mod/port. I guess you could try that? If all else fails they (most phones) are supposed to try to boot from the sdcard, right? Put Ubuntu on there or something...gotta find some way to run fsck/examine the drive. Bet it isn't hosed, just wrong permissions/wrong kernel/wrong timestamp or something like that....
Yes no responce from adb, and i will try that
Good morning, everyone.
I have been frequenting this forum since the days when I had my trusty and beautiful HTC m8.
I find myself writing this post today looking for help: my uncle received from his friend a Doodgee x93 phone that was locked and whose unlock code he couldn't remember.
So I thought it would be simple, flash the ROM again so as to erase all the old data and reset the phone.
However, I found myself unable to do so.
After installing several versions of the drivers, in the various attempts, I used "SP_Flash_Tool_v5.1924_Win" with the only two firmwares available (any site always links to the exact same downloads) "Doogee_X93_MT6580_EEA_210902_10.zipper" and "DOOGEE-X93-Android10.0-20210902_user_20210902_R16.zipper".
The process stops at 2% without any error description.
In addition, the phone remains unusable, the screen does not turn on, and I cannot start recovery.
I then tried installing each file individually, and they all work except "super.img", which I assume are the android files given the weight of the 1.8Gb file.
Here I was able to turn it on, it did the boot android logo, then went to ">start fast boot.." but it never booted, surely because it couldn't find the rest of the files.
From the "MT6580_Android_scatter.txt" file, I tried editing the following.
"boundary_check: false" to true, but always to no avail.
I attach a screenshot and ask for your help, because I don't know how to proceed anymore, and all the online guides are the same copy/paste that don't work.
Thank you in advance
so you got a working phone and you bricked without doing research how to factory reset + reset FRP
Error: 3154 (S_DA_SDMMC_WRITE_FAILED) indicates flash storage wear-out.
you can however try another tool. do a full backup of all partitions first (especially partitions not included in stock ROM)
https://github.com/bkerler/mtkclient
I thank you for responding, I have downloaded and set up everything, as soon as I have a moment I will try to use the software you linked.
The phone worked, but it was locked as the owner, a friend of my uncle who gave it to him, had changed it long ago and could not remember the code to unlock it.
It was not a problem to reset it as he had already taken out his things before changing it.
However, I actually looked at several guides and followed every step, I didn't make anything up.
It had been several years since I had last done it, it seemed very similar to when using odin, and I went easy.
I can see in your screenshot you haven't unticked checkbox preloader. therefore I doubt you found the right tutorial. All it needs is formatting userdata and erase metadata + frp partitions.
https://www.hovatek.com/forum/thread-21638.html
some more information about Secure Boot Download Agents and why one must not flash in Format all + Download mode
https://www.hovatek.com/blog/so-whats-all-this-talk-about-meditek-secure-boot-and-da-files
similar thread
https://forum.xda-developers.com/t/frp-protection-on-doogee-s96-pro-who-has-tips.4418737
In the next few days I will have time to put in and try.
I have read the documentation, but I have a doubt: should I flash all *.img files, or just "super.img" which I failed with "SP Flash Tool"?
Or is there a command I haven't seen that automatically uses the "Android_scatter" file?
mtkclient don't use scatter file, it reads partition table on device. you can flash only super.img based on partition label.
Code:
python3 mtk w super super.img
Thanks for all the reply!
Im gonna watch all your link and in the next days let you know if it works! Meanwhile i wish you a good evening