Hello guys,
because of the fact that nandroid isn't available for the Ray till now I tested another way to make an image of the device.
I used YaffsExpert (available on market) to create an image of the userdata-partition. To verify that everything is fine I unpacked this image on pc with unyaffs.exe => All files were there except 3 but which are everytime created when the phone reboots (files under /data/idd for example).
I then flashed this image with
fastboot flash userdata userdata.img
Everything went fine... but after that, rebooting did take much longer than usual and I was afraight I "bricked" the device. After some time it booted through and was running, but started with the setup-assistant.
So the device just behaves like I did an factory reset... Any ideas why MY userdata-image had'nt been restored correctly?
I'm really thankful for any help!
Greets,
Touch2er
i think it started late because it generates cache .
Related
Hello,
I just got my new phone, and are desperately trying to install a MIUI ROM (which i've used for about a year on my old HD2).
I own a XT910 GSM (UMTS) version, loaded with SPDREM_U_01.6.7.2-180_SPU-19-TA-11.6_SIGNEuropeAustraliaEMEA_USASPDRICSRTFR_HWp2b_Service1FF_fastboot firmware (french)
Now my problem is that i cannot get Bootstrap nor RazrTouchBlack CWM recovery to work.
I always end up with a black screen after the first boot logo.
After having tried mattlgroeff's Droid Utility 1.82 for rooting, i tried RazrTouchBlack 5.8.4.5. After initial boot logo, i endup with a black screen. I've tried getting into recovery a couple of times without success.
After a while, i decided to fully reinstalled my phone with RSDLite 6.1.4 (version stated above).
I then tried rooting my phone with EPRJ_EasyRootICS_MultiOS_v1.5, and installed RazrBootStrap.apk. After initial boot logo, i endup with a black screen. I've also tried RazrBootStrap a couple of times, and RazrTouchBlack... without succes.
I read about Boot Manager but it seems it's really buggy with MIUI as for know.
Well, i don't really know what i'm doing wrong, i'm used to flash HTC / samsung devices... This is my first MOTOROLA but i don't think get the error.
Can anyone bring light on my problem ?
Thanks
EDIT: I also tried RazrICSBootStrap.apk... Same results.
Well... found the problem:
I've also played with boot menu manager 0.27. Told me " you don't have enough free space on /preinstall "
So i looked into /preinstall with "super manager" file manager, with root access, and show hidden files option.
I've deleted everything in that folder and tried boot menu again. Works !
After this, i've fully reinstalled my phone with RDS lite, then emptied the /preinstall folder again, installed ClockWorkMod Recovery 5.8.4.5... With SUCCESS !
Yeah. /preinstall folder seemed to make trouble, and doesn't get emptied even after a full wipe and RDS lite stock firmware reinstall...
Hopefully this might help out people in the same case.
Hey. Been lurking this forum since before i got my NOTE.
ran it stock for a bit noticed issues.
Rooted thru Odin3 V1.85 (DA_G + zaptor99 's methods)
things worked ok cept for streaming video online (not youtube)
in an attempt to freeze my social hub and answering machine notification (its disabled on bell's side but i still have a notification that won't go away)
I assume i button mashed or did something wrong went i went to freeze those apps.
the note acted like it crashed, slowed the hell down and froze.
upon restart, i get past the first samsung screen, into the second that also has the model number in is (in my case SGH-i717M)
this is where the phone get stuck up on now.
Useful info:??
I can get into Download mode. I can get into TeamWin Recovery.
But the phone doesn't seem to get recognized by Odin3 anymore (v1.85 or v3.04 )
So would there be a way to restore thru Teamwin's recovery by using my SD card and loading it with the required files?
or do i have a brick on my hands?
thanks in advance for any help whatsoever!
It sounds as if you have frozen your launcher, and of course this means the device wont boot past the splash screen.
If you have a nandroid backup of the rom prior to the freeze, you can push that image back to the device using recovery. (wipe first)
You can also push the exact same rom image you are currently using, (rom image only) to the device via recovery, and correct the issue as well. (full wipe)
Either way, fully wiping the device before a nandroid restore, or fresh rom install is always a good idea.
You are very far from bricked...
Good luck....g
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...
Hello, XDA forumites!
I've been lurking and reading a lot of threads in here for years, using all your knowledge to fix various phones. Today though is the day I first post and it is for good reason. I'm a guy who loves challenges but this one is making me go insane. I've spend the last two days looking for ways to fix this phone but NOTHING works.
So, the deal is that this phone turns on fine. It boots, it gets to the lockscreen and... it restarts itself. Again and again and again until the battery is removed. To fix it, I've tried the following:
- recovering/updating it through the Huawei official "firmware" supplied by the site: you put the file they supply on an SD card, inside a folder named "dload" and then hold vol up and down along with the power button to make the phone install the contents of that file, named UPDATE.APP. Needless to say it doesn't work. A menu appears with the options reboot system now, apply update from sdcard, apply update from cache, wipe/data factory reset, wipe cache partition and calibrate touch screen. Trying to apply update from sdcard only lets me browse the SD looking for the file but doesn't actually see the file itself, it just shows the dload folder empty (I've tried with 4 different versions of the file compatible with phones from Central America which is where I am ATM). Also, the factory reset does nothing (although it shows it wipes data), everything's there when I start the phone up.
- flashing it with SD Flash Tool: apparently partially works with the last version 3 of the tool (although nothing changes) while version 5 of SDFT doesn't even see the phone (drivers are correctly installed, adb detects it, more on this later). A problem that arises is that I can't flash the SEC_RO package on it (don't know why) nor the PRELOADER (not that one is supposed to normally, but I feel like it would fix my problem in this case).
- cleaning it in safe mode: booting it in safe mode made me notice that it was an app pretending to be Whatsapp causing the restarts (or, perhaps, the one that loads immediately after? The phone has several malware apps). In safe mode those apps didn't load so the phone stayed on. So I cleaned everything, activated USB debugging (for later use in adb mode) and restarted only to find everything as it was before I did the cleanup. I tried rooting it in safemode, cleaning again, still reverts to full "normality" after the restart. Same results when using the phone's proprietary SW HiSuite.
- installing CWM's recovery img through adb+fastboot: I installed all the possible - necessary or unnecessary - drivers (Google's, phone's official ones, PDANet ones) and the phone is correctly detected by the PC (visible in Device Manager) and is visible through the adb devices command. But as soon as I adb reboot bootloader it to fastload the CWM image, the phone stops being seen correctly and doesn't show up in fastboot devices, only showing "NEW: SAFE OLD:RISK" on a black background on its screen.
So, to recap: the phone restarts because of a malware at startup, reverts any and all changes made to it in safemode, doesn't wipe from the recovery menu, apparently has a corrupted bootloader and is impervious to normal flashing SW... Anyone got any more ideas on how to deal with it? The only option left that comes to mind is to fix it directly by flashing the internal memory using JTAG/RIFF but I don't have the equipment (nor do I intend to buy it).
Bump, hoping for some help...
One more bump, still stuck
First, don't get happy: I have no answer to your problem. Sorry. But I have a similar one. I was running a very efficient, rooted, stock ROM G730-U251, until I decided to switch from 'Ninjamorph Free' to 'Pro'. I've been made a lot of changes with Free version for a long time without any issues at all. Then, one day, when making a small, useless change with 'Pro', something went wrong; phone just rebooted and refused to get past bootanimation. With no custom recovery on hand, only solution for this is to flash ROM. Though I had no problem finding the official, stock UPDATE.APP, which flashed smoothly from the SD card to be fair. Mess came when, once flashed, I decided to install OTA update available, which I overlooked since phone was new. Big, BIG mistake. It just came with more restrictions than ever, letting me root, yes, but this time with 'Kingroot' only (as stock, I had no problem rooting with Framaroot) but soon discovered I wasn't able to use 'Super-Sume', 'Adaway' and 'Link2SD', because some system parts now CAN'T be mounted rw, even using ES File Explorer. To avoid any complication, decided to reflash UPDATE.APP just as I did before. No way I can do it this time. Don't know exactly why, but assuming it's not possible to update with a previous version of the 'same' ROM. So now I'm looking for a flashable stock ROM in order to try SP flash tool. Phone is in working state right now (not as yours), but I just don't feel comfortable with it as it is right now, because those apps are always the main reason why I actually root every single of my devices and simply because I like to have my stuff as my own way as possible. You know, truth is there's not much of an advanced support for this phone, not even here at XDA and I think that's because this is a Latin America version. We owners of G730-U251 devices are pretty much on our own, to say the least. Whatever, if the whole deal gets more complicated than it is, there's a strong possibility for me to end up getting rid of this phone. Sad. Really. It's actually a good phone. Though it WAS better...
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