Database Develop

[Q] Atrix HD Corrupted Data partition

I'm a newb..
Atrix HD with unlocked bootloader and rooted. Installed cwm recovery, flashed to the latest nightly cm 11 for atrix hd, rebooted and stuck at cyanogenmod loading screen (head with the spinning circle around it). left it that way over night with no change still stuck on bott.
I've spent several hours following several guides with no success
I think the problem started whn I did a factory reset and clear cache in cwm before I flashed cm 11. it gave an error on data or something.
fastforward several hours later I now have philz touch 6 recovery which I read on this guide http://forum.xda-developers.com/showthread.php?t=2577447 you could use to fix the corrupted data partition. problem is when booted to philz recovery the driver for phone is not installed correctly.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
The phone is recognized fine in fastboot mode however.
Is there a way to fix the corrupted data partition using fastboot?
I've already tried fastboot -w and reflashing but that did not work.
I have the latest motorola drivers and latest sdk with google usb installed etc.
Unfortunately I was stupid and didn't make a nandroid backup so I hope there is another way to get this phone working.
thanks

Solved
After 2 days of monkeying around I finally got it fixed.
I never could get the phone recognized in recovery mode (philz mod) and using ADB as suggested by the guide I linked.
Finally what worked is I downloaded the stock rom zip, extracted it, edited the xml file in MS word deleting the 2 lines with "getvar" in them, booted the phone into fastboot mode, connected the phone to my PC and made sure it was recognized in device manager, loaded the xml from the stock rom into RSD Lite and flashed back to stock, rebooted, and all was working fine.
I know there's a million and 1 guides that say to do what I just described and believe me I tried the exact things I posted above for the better part of 2 days and rsd lite would always fail with some kind of error. Finally I rebooted my PC, downloaded the stock rom again, edited the xml, and tried one last time and it finally worked...I don't know what made the difference.
Now if I could just find a trick around this darn subsidy (hard) lock this Atrix HD would be back in business.

Cant oem unlock my nexus 6

