Soft Bricked - Help! - Upgrading, Modifying and Unlocking

I have an Iriver NS-14T002. Not sure how but I still have stock rom on the device and worked on some rooting. Worked well didn't have any issues until one day seems it wont boot into OS. Gladly I had a backup just in case with cwm. I restored and everything seem to work fine. Then it happened again so I thought well I will just unroot it and make it factory again, but I wasnt going to mess with it at the moment. I worked on some other projects and realized that the cwm backup was gone. Little upset so I researched the internet for the stock rom. Couldn't find it. Maybe a custome rom? Nope this device has little support which I understand. I tried factory resetting with CWM. Didn't fix it. Delvik? Nope. So I had adb shell available for CWM. I thought if I reflash stock recovery that it would know how to properly factory reset the OS. Nope no go. Now I am stuck with factory recovery and a broken OS. Factory recovery doesn't have adb access or if it does I dont know how to gain it. The recover version is 4.2.01. Or Android system recover <3e>. Anyway I can possibly flash cwm back on it? or if there is any solution to repair android OS that would be great. On another not I am not sure if the tablet has a bootloader.

Related

Galaxy Neuxs Encryption woes!!!

Hey All,
New to XDA but been using this site years so my level of Android knowledge is not bad.
I am currently having a huge problem with my Nexus. I used Google Apps encryption on it recently and that seems to have bricked my phone. I am unable to reset to factory settings to wipe the encryption as recommended by Google and I am stuck now with a bricked Nexus.
I also tried flashing stock roms with Odin which appears to work but the encryption still remains. All I am trying to do is put the stock back on my phone and re-root but I am having no joy. When using CWM to flash a new rom the system does not mount in recovery mode so I can't load any other roms. I have also tried the fastboot method but it stalls on waiting for device all the time.
If anyone has seen this and can help or if anyone just knows how to fix it please help me! I am stuck now with a useless Nexus. I should have just left it alone but as usual I couldn't.
Any help would be so appreciated. Thank you.
By some chance is your phone both rooted with CWM?
Hey, yeah it was so when I did a factory reset it could'nt use the stock bootloader so it didn't know how to wipe it. Unfortunetly once you apply encryption from a Google Apps the only way to remove is to factory reset.
I got around it by fastbooting the stock bootloader, radio and image from Google. Then I completed a manual reset using the original bootloader.
A world of hurt really! I have learned a lot but never going near Google Apps encryption again. It also slowed down the phone too.
Anyhow all sorted now, re rooted and running revolution rom now.
theres another thread with a guy who had the same problem. I wonder if vzw nexus has an issue with encrypting...
If the phone wasn't rooted I would have had no issues. It is simply a problem when it comes to loading roms. In CWM the recovery cant mount the data/system so you can't flash anything. Also doing a factory reset from settings doesnt work because the phone is looking for a stock bootloader which it doesn't have once you root. So I ended up in a loop and could do nothing. Fortunetly I learned all about adb and fastboot this morning, never heard of them before and that allowed me to reload stock and unroot. I still had to wipe the phone using the bootloader as I couldn't get into the phone or past the encryption.
If anyone is having issues with this I will gladly help as I really thought that my phone was bricked and was very frustrated. The only way I got help was from a guy on this tread http://forum.xda-developers.com/showthread.php?t=1392037&page=3

[Q] Soft brick recovery problems on T-Mobile S4

Last night I installed a new nightly update of Cyanogenmod for my S4. Unlike the last few times, it went into a boot loop.
I could not get it to go into recovery. The twrm recovery hung on the load screen. I installed cm recovery. That worked, but reformatting /data causes a reboot.
I got a stock image for 4.4.2 and flashed that. That would boot, but it now claims that the /data partition is encrypted. It does not decrypt with any password I have ever used.
Any idea how I can reformat /data without recovery? I could use heimdall, but I do not have a data.img. Any idea where I can find one?
This is REAL frustrating. I could probably fix it in an adb shell, but I have not been able to get to that either.
Ideas?
May be pining for the fjords.
AlanO2 said:
Last night I installed a new nightly update of Cyanogenmod for my S4. Unlike the last few times, it went into a boot loop.
I could not get it to go into recovery. The twrm recovery hung on the load screen. I installed cm recovery. That worked, but reformatting /data causes a reboot.
I got a stock image for 4.4.2 and flashed that. That would boot, but it now claims that the /data partition is encrypted. It does not decrypt with any password I have ever used.
Any idea how I can reformat /data without recovery? I could use heimdall, but I do not have a data.img. Any idea where I can find one?
This is REAL frustrating. I could probably fix it in an adb shell, but I have not been able to get to that either.
Ideas?
Click to expand...
Click to collapse
The more I look at this, the more I think that the media that /data lives on is dying/dead. It is the only thing that explains the reboot when I try and do a factory reset. I am going to see if I can get an exchange on the phone. Wish me luck.
SOLVED!
I figured out what it takes to resolved the brickatude.
:cyclops:
Flash back to stock including the original recovery. Use the original recovery to do a factory reset. That works!
For some reason the original recovery will work where the CM recovery bjorks out and reboots the device.
Also, there are rumors that the stock recovery resets the Knox flag. This is not true. It just no longer displays the status every time you boot. The flag is still set, the OS just does not seem to care.
BTW, getting into recovery is a pain in the ass no matter what. It took me about 5-6 tries to get it to work. There seems to be some sort of timing issue as to when you need to release the buttons and you have to get it just right or it won't work. Don't give up.
Also, get the stock firmware from sammobile.com. The other sites listed kept trying to install malware on my machine. (Pretty funny when it tried to claim I needed a Windows update on my Linux system.) At some point I will yank down the malware and see what it does.

