Related
Hello guys, having a bit of a dilemna here as only took the plunge to root today and is my first time in doing so. What I have done is updated to 4.4.2 KitKat OTA and then rooted my moto g. I used the superboot method and got the horrible pink screen and had to manually install supersu, however the device is rooted and obviously the bootloader is unlocked. I then proceeded to put everything back on my phone and then encrypted my phone.
However, I tried to get into recovery (stock) and was fronted with the on its back android with its belly open and red "!" in a triangle. I got this before I even unlocked to bootloader. Anyhow, I wanted to use a custom recovery so I could manage different ROMs in ROM manager etc, so I flashed CWM6046-MotoG44.img (CMW ver. 6.0.4.6) and all was swell.... until i wanted to make a backup.
I did a little searching around and was stumped until I found a post suggesting that CMW couldnt mount storage because the device was encrypted.
What I would like to know if at all possible; what would be the best course of action to take, as im unsure what will/could brick/break my device and as its encrypted I dont think adb commands are pushed as when flashing the recovery image, my device was listed in fastboot devices but not adb devices.
Should I flash a stock image and go from there, put everything back on yada yada yada and NOT encrypt the device, or....
Should I do a factory reset? will this brick my device/lose root access? or will I be able to re root?
I really appreciate any input you guys can give me, and for the meantime im just going to leave my device as it is and not flash anything else,
Many thanks and best regards,
voosh
Anybody have any ideas?
Can anybody help me here. Need to get this sorted so I can flash a custom ROM. Thanks
Bump...................
voosh710 said:
Hello guys, having a bit of a dilemna here as only took the plunge to root today and is my first time in doing so. What I have done is updated to 4.4.2 KitKat OTA and then rooted my moto g. I used the superboot method and got the horrible pink screen and had to manually install supersu, however the device is rooted and obviously the bootloader is unlocked. I then proceeded to put everything back on my phone and then encrypted my phone.
However, I tried to get into recovery (stock) and was fronted with the on its back android with its belly open and red "!" in a triangle. I got this before I even unlocked to bootloader. Anyhow, I wanted to use a custom recovery so I could manage different ROMs in ROM manager etc, so I flashed CWM6046-MotoG44.img (CMW ver. 6.0.4.6) and all was swell.... until i wanted to make a backup.
I did a little searching around and was stumped until I found a post suggesting that CMW couldnt mount storage because the device was encrypted.
What I would like to know if at all possible; what would be the best course of action to take, as im unsure what will/could brick/break my device and as its encrypted I dont think adb commands are pushed as when flashing the recovery image, my device was listed in fastboot devices but not adb devices.
Should I flash a stock image and go from there, put everything back on yada yada yada and NOT encrypt the device, or....
Should I do a factory reset? will this brick my device/lose root access? or will I be able to re root?
I really appreciate any input you guys can give me, and for the meantime im just going to leave my device as it is and not flash anything else,
Many thanks and best regards,
voosh
Click to expand...
Click to collapse
When you get the dead android hold power button for ten seconds then tap the power button,that should get you into stock recovery ,then navigate to wipe data factory reset ,you shouldn't lose root but you will lose da ta and apps
Thanks for the reply but I have already installed the cwm custom recovery. Should I add that I'm still able to access device, my problem mainly is getting rid of encryption as I can't use cwm while device is encrypted and can only do so by factory reset or flashing a stock ROM, but unsure of which option to take. Many thanks and best regards
kieranc88 said:
When you get the dead android hold power button for ten seconds then tap the power button,that should get you into stock recovery ,then navigate to wipe data factory reset ,you shouldn't lose root but you will lose da ta and apps
Click to expand...
Click to collapse
https://docs.google.com/file/d/0B2LP8tI1Xwu4MGtPTlpVcVQxN0k/preview try this cwm it worked for me,I'm not too clued up on encryption but I'm guessing you can't read/write to phones system to easily with it on so I'd guess it conflicts with root
---------- Post added at 06:10 PM ---------- Previous post was at 06:08 PM ----------
kieranc88 said:
When you get the dead android hold power button for ten seconds then tap the power button,that should get you into stock recovery ,then navigate to wipe data factory reset ,you shouldn't lose root but you will lose da ta and apps
Click to expand...
Click to collapse
voosh710 said:
Thanks for the reply but I have already installed the cwm custom recovery. Should I add that I'm still able to access device, my problem mainly is getting rid of encryption as I can't use cwm while device is encrypted and can only do so by factory reset or flashing a stock ROM, but unsure of which option to take. Many thanks and best regards
Click to expand...
Click to collapse
So when you boot to recovery can you access recovery options or do you get dead robot
kieranc88 said:
https://docs.google.com/file/d/0B2LP8tI1Xwu4MGtPTlpVcVQxN0k/preview try this cwm it worked for me,I'm not too clued up on encryption but I'm guessing you can't read/write to phones system to easily with it on so I'd guess it conflicts with root
---------- Post added at 06:10 PM ---------- Previous post was at 06:08 PM ----------
So when you boot to recovery can you access recovery options or do you get dead robot
Click to expand...
Click to collapse
I did get a dead robot. So I flashed CWM custom recovery. I now get the cwm recovery and options, but I can't make a backup becausey filesystem is encrypted, so would like to know the best way to decrypt by means of flashing a new or ROM or simply doing a factory reset within tho phones menus.
Many thanks
voosh710 said:
I did get a dead robot. So I flashed CWM custom recovery. I now get the cwm recovery and options, but I can't make a backup becausey filesystem is encrypted, so would like to know the best way to decrypt by means of flashing a new or ROM or simply doing a factory reset within tho phones menus.
Many thanks
Click to expand...
Click to collapse
OK,you need to boot into cwm and choose the wipe data factory reset option from cwm, I tried to wipe my phone before from the phones menu and because it had a custom recovery it didn't work,but if you boot cwm-wipe data/factory reset it will remove encryption.
Any luck???
kieranc88 said:
Any luck???
Click to expand...
Click to collapse
Sorry, I fell asleep lol was a long day.
Going to try it now and will keep you posted, Cheers.
EDIT - Didnt work - failed to mount storage because "android secure"
Factory reset within the phone also didnt work - The phone reset and the android with the blue thing in its stomach was stuck in a loop, probably because of custom recovery.
Is there a stock recovery I can flash to factory restore the phone?
EDIT 2 - Flashed this recovery - http://forum.xda-developers.com/showthread.php?t=2578243
Now when I boot into recovery it just boots into the phone regularly. When performing a factory reset now the android doesnt even appear and the phone boots regularly again, still encrypted
voosh710 said:
Sorry, I fell asleep lol was a long day.
Going to try it now and will keep you posted, Cheers.
EDIT - Didnt work - failed to mount storage because "android secure"
Factory reset within the phone also didnt work - The phone reset and the android with the blue thing in its stomach was stuck in a loop, probably because of custom recovery.
Is there a stock recovery I can flash to factory restore the phone?
EDIT 2 - Flashed this recovery - http://forum.xda-developers.com/showthread.php?t=2578243
Now when I boot into recovery it just boots into the phone regularly. When performing a factory reset now the android doesnt even appear and the phone boots regularly again, still encrypted
Click to expand...
Click to collapse
I kinda guessed that would happen because its not stock recovery,have u got a us version or international(is it xt1032 or xt1034?
kieranc88 said:
I kinda guessed that would happen because its not stock recovery,have u got a us version or international(is it xt1032 or xt1034?
Click to expand...
Click to collapse
Its a unlocked retail UK version, not sure if its xt1032 or xt1034 because I renamed it to Moto G.
voosh710 said:
Its a unlocked retail UK version, not sure if its xt1032 or xt1034 because I renamed it to Moto G.
Click to expand...
Click to collapse
You've got the same as mine,OK if that didn't work it might be because its jellybean, this is a recovery for the us version but its a KitKat recovery but worst that can happen is it won't boot to recovery, flash it and if doesn't work I'll see can I extract the recovery image from my phone, try it and get back to me asap fastboot flash recovery recovery.IMG
https://www.dropbox.com/s/66br4aiyzipu6x9/recovery.img
kieranc88 said:
You've got the same as mine,OK if that didn't work it might be because its jellybean, this is a recovery for the us version but its a KitKat recovery but worst that can happen is it won't boot to recovery, flash it and if doesn't work I'll see can I extract the recovery image from my phone, try it and get back to me asap fastboot flash recovery recovery.IMG
https://www.dropbox.com/s/66br4aiyzipu6x9/recovery.img
Click to expand...
Click to collapse
Flashed and still boots regularly .
voosh710 said:
Flashed and still boots regularly .
Click to expand...
Click to collapse
In the command line is it saying recovery sent
kieranc88 said:
In the command line is it saying recovery sent
Click to expand...
Click to collapse
Sent and finished ok
voosh710 said:
Sent and finished ok
Click to expand...
Click to collapse
How many times have you flashed it,try flashing two three timees
kieranc88 said:
How many times have you flashed it,try flashing two three timees
Click to expand...
Click to collapse
Actually, looking at the device it says "hab check failed for recovery"
However the other one (jellybean one i think that I linked to) never.
tried flashing 5 or 6 times no luck
Try this link to restore to 4.3 then ota to 4.4 again http://www.modaco.com/topic/366786-how-to-flash-to-the-standard-uk-rom/
Hi, I have a rooted nexus 5 which I want to sell, I really don't mind selling it rooted or not but all I want to do is factory reset it so none of my old data is on there. Can I just factory reset it in settings or Do I need to flash a stock image. It has the stock rom, with Super Su installed, and a custom recovery has also been installed. I also want to make sure the customer will be able to update the device normally. I have seen many ways to unroot the device and bring it back to stock, but I wanted to make sure which route to go as the last thing I want is the device to be bricked or anything like that. :'(
Factory reset should be enough. Make sure you haven't modified any system files and Xposed isn't installed and he should be able to update. I would go ahead and update the recovery to. Use TWRP as CWR is buggy as hell
#AndroidL
If it were me, I'd flash the stock firmware in fastboot, lock the bootloader and sell it like that.
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
If it were me, I'd flash the stock firmware in fastboot, lock the bootloader and sell it like that.
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
I would to. I would also use the SDK kit to securely wipe my device properly as well.
#AndroidL
Thanks for the replies, I think I'm just gonna flash the stock image via fastboot, but I was just thinking can't I just factory reset in TWRP?
josephlavagna said:
Thanks for the replies, I think I'm just gonna flash the stock image via fastboot, but I was just thinking can't I just factory reset in TWRP?
Click to expand...
Click to collapse
All that does is wipe /data and /cache. SuperSU binaries/apk are in /system.
josephlavagna said:
Hi, I have a rooted nexus 5 which I want to sell, I really don't mind selling it rooted or not but all I want to do is factory reset it so none of my old data is on there. Can I just factory reset it in settings or Do I need to flash a stock image. It has the stock rom, with Super Su installed, and a custom recovery has also been installed. I also want to make sure the customer will be able to update the device normally. I have seen many ways to unroot the device and bring it back to stock, but I wanted to make sure which route to go as the last thing I want is the device to be bricked or anything like that. :'(
Click to expand...
Click to collapse
There is more than one option to wipe your personal info and sell it rooted and hopefully I can add to the confusion. This is what I've done in the past when selling or giving away any device that the new owner wants to have rooted. I fastboot flash the system and boot images that are extracted from the factory image. Flashing the system image will make 100% sure that no modified system files will be lurking around trying to cause problems in the future. After flashing the system and boot images, while your device is in the bootloader screen, use the buttons to boot into recovery and flash the SuperSu installable zip that you will have downloaded to your device storage before flashing any images. After installing SuperSu while still in TWRP go to Wipe/Advanced Wipe and check the boxes for Cache, Internal Storage, Data and Dalvik Cache. Do NOT check System, you will have no OS to boot into if you do! If you're extra cautious/paranoid or have OCD (like myself) you can do a factory reset from inside your device settings after it boots up. TWRP has very recently been updated so that image can be flashed with the other images or beforehand using Flashify, if it needs to be updated. The above is just one of the ways to get to the same outcome, making sure there are no modified files in the system and that all personal info has been removed!
josephlavagna said:
Thanks for the replies, I think I'm just gonna flash the stock image via fastboot, but I was just thinking can't I just factory reset in TWRP?
Click to expand...
Click to collapse
You can use factory reset but if the seller want to recover your old file; its possible.
http://www.cnet.com/news/android-phone-wiping-fails-to-delete-personal-data/
Good luck!
I believe encrypting your device prior to doing a factory reset will prevent recovery of your files, but I haven't been able to confirm that.
Restola said:
I believe encrypting your device prior to doing a factory reset will prevent recovery of your files, but I haven't been able to confirm that.
Click to expand...
Click to collapse
Yes it would because the files left on the device after a factory reset will be inaccessible.
good thinking...
Possibly most efficient way:
fastboot oem lock (if currently unlocked)
boot into Android then go to Settings and turn on encryption
reboot to bootloader (or "adb reboot bootloader") and then fastboot oem unlock (this will absolutely erase everything on your device!)
boot into recovery and use ADB sideload to flash SuperSU (TWRP should support this)
(optional) relock bootloader?
That should result in a completely wiped, stock, rooted device with TWRP and unrecoverable personal data without having to reflash anything other than SuperSU?
chaosdefinesorder said:
Possibly most efficient way:
fastboot oem lock (if currently unlocked)
boot into Android then go to Settings and turn on encryption
reboot to bootloader (or "adb reboot bootloader") and then fastboot oem unlock (this will absolutely erase everything on your device!)
boot into recovery and use ADB sideload to flash SuperSU (TWRP should support this)
(optional) relock bootloader?
That should result in a completely wiped, stock, rooted device with TWRP and unrecoverable personal data without having to reflash anything other than SuperSU?
Click to expand...
Click to collapse
1. Encrypt.
2. Flash and wipe everything with fastboot (flash-all.bat/sh).
3. Relock bootloader
4. Sell.
Alternatively, use LG Flashtool and it'll automatically reflash/wipe + relock bootloader + reset tamper flag. Then it would be three steps.
Lethargy said:
1. Encrypt.
2. Flash and wipe everything with fastboot (flash-all.bat/sh).
3. Relock bootloader
4. Sell.
Alternatively, use LG Flashtool and it'll automatically reflash/wipe + relock bootloader + reset tamper flag. Then it would be three steps.
Click to expand...
Click to collapse
I was going for the route that did not require downloading the full ROM first...
chaosdefinesorder said:
I was going for the route that did not require downloading the full ROM first...
Click to expand...
Click to collapse
Quite a few of us always keep a set of factory images on a PC anyways
Edit: also, there are many people on custom ROMs or have modified /system. Factory reset within Android only wipes /data (internal storage included) and doesn't do anything else. Same with bootloader unlock. If you deleted an .apk in /system for example, where would a factory reset/bootloader unlock get it back from?
chaosdefinesorder said:
I was going for the route that did not require downloading the full ROM first...
Click to expand...
Click to collapse
To keep rooted but give a good clean up - you can
-download rooted rom.zip and flash via recovery.
-Lockock bootloader and reset flag via bootunlocker app.
-Encrypt.
-Wipe.
Easy. Can even flash a different recovery first although, if rooted, custom recovery is good idea. Still best to unroot if you ask me, which you can easily do via the superuser app..
-download rooted rom.zip and flash via recovery.
-Flash stock recovery zip
-Lockock bootloader and reset flag via bootunlocker app.
-Uroot via supersu
-Encrypt.
-Wipe.
Hi,
I wanted to flash the just released lollipop image so I unlocked my phone and updated TWRP from 2.8.0.1 to 2.8.1.0. Then I started Recovery and it was doing some werid thing in a list (was too fast), then rebooted. Recovery came up again (only the image of TWRP) and a restart again. Since then always when I try to go into recovery the starting image will show up, after 2-3 secs it gets black for half a second, then the image will show up again. This is a permanent loop. I flashed back to the old recovery but nnothing, still the same (and this one worked before!).
Hopefully someone of you knows whats wrong.
Thanks,
S3cret
reflash twrp recovery. but to correct you on your mistake before you do it, factory imgs are not flashable via any recovery, you can only flash them via fastboot.
I reflashed recovery several times now. I just thought being on the latest recovery version would be good. I know how to flash the lollipop image via fastboot, but I still need recovery for root.
I locked and unlocked the bootloader again and the same happened. Recovery started, doing some weird things and then the loop again.
Edit: Ok, I fixed it, somehow, I dont rly know how...
TWRP only starts after flashing it on my device. After a reboot, it doesn't work.
vercety974 said:
TWRP only starts after flashing it on my device. After a reboot, it doesn't work.
Click to expand...
Click to collapse
exactly the same here
Yup, dead Android with red warning triangle appears...
My stock recovery is broken after fastbooting the latest 5 image. Shows a red triangle above the laying down android.
How are we supposed to fix this?
Moreover, I've just reflashed the entire rom, and can't access the stock recovery. But the stock recovery seems to work beacause I can to factory reset via the settings menu, backup and restore.... Maybe it is the new security policy from google, to avoid that a thief make a factory reset directly from the recovery ?
So we can't navigate in the stock recovery anymore ?
Highway 55 said:
After fastboot flashing the .img files you need to (WITHOUT REBOOTING) flash custom recovery, TWRP etc... After that from the bootloader reboot into TWRP or whatever. When your in the custom recovery you need to adb push a permissive stock kernel or custom kernel as well as suspersu.zip. Again, without rebooting into the system, flash the kernel first then supersu. Now you can reboot into the system. ?
Click to expand...
Click to collapse
vercety974 said:
Moreover, I've just reflashed the entire rom, and can't access the stock recovery. But the stock recovery seems to work beacause I can to factory reset via the settings menu, backup and restore.... Maybe it is the new security policy from google, to avoid that a thief make a factory reset directly from the recovery ?
So we can't navigate in the stock recovery anymore ?
Click to expand...
Click to collapse
Yes I think it does have to do with the new selinux security stuff. I don't know the specifics. Maybe you want to refer to this thread. http://forum.xda-developers.com/showthread.php?p=56538538 @rootSU knows far more than I do. [emoji6]
Highway 55 said:
Yes I think it does have to do with the new selinux security stuff. I don't know the specifics. Maybe you want to refer to this thread. http://forum.xda-developers.com/showthread.php?p=56538538 @rootSU knows far more than I do. [emoji6]
Click to expand...
Click to collapse
It is exactly as he said in the post you linked.
Flash TWRP recovery and immidiately after run auto root. Then TWRP recovery will survive system boots.
I was using package disabler pro to disable some Samsung apps, like galaxy apps, billing etc. I have had the phone like this for months without problem. Today I re enabled galaxy apps and rebooted phone and now my phone is boot-looping, stuck on samsung logo. I re flashed the EXACT same rom that is on there via ODIN, (XSA g920i) and it STILL boot loops. Normally this fixes problems like this. The phone is stock, uprooted. Don't tell me I have to factory reset it all?
Will not even boot up in safe mode.
This can be moved to the Q and A section but I also didn't realise you can soft brick your phone without root.
I am definitely sure it was re enabling some apps in package disabler pro that did it. Is there some way to ABD console re enable all apps or undo whatever the program has done?
I'm willing to install twrp recovery on the phone so I can mount system and undo whatever the program has done. Does anyone know what to alter?
$10 paypal for solution that doesn't involve loosing data.
If I factory reset, will I be able to recover the files on there like pictures and images with a program?
Install custom recovery, then mount you sd partition in recovery and connect to pc then move all your pics etc to pc, then factory reset
rosso22 said:
Install custom recovery, then mount you sd partition in recovery and connect to pc then move all your pics etc to pc, then factory reset
Click to expand...
Click to collapse
Yea Im aware I would be able to do that but I want to be able to undo the programs influence so I can boot into my phone again.
So I take it I use the latest twrp and just flash via odin? I dont need to also flash a custom kernel?
Yeah just flash recovery with odin, you could probably try using the file manager in recovery to delete the galaxy apps apk, or fixing permissions may work, or possibly wipe cache and dalvik and may be able to boot, the custom recovery gives you a few options
I contacted the dev and he said there is a way to fix it via ABD. The stock s6 mm recovery has an ABD option, is this the same as a proper abd when the phone is booted up, or does it only allow you to push signed files and updates accross?
So does this mean it is possible to fix the issue without flashing custom recovery?
Is there another section this can be moved to? Im surpised there isnt more information for such a popular app with a common problem.
I just realised I have reactivation lock enabled. Does this mean I CANNOT flash custom recovery? If thats the case I dont even want to try.
How to enable 'Android system' back?
Hello!
I have disabled 'Android system' in 'packagedisabler pro' in Samsung sm-9005 and now the phone is stuck with Samsung logo and stars during booting. The phone cannot boot. How to enable 'Android system' back?
Hi, i just got my old 5 year old (now retired) device to bootup because someone had made a kernel for the device which supports overclocking so for the fun I wanted to try it
but there was one weird problem, it seemed that though the root permissions from years ago remained just like they were but magisk manager itself had lost root permissions though I was still able to grant root permissions to other applications normally
I was on an unofficial Lineage OS build and thought of returning to original Miui for the device, got the fastboot rom, got Mi flash, flashed it, booted up
but there was a catch, it would always throw an error on the login Miui account screen at startup saying "Couldn't check device security, please try again"
I had tried everything possible including:
adding a Xiaomi account
skipping sign in
Inserting a sim
None of them seemed to do anything so i flashed twrp recovery again as using mi flash to flash ur device's stock rom gets rid of custom recovery
Now here is the mistake I made
**I wiped the device clean using TWRP**
now i tried going into adb sideload mode, no matter what I did my PC wouldn't detect my device, tried going into fastboot mode and still my PC wouldn't recognise the device and same goes for Mi flash tool
additionally the device would automatically exit out of fastboot mode within 2 minutes and go on to the power off screen
I do have charge on the device it says it's at 87% on the TWRP menu
I can no longer bootup, im stuck at the MI logo on bootup
Device: Mi Max 2
Additional notes: I am not in a hurry as that is not my primary device so it is okay if you want to take your time to reply, even if there's no way i can get my phone to see the light of day again it's alright as the phone was retired and sitting collecting dust for 2 years now
I do not wish to visit a service center as it's not worth it for a device I'm just gonna use for a few hours then put it back into its grave again
just download that same, or another custom ROM, and flash it via TWRP (just put ROM in SD card).
Nothing is gone, i mean if you delete system via twrp of course it will bootloop as it don't have system.
And for reverting back to original stock ROM , i think it have to do something with encryption, or maybe just the fact you unlocked bootloader.
Best is to stay away from stock ROM, find some custom ROM which have similar to MIUI (stock rom) , somewhat improved, if you want to get as much stock ROM experience.
kraken-gz said:
just download that same, or another custom ROM, and flash it via TWRP (just put ROM in SD card).
Nothing is gone, i mean if you delete system via twrp of course it will bootloop as it don't have system.
And for reverting back to original stock ROM , i think it have to do something with encryption, or maybe just the fact you unlocked bootloader.
Best is to stay away from stock ROM, find some custom ROM which have similar to MIUI (stock rom) , somewhat improved, if you want to get as much stock ROM experience.
Click to expand...
Click to collapse
Hi, thanks for the reply, I tried using an SD card and unfortunately it wouldn't detect that too, what i found was I didn't wipe System it still shows that it's taking up some place (3597 MB)
i would be fine getting a custom rom on the device infact i have crdroid ready to be installed
could it be that the TWRP i installed (yes I downloaded the latest version and didn't flash the old one i had years ago) have some bugs? (I did install it from official TWRP website)
also note: though you see a Senior Member title below my name, im a complete and utter noob
BR4UTAL said:
Hi, thanks for the reply, I tried using an SD card and unfortunately it wouldn't detect that too, what i found was I didn't wipe System it still shows that it's taking up some place (3597 MB)
i would be fine getting a custom rom on the device infact i have crdroid ready to be installed
could it be that the TWRP i installed (yes I downloaded the latest version and didn't flash the old one i had years ago) have some bugs? (I did install it from official TWRP website)
also note: though you see a Senior Member title below my name, im a complete and utter noob
Click to expand...
Click to collapse
Lol I thought I was the only proper noob here on xda but nice to meet other noobs here too .
I think Kraken-gz is right, once the older devices are OEM off-support its best to stay away from OEM servers, I lost couple of old lesser-known-brand devices to OEM mischief i'd say coz it happened twice to me when I reloaded the original ROMs and tried to connected to the net they went dead on the next bootup, I think the OEMs have something going on there to boot out the older devices so newer ones could be pushed in the market sooner than they were supposed to. Possible.
so, first, in twrp, try to completely format it, follow this to do it
Just, a note: in advanced wipe delete system, data, dalvik cache and cache.
When trying to reboot into system, make sure twrp complains that it have no system. (that way, you know you deleted it)
reboot it, again in twrp.
try to flash custom ROM, should work as it have clean memory.
If it doesnt flash, then make sure to note all log file from twrp while flashing, and post it here, in order to see, what failed in flashing. If it succeds, it should load custom rom . If custom rom dont work, try another one, maybe older, or one that you had previous time (before trying to go into stock rom) (just, to try to boot it somehow. But before trying another custom rom, if one fails, do proper wiping described above.
If that fails try to download oldest stock ROM, and flash it. Maybe newest is blocking it.
If that fails, there is something called EDL mode, when fastboot is not available (for hard brick, like this).
here is video just to give you overview how to do it
and text also
Edit:
WAIT, try to format it, without wiping system. maybe it will boot again.
If not, other solutions are not applicable, if you dont find way to detect that sd card. Only EDL remains.
kraken-gz said:
so, first, in twrp, try to completely format it, follow this to do it
Just, a note: in advanced wipe delete system, data, dalvik cache and cache.
When trying to reboot into system, make sure twrp complains that it have no system. (that way, you know you deleted it)
reboot it, again in twrp.
try to flash custom ROM, should work as it have clean memory.
If it doesnt flash, then make sure to note all log file from twrp while flashing, and post it here, in order to see, what failed in flashing. If it succeds, it should load custom rom . If custom rom dont work, try another one, maybe older, or one that you had previous time (before trying to go into stock rom) (just, to try to boot it somehow. But before trying another custom rom, if one fails, do proper wiping described above.
If that fails try to download oldest stock ROM, and flash it. Maybe newest is blocking it.
If that fails, there is something called EDL mode, when fastboot is not available (for hard brick, like this).
here is video just to give you overview how to do it
and text also
Edit:
WAIT, try to format it, without wiping system. maybe it will boot again.
If not, other solutions are not applicable, if you dont find way to detect that sd card. Only EDL remains.
Click to expand...
Click to collapse
Tried wiping data, cache and dalvik cache and formatting data, none seemed to help
and still no sd card being detected
Now edl mode
I would love to boot into edl mode but the thing is my device isn't being recognised by adb nor is it being recognised by fastboot commands
so that's where I'm stuck for now
OldNoobOne said:
Lol I thought I was the only proper noob here on xda but nice to meet other noobs here too .
I think Kraken-gz is right, once the older devices are OEM off-support its best to stay away from OEM servers, I lost couple of old lesser-known-brand devices to OEM mischief i'd say coz it happened twice to me when I reloaded the original ROMs and tried to connected to the net they went dead on the next bootup, I think the OEMs have something going on there to boot out the older devices so newer ones could be pushed in the market sooner than they were supposed to. Possible.
Click to expand...
Click to collapse
Perhaps that is true