So before I start I just wanted to say that I have been rooting and installing roms back at the time when I had my galaxy s3, I knew this stuff before upgrading to my nexus 6.
So the problem as you can see on the title that I cant unlock the oem option, means I cant unlock my bootloader, but there is a twist.
When I bought my nexus, I remember it was 5.0, and there was an update to 5.1, the update was OTA, and I remember the update had problems, it couldn't finish and the phone stayed on 5.0 and you could not
update to 5.1 unless you flash 5.0 again. So I unlocked my bootloader back at the time, and installed 5.0 all over again, and everthing was fine until now(now I am on 7.0)
Now I want to root my phone and install things and I cant do that, because of the oem options, but when i go into fastboot it says device is unlocked, and when I turn my phone on under the google sign there is small open lock sign that I know tells the bootloader is unlocked.
So there is my problem, I cant root it and so on, very sorry of the long post but I think it was necessary so I could explaine my problem.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Not quite sure what your problem is. Your bootloader is already unlocked, you just flash twrp via faatboot
Code:
faatboot flash recovery nameoffile.img
then flash SuperSU. If it asks for a password, or you can't find any files on your device in twrp, that means you're encrypted, and will have to completely wipe data on device. You do that by hitting cancel (if it's asking for a password) then go to wipe. Then select format. You'll have to type yes. Now you'll be unencrypted.
As a side note, you may be able to get away with just flashing twrp, and then sideloading the SuperSU zip

dictionary said:
Not quite sure what your problem is. Your bootloader is already unlocked, you just flash twrp via faatboot
Code:
faatboot flash recovery nameoffile.img
then flash SuperSU. If it asks for a password, or you can't find any files on your device in twrp, that means you're encrypted, and will have to completely wipe data on device. You do that by hitting cancel (if it's asking for a password) then go to wipe. Then select format. You'll have to type yes. Now you'll be unencrypted.
As a side note, you may be able to get away with just flashing twrp, and then sideloading the SuperSU zip
Click to expand...
Click to collapse
Thank you very much, apparently it worked even if the oem option is not available, hope I wont get into more troubles.

Encription error, unable to start

I have a note 8, after the samsung logo it appears this message and i can't do anything; all i can do is to reset the phone, and even if i do it the message is still there.
I also tried to wipe data and cache from recovery but without results; and i also tried to flash the stock firmware many times with odine but it didn't work.
Are there any other ways that i can try to fix this terrible problem?
Thanks in advance.

elettrbel said:
I have a note 8, after the samsung logo it appears this message and i can't do anything; all i can do is to reset the phone, and even if i do it the message is still there.
I also tried to wipe data and cache from recovery but without results; and i also tried to flash the stock firmware many times with odine but it didn't work.
Are there any other ways that i can try to fix this terrible problem?
Thanks in advance.
Click to expand...
Click to collapse
Upload a photo of the error

I don't have the access of the phone now, but this is the error showed on my note 8.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

maybe try reflash with a different version of odin but maybe also try from a pc to access your accounts and do resets from there first

elettrbel said:
I don't have the access of the phone now, but this is the error showed on my note 8.
Click to expand...
Click to collapse
Never seen this before. Take it to Samsung ??

https://www.youtube.com/watch?v=ApSzrfckUUY
This is for S7 Edge but should be same for note 8, except for the files which you MUST download for your note 8.
make sure u download the correct firmware and select it in correct places on ODIN

vash_h said:
https://www.youtube.com/watch?v=ApSzrfckUUY
This is for S7 Edge but should be same for note 8, except for the files which you MUST download for your note 8.
make sure u download the correct firmware and select it in correct places on ODIN
Click to expand...
Click to collapse
Yeah this was the video that i followed without solve it.

I got a Solution!
1.Download latest dm-varity..
2.Go into TWRP and Format data "Type yes"
3.Reboot Recovery
4.Flash DM-varity and Reboot Recovery.
5.Now wipe all Partition
6.Boot Download Mode
7.Flash BQKG firmware!
8. Habe fun! Now you can inStall any Rom

Boot Freeze - Magisk Ver 20.00 for Samsung Galaxy S10+ (SM-G9750) Snapdragon

I used Magisk Manager 7.3.4 and patched a firmware (AP G9750ZHU2ASIK) for my Samsung 10+ (SM-G9750) and flashed it by Odin to my device but it only cuz it a bootfreze.
Yes I went the right way.... in the Dev options I set OEM unlock. Than I went to the Download Mod and pressed vollume up for 7 sec. I confirmed the bootloader unlock with vollume up again, and it booted into recovery and erased everything. I booted back to the Download mod and flasched the patched firmware with auto reboot option off in odin app. After passing successfully flashing, I turned the phone of and try to boot into recovery by using power + vollume up and bixby key, but it ends up with the black samsung screen freezed. No matter how often I try again to reboot normal or reboot into recovery, it doesnt change anything.
And yes I say that this is a bug in Magisk 20.0
because I also found an older patched firmware that I patched previously a few weeks ago. And I tried this one. No problem. I could boot into recovery to fullwiping and I was able to boot into system with Magisik root. But this older patched firmware has Magisik 19.
Once I open Magisk Manager than, and start updating to Magisk 20.0, it ends up with the same boot freez.
here is a picture with the freezed screen
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
h t t p s: / / img1.img1.de/20191015185446219b3.jpg
Its wired that if u look on the picture of the freezed screen that apears. than u can see that it says that OEM Lock is on, but If I open the download mod and have a look there. Than it says that OEM Lock is off. So there is defenetly something wrong with Magisk 20.0 for Samsung Galaxy S10+ (SD)
I beg the Masgik Dev to fix it, cuz I really wanna patch and use a recent firmware.
regards. Jens

Moto G5s Plus Bricked

Here's the background on how it got bricked
i tried unlocking bootloader whcih went succesfully.
then flashed twrp, also succesfully. Could boot into it and the rom
So i started flashing a custom rom without a backup..erased system,cache,dalvik,userdata etc and went into flash rom but it was 64bit rom but my twrp was 32 bit.
i tried installing 64 bit one but phone wont boot into it.
so i decided to flash stock through fastboot
i downloaded a rom which was for moto g5 plus...i didnt realised 5s plus and 5 plus were two different phones...fricked up there
i went to reboot and the phone just went blank, wont display anything,wont boot or any response at all.
but its being recognized as Fastboot Sanders S on my PC and i can access fastboot but phone wont turn on no matter what roam i flash through fastboot.
I was on latest Oreo 8.1 august patch and the flashing goes smoothly, only getting error in bootloader...."security downgrade" stuff
Is there a way i can fix this or is the device just gone?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
[/IMG][/IMG]

dr3mz said:
Here's the background on how it got bricked
i tried unlocking bootloader whcih went succesfully.
then flashed twrp, also succesfully. Could boot into it and the rom
So i started flashing a custom rom without a backup..erased system,cache,dalvik,userdata etc and went into flash rom but it was 64bit rom but my twrp was 32 bit.
i tried installing 64 bit one but phone wont boot into it.
so i decided to flash stock through fastboot
i downloaded a rom which was for moto g5 plus...i didnt realised 5s plus and 5 plus were two different phones...fricked up there
i went to reboot and the phone just went blank, wont display anything,wont boot or any response at all.
but its being recognized as Fastboot Sanders S on my PC and i can access fastboot but phone wont turn on no matter what roam i flash through fastboot.
I was on latest Oreo 8.1 august patch and the flashing goes smoothly, only getting error in bootloader...."security downgrade" stuff
Is there a way i can fix this or is the device just gone?
[/IMG][/IMG]
Click to expand...
Click to collapse
If you got fastboot, then just flash the stock firmware and boot it. Note:- remove bootloader and gpt commands from the fastboot so it won't get brick.