V410 7.0 LTE bricked

Ok guys I am pretty sure I fubar'd my tablet.
I am stuck in a recovery loop. When I start the tablet it just goes back into recovery. Which if I still had TWRP I think I could still do something, but I flashed cyanogen recovery trying to flash cm13 since I cold not get anything else to work. I cannot boot into download/firmware update screen. The screen just flickers a little and goes dark.
A little background:
Started when tablet forced install of 5.0 update and I was in a recovery loop. I flashed 410 test build, rooted, flashed twrp, installed stock rooted ROM. Everything was fine. Then tablet did it again, this time I just flashed rooted ROM and factory reset. Even took the steps to fix the white lines and storage issues. Was working fine. Got home a few days ago and I was in a recovery loop again. But now I don't have the bootloader screen/download mode/firmware update screen (whatever you want to call it) so last night i tried to download cm13, Gapps and cyanogen recovery with no avail.
I can access adb on my PC while in recovery, but when I try to access ADB shell I get unauthorized something or other. Because I cannot authorize USB debugging, because ROM won't boot. I tried to flash stock rooted ROM from cyanogen recovery and it says not signed or something like that.
Does anyone have any ideas? I really think I have screwed the pooch here.
sent from a device using an app
title
if you have a stock recovery image flashing it is easy, i had a LOT of troubles with my v410 and still am working with it. i have mine rooted, just with TWRP though, i cant use xposed framework, which negates why i rooted this in the first place. anyway, through much grit and determination flash your stock image after wiping what needs to be wiped and doing all other necessary things. Then, you must download kingo root, supersu, superuser. flashify would help with the flashing i hear, but it has troubles with the v410. kingo root was an apk i managed to find buried under a million viruses on the 34th page of google..or something. rooted mine in one click, from stock to reboot to twrp root.. many glitches.
I need help myself, deleted my "Phone" system app, causing me to lose connectivity with my data plan. cant seem to restore it, and flashify nor twrp has been able to flash a custom recovery, or a backup, im at a loss.
Help? We seek the same thing.
Ok but how do I flash the stock recovery image. I can't use fastboot. ADB says I am unauthorized.
sent from a device using an app
Anyone have any other ideas?
I am at a complete loss. I am by no means a developer, but I do know my way around. I really think I have FUBAR'd this one.
Kind of stinks, I give up. Anyone want a bricked v410?
Sent from my Galaxy Tab 2 using Tapatalk

Trying to update while rooted...

Hello,
today I accidentally tapped on "Update" (to 7.1.1) on my rooted Nexus 5X... Something you usually shouldn't do, but it was 2am and I was tired and.... Doesn't matter. After this my phone rebooted and almost instantly showed the dead android with the message "No command". And now I'm stuck there. After rebooting I still land there.
Since the error message almost instantly appeared and since I still can boot into TWRP (3.0.2-2), I think the update wasn't installed and I hope to find a way to avoid the factory reset of my phone. Do you have some tips or possible solutions what I should do in this case?
Thank you for your help.
Its odd this happened, when rooted and twrp installed. in my experience, the update will just simply fail and it will boot back up.... in your case, it sounds like something flashed but the phone didnt like it.... All I can think of is if you cant get into twrp, boot into fastboot and flash the factory image from google, you will loose all data though.....
EDIT, RE-READ you post, if you CAN get into TWRP, try flashing a backup... you should have a backup I hope, lol... First rule of root and flashing is make a backup asap....LOL
When I rooted my phone I did a backup. But the problem is, it was several months ago. So I tried the only method I could save all my data. It wasn't safe, I knew this, but no risk no fun.
My solution was: Download the ota update from Google and flash it with TWRP... Voila! My phone boots properly with the new update... But this method is like I mentioned before not safe and can probably cause a boot-loop with an overwritten recovery. I had to flash my recovery again, but everything works fine now.

[Q] LG G4 H811 Stuck in Recovery (TWRP) Loop

I was running the latest version of TWRP and a rooted version of the LG G6 port. Everything was stable and worked fine. So I was ready to give it back to its owner who I had modded it for. I went into the settings menu of the phone and did a standard factory reset to remove my account that was logged in so I could test the phone out before giving it to the owner. well when it finished resetting and rebooted, its been stuck in a boot loop ever since.
Tried just clearing both Dalvik Cache and Cache, to no avail. Tried Reflashing the rom and starting over. Still nothing. Tried flashing a different rom. Still nothing.
So what else can I try? and also if its the only thing I can do, rest it all the way back to stock factory everything. How do I do that on this phone. What program do I need and what files. and whats the steps to complete the process.
Thank you in advance for all help that is given
i factory reset in twrp and turned on developers options after first boot then reflashed twrp i always forget backup lol or delete it or use kdz you flashed before anyway i can help i will if you still need
if you have tried to flash the same custom rom or another is still not working, flashes with the program "lg up", you will need a kdz file,and the corresponding drivers. if with that you can not watch this tutorial before doing anything.
if you have a backup made with twrp, it flashes again.
https://forum.xda-developers.com/g4/help/unbrick-lg-g4-brick-hs-usb-qdloader-t3542785
during this process you will have to disassemble the back of the phone, (plastic) you do not need to remove the motherboard completely from the phone, anyway if you can enter download mode try with lg up tool.
if you need help around here we are.
Well now in the process of trying to fix it. The phone bricked and will no longer turn on at all. Is there anyway to fix this ?
Silicon Knight said:
Well now in the process of trying to fix it. The phone bricked and will no longer turn on at all. Is there anyway to fix this ?
Click to expand...
Click to collapse
Can you get into download mode?
Also, it's possible you have been hit by the bootloop

Categories

Resources