Related
Hi, after attempting to flash a custom ROM to my phone I'm experiencing a big problem, the phone will not boot past the HTC screen. This is obviously very frustrating as the phone is pretty much rendered useless.
I am able to get into the HBOOT menu by holding the Power button and Volume Down and from there am able to select Recovery and enter the ClockWork Mod recovery screens. As you can tell I'm a 100% noob and I really just want to revert my phone to a working state. My network is Vodafone UK. I can't find an RUU above version 3.13 which is apparently what I have (so it tries updating 3.13 to 3.13 and obviously fails).
Any help on getting my phone to work again would be very very appreciated, thanks.
VBQ24 said:
Hi, after attempting to flash a custom ROM to my phone I'm experiencing a big problem, the phone will not boot past the HTC screen. This is obviously very frustrating as the phone is pretty much rendered useless.
I am able to get into the HBOOT menu by holding the Power button and Volume Down and from there am able to select Recovery and enter the ClockWork Mod recovery screens. As you can tell I'm a 100% noob and I really just want to revert my phone to a working state. My network is Vodafone UK. I can't find an RUU above version 3.13 which is apparently what I have (so it tries updating 3.13 to 3.13 and obviously fails).
Any help on getting my phone to work again would be very very appreciated, thanks.
Click to expand...
Click to collapse
Download a ROM onto your computer, connect to your phone in recovery, mount the sdcard, move the ROM from your computer onto your phone's sdcard, and flash from recovery. No need for RUU.
Dont forget to wipe.
wipe data/factory reset and format all partitions (except sd card) from recovery.
Go to bananagranolas link in her signature, you'll find everything you need there.
Thanks a lot for your help! I was attempting to flash the JellyTime ROM which I understand must have failed to result in my phone not booting properly. Should I flash a stock ROM or will any ROM suffice?
VBQ24 said:
Thanks a lot for your help! I was attempting to flash the JellyTime ROM which I understand must have failed to result in my phone not booting properly. Should I flash a stock ROM or will any ROM suffice?
Click to expand...
Click to collapse
As long as you are S-OFF and have a custom recovery (CMW or 4EXT) you are able to flash any custom rom you like. Just make sure that you make a full wipe before the flashing (wipe data/factory reset, wipe cache partition, format system or in 4ext recovery just choose format all partitions except sdcard).
That should leave you up and running again.
Okay great!
I used the HTCDev tools to unlock my boot loader which I understand is different to S-OFF? Could that be while the ROM flashing failed originally?
EDIT: Upon trying to flash the JellyTime AKOP Rom I get a message saying install from SD card complete but it's still stuck at the HTC screen...
VBQ24 said:
Okay great!
I used the HTCDev tools to unlock my boot loader which I understand is different to S-OFF? Could that be while the ROM flashing failed originally?
Click to expand...
Click to collapse
If you have an unlocked bootloder, then you have to flash the rom (previous full wipe of course) then reboot bootloader (from advanced options in CWM) and then in fastboot (you should see fastboot usb in red in the phone when plugged to the pc) you have to flash the boot.img inside the rom zip folder.
Extract that file only (not the whole rom) and from a cmd session or terminal as root (located where the boot.img file is) type:
fastboot flash boot boot.img
Once that is done (you will get OKAY. finished near the bottom) you can reboot normally by typing in cmd fastboot reboot or choosing reboot from hboot.
My bootloader now says RELOCKED, how can I unlock it again? (I'm really sorry about this)
VBQ24 said:
My bootloader now says RELOCKED, how can I unlock it again? (I'm really sorry about this)
Click to expand...
Click to collapse
Use the token HTC sent you when u unlocked it. and typing in cmd the fastboot unlock command.
Okay done that, thanks a lot!
I'm now looking in the advanced options of CWM, I can see the option "Reboot Recovery" but no "Reboot Bootloader"?
VBQ24 said:
Okay done that, thanks a lot!
I'm now looking in the advanced options of CWM, I can see the option "Reboot Recovery" but no "Reboot Bootloader"?
Click to expand...
Click to collapse
then just turn the phone off (power off option) and then boot with power + volume down
glevitan said:
then just turn the phone off (power off option) and then boot with power + volume down
Click to expand...
Click to collapse
Okay, I wiped all partitions, installed JellyTime AOKP, restarted, went into fastboot, extracted/flash boot file and the rebooted phone.
The phone will now progress from the HTC screen but is now stuck on a black screen, Windows tried to install drivers but failed....
VBQ24 said:
Okay, I wiped all partitions, installed JellyTime AOKP, restarted, went into fastboot, extracted/flash boot file and the rebooted phone.
The phone will now progress from the HTC screen but is now stuck on a black screen, Windows tried to install drivers but failed....
Click to expand...
Click to collapse
Was the boot.img file flashed successfully?
Yes it said so...
EDIT: Not sure if this is an issue with the ROM of if I'm doing something wrong? I went to the "mounts and storage" section of CWM and clicked all the format options accept sdcard. I then installed ROM, went into fastboot and flashed boot.img, it said OKAY twice then finished. Still stuck at black, backlit screen after HTC screen. ROM is JellyTime by randomblame.
VBQ24 said:
Yes it said so...
Click to expand...
Click to collapse
that is weird. Try flashing a different rom then and see what happens. flash the boot image first and then the the rom in recovery.
glevitan said:
that is weird. Try flashing a different rom then and see what happens. flash the boot image first and then the the rom in recovery.
Click to expand...
Click to collapse
I've just tried flashing the boot image first and then installing JellyTime AOKP, same black screen. Maybe I should try a Gingerbread ROM? That's the Operating system I had before, is there a known working ROM?
VBQ24 said:
I've just tried flashing the boot image first and then installing JellyTime AOKP, same black screen. Maybe I should try a Gingerbread ROM? That's the Operating system I had before, is there a known working ROM?
Click to expand...
Click to collapse
Sorry, have You checked the md5sum of the file? Maybe You have a bad download...if that it Is ok, then try flashing a totally different rom and see what happens.
glevitan said:
Sorry, have You checked the md5sum of the file? Maybe You have a bad download...if that it Is ok, then try flashing a totally different rom and see what happens.
Click to expand...
Click to collapse
No I haven't checked the md5sum of the file, how should I go about doing that?
VBQ24 said:
No I haven't checked the md5sum of the file, how should I go about doing that?
Click to expand...
Click to collapse
https://play.google.com/store/apps/details?id=com.fab.md5
EDIT: well, don't I feel stupid. I knew full well from reading that your phone wasn't working, but posted a link to an app. Just not paying attention. Sorry about that.
VBQ24,
You can go back to stock by flashing a stock RUU from your PC.
(Edit: You should relock your bootloader first. you can do so from Hboot. There's an option that says relock bootloader or something like that)
The version of the RUU should be equal or greater to the version that came with your phone. Try this v3.13
However, if you want to flash a custom ROM:
You need to downgrade your device first, get s-off and root, then flash a custom ROM
You need to use the Advanced Ace Hack Kit (AAHK), get it from here.
Make sure to read the manual (called 'effin manual) word by word. There are instructions on how to downgrade.
Follow the instructions, and if you have any questions, ask here.
Early this morning I decided to try to get root and flash a custom rom, either CyanogenMod or Omni. I was able to flash touch recovery and wiped system files and cache. All custom firmwares failed to load. Now when the phone boots up, it goes into OTA activation, activates, does a PRL update, and reboots. Touch recovery repeats the system restore, unattended, and the loop repeats infinitely.
I am looking for a process that will help me cure the reboot loop to let me return to using the stock 4.3, but because of some bugginess I was experiencing, I would prefer a method that rids the knox bootloader and other protections so that I can gain root access and load custom firmwares.
I found a similar thread for a different model number, but I'm sure I'll need specific instructions for this model. Any help is greatly appreciated, as I'd rather not have to figure out a way to destroy the phone to get an insurance replacement. I'm also 23 days away from my upgrade date.
I am offering a $50 bounty for now, and when I upgrade, if possible to retain my phone while getting the upgrade price, you can have the note 2 that you helped fix.
cjkline83 said:
Early this morning I decided to try to get root and flash a custom rom, either CyanogenMod or Omni. I was able to flash touch recovery and wiped system files and cache. All custom firmwares failed to load. Now when the phone boots up, it goes into OTA activation, activates, does a PRL update, and reboots. Touch recovery repeats the system restore, unattended, and the loop repeats infinitely.
I am looking for a process that will help me cure the reboot loop to let me return to using the stock 4.3, but because of some bugginess I was experiencing, I would prefer a method that rids the knox bootloader and other protections so that I can gain root access and load custom firmwares.
I found a similar thread for a different model number, but I'm sure I'll need specific instructions for this model. Any help is greatly appreciated, as I'd rather not have to figure out a way to destroy the phone to get an insurance replacement. I'm also 23 days away from my upgrade date.
I am offering a $50 bounty for now, and when I upgrade, if possible to retain my phone while getting the upgrade price, you can have the note 2 that you helped fix.
Click to expand...
Click to collapse
Try this
Flash twrp recovery zip
Custom wipe system, data, cache
Install this http://forum.xda-developers.com/showthread.php?p=36388145
Install the root zip located in that op
Do not wipe anything else
Reboot it should act weird then reboot
After about 5-10 mins it will finish booting
Now flash philz 6.07.9 recovery via odin
Then boot into recovery factory reset/clean for new rom
Under mounts format data/media (internal sd)
Reboot into recovery
Flash your 4.4 rom
Sent from my SPH-L900 using XDA Premium 4 mobile app
Pending Testing
jlmancuso said:
Try this
Flash twrp recovery zip
Custom wipe system, data, cache
Install this http://forum.xda-developers.com/showthread.php?p=36388145
Install the root zip located in that op
Do not wipe anything else
Click to expand...
Click to collapse
Yeah, I wiped everything when I got home from work (don't know what I was thinking, really). TWRP even warned me no OS was installed, and I was like "so?". Anyway, as soon as it got stuck on the Samsung Galaxy Note II screen, I started the download of that rom you linked to. Still has 10 minutes left (big file is big). I'll come back with an update once I complete these first set of steps.
[Pending:]
Reboot it should act weird then reboot
After about 5-10 mins it will finish booting
Now flash philz 6.07.9 recovery via odin
Then boot into recovery factory reset/clean for new rom
Under mounts format data/media (internal sd)
Reboot into recovery
Flash your 4.4 rom
====================================
ADB Sideload
Since the device is not bootable, and I don't have an adapter to copy to my SD card via a usb reader, I struggled, but got the ADB Sideload function of the Android Development Toolkit to work once I upgrade to Team Win Recovery 2.7.0.0 via ODIN.
sideload log is as follows:
Code:
Updating partition details...
Full SELinux support is present.
Starting ADB sideload feature...
Installing '/data/media/0/sideload.zip'...
Checking for MD5 file...
Skipping MD5 check: no MD5 file found.
UnRooted MC2 Stock Restore by blizzard412
Formatting /system and installing..
This will take a while
...Flashing temp special recovery
...Again just in case
Installing Radio...
Flashing firmware...
Flashing garwrnn & -EViL-KoNCEPTz- carrier partition fix...
You will automatically reboot to twrp to finish up...
[COLOR="Red"]E:Unable to mount '/preload'[/COLOR]
Should I be worried about the preload error?
Edit: rebooted but currently in a reboot loop without the startup sound. I'm going to let this go for about 10 minutes before I try to wipe and re-sideload? Before TouchWin rebooted it asked me if I wanted to install SU-SuperUser for root. Should I not install the root at this time?
Edit 2 THANK YOU!
[Pending:]
Reboot it should act weird then reboot
After about 5-10 mins it will finish booting
Now flash philz 6.07.9 recovery via odin.
Click to expand...
Click to collapse
I could not get this to flash via ODIN. The stock recovery kept loading instead
Decided to just try and move down the list.
Then boot into recovery factory reset/clean for new rom
Under mounts format data/media (internal sd)
Click to expand...
Click to collapse
Phone is now out of reboot loop once I cleared the data and cache. Text messages immediately came in after OTA activation and PRL update. I am now running stock rooted 4.1.2 without KNOX.
Reboot into recovery
Flash your 4.4 rom
Click to expand...
Click to collapse
Might wait on that for a minute. So thankful to at least have a working device again. Thanks for your help. Would you like the bounty? Please PM me a paypal address or your preferred methods.
The preload error is normal with twrp and is not an issue. Now you have lots going on so let me ask you this. Do you have a custom recovery and/or root as of now?
Sent from my SPH-L900 using XDA Premium 4 mobile app
Systems nominal
jlmancuso said:
The preload error is normal with twrp and is not an issue. Now you have lots going on so let me ask you this. Do you have a custom recovery and/or root as of now?
Sent from my SPH-L900 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Yes, I had a rooted stock rom, replied to my texts from the day, then loaded rom manager, installed clockwork recovery. downloaded omni directly to the phone from their website, rebooted into clockwork, flashed, and things were fine. Booted into rooted kitkat 4.4.2, and now I'm flashin the gapps update to enable google services. network and wifi working fine under omni.
Can't thank you enough for helping me out of that hole from earlier.
In case you dont know omni rom does not come rooted.
Sent from my SPH-L900 using XDA Premium 4 mobile app
jlmancuso said:
In case you dont know omni rom does not come rooted.
Sent from my SPH-L900 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Yep, I flashed SuperSU in CWM and fixed that. Things are running great. Just need to see what the battery life is like now on a new rom.
I have been trying to flash TWRP 2.7.1.0 on my Wildfire S, but failed. It just goes back to CWM 5.0.2.8. I stupidly went to wipe data in recovery, and now my recovery is corrupted. When I try to mount USB storage, it gives me
Code:
E:Unable to write to ums lunfile (No such file or directory)
I tried fastboot, but since I'm running Windows 8.1, HTC drivers won't install. I have tried most solutions but they all don't work. Is there a way I can flash the recovery from my computer?
You should be able to flash a .tar recovery through Odin
Sent from my SPH-L900 using XDA Free mobile app
DubLJay said:
You should be able to flash a .tar recovery through Odin
Sent from my SPH-L900 using XDA Free mobile app
Click to expand...
Click to collapse
As bootloader? PDA? Phone? CSC?
Edit: Odin can't even detect my phone
herobrine_second said:
As bootloader? PDA? Phone? CSC?
Edit: Odin can't even detect my phone
Click to expand...
Click to collapse
It should not detect too. Odin is for samsung phones. To reinstall the recovery you can try to flash by the PG76100.zip method. Get a recovery in a zip, place it on root of sdcard and boot to bootloader.
BTW how are you sure that your recovery is corrupted? It is really a very weird thing for the recovery to be corrupted.
aWFSuser said:
It should not detect too. Odin is for samsung phones. To reinstall the recovery you can try to flash by the PG76100.zip method. Get a recovery in a zip, place it on root of sdcard and boot to bootloader.
BTW how are you sure that your recovery is corrupted? It is really a very weird thing for the recovery to be corrupted.
Click to expand...
Click to collapse
It isn't really corrupted, just not working as intended. I will try the PG76100.zip tomorrow when I have time. BTW, that is flashed from bootloader right?
Sent from my GT-I9305 using Tapatalk
herobrine_second said:
It isn't really corrupted, just not working as intended. I will try the PG76100.zip tomorrow when I have time. BTW, that is flashed from bootloader right?
Sent from my GT-I9305 using Tapatalk
Click to expand...
Click to collapse
Yes you can just go to bootloader and it will check for the file and prompt to install it. And what do you mean by not working as intended? Are you trying to flash CM11 then it will require at least CWM6 or TWRP 2.7
aWFSuser said:
Yes you can just go to bootloader and it will check for the file and prompt to install it. And what do you mean by not working as intended? Are you trying to flash CM11 then it will require at least CWM6 or TWRP 2.7
Click to expand...
Click to collapse
Trying to mount USB storage will give error as posted in OP, trying to flash from SD card or mount SD card will show Unable to mount SD card error. I am trying to flash TWRP 2.7.1.0. (check OP)
Sent from my GT-I9305 using Tapatalk
Tried the PG76IMG.zip method from 2.3.5 RUU, flashed in HBoot, factory reset-ed, phone still not booting/recovery still CWM 5.0.2.8.
Edit: Recovery is working as per normal, however anything I flash, it will just reboot to recovery half way in booting process. Stock 2.3.5, Marvellous Sense 3.5, CM10.1, all of them.
herobrine_second said:
Tried the PG76IMG.zip method from 2.3.5 RUU, flashed in HBoot, factory reset-ed, phone still not booting/recovery still CWM 5.0.2.8.
Edit: Recovery is working as per normal, however anything I flash, it will just reboot to recovery half way in booting process. Stock 2.3.5, Marvellous Sense 3.5, CM10.1, all of them.
Click to expand...
Click to collapse
You don't need to factory reset after the recovery. Was there any errors while flashing? Try a fresh start like --> Install another recovery, if it installs then all well but if it does not then find the correct RUU for your model and flash it. You'll need to redo everything you did to root your phone after this. BTW are you sure you wiped system and data? Both of them and before flash not after.
aWFSuser said:
You don't need to factory reset after the recovery. Was there any errors while flashing? Try a fresh start like --> Install another recovery, if it installs then all well but if it does not then find the correct RUU for your model and flash it. You'll need to redo everything you did to root your phone after this. BTW are you sure you wiped system and data? Both of them and before flash not after.
Click to expand...
Click to collapse
My process went from start to current position like this:
1. Was on Marvellous Sense 3.5
2. Tried to flash TWRP 2.7.0.0 through terminal
3. Reboot to recovery, CWM 5.0.2.8 still there
4. Redid process, still CWM 5.0.2.8
5. Thought it was a ROM problem, wiped data, tried installing Marvellous Sense 3.5, CWM wouldn't read SD card, (CWM problems started)
6. Tried creating own PG76IMG.zip with TWRP 2.7.0.0 inside, CID error when flashed in hboot
7. Ran RUU to get ROM.zip, transferred to SD card as PG76IMG.zip, flashed in hboot. (Wiped data before flashing)
8. Phone won't boot, recovery problem automagically ended
9. Tried flashing OWL recovery PG76IMG.zip in hboot, got CID error again.
10. Current situation.
I won't be able to get my CID since I'm running Windows 8.1, and I can't get hold of any Windows 7 PC.
Sent from my GT-I9305 using Tapatalk
herobrine_second said:
My process went from start to current position like this:
1. Was on Marvellous Sense 3.5
2. Tried to flash TWRP 2.7.0.0 through terminal
3. Reboot to recovery, CWM 5.0.2.8 still there
4. Redid process, still CWM 5.0.2.8
5. Thought it was a ROM problem, wiped data, tried installing Marvellous Sense 3.5, CWM wouldn't read SD card, (CWM problems started)
6. Tried creating own PG76IMG.zip with TWRP 2.7.0.0 inside, CID error when flashed in hboot
7. Ran RUU to get ROM.zip, transferred to SD card as PG76IMG.zip, flashed in hboot. (Wiped data before flashing)
8. Phone won't boot, recovery problem automagically ended
9. Tried flashing OWL recovery PG76IMG.zip in hboot, got CID error again.
10. Current situation.
I won't be able to get my CID since I'm running Windows 8.1, and I can't get hold of any Windows 7 PC.
Sent from my GT-I9305 using Tapatalk
Click to expand...
Click to collapse
Creating the PG76IMG.zip by your own would not work as the necessary info file is not inside. Take the zip I attached and replace the recovery.img inside with which recovery you want. And don't replace the android-info.txt. That's the one you're missing now.
And press thanks if it worked
aWFSuser said:
Creating the PG76IMG.zip by your own would not work as the necessary info file is not inside. Take the zip I attached and replace the recovery.img inside with which recovery you want. And don't replace the android-info.txt. That's the one you're missing now.
And press thanks if it worked
Click to expand...
Click to collapse
There's no zip attached, but anyway, thanks for your solutions, I fixed my problem by flashing recovery from fastboot by borrowing a Windows 7 laptop from my friend
Hi
I recently bought a used HTC One M8.
The previous owner already rooted the phone, and had Viper 1.5 installed.
Now, trying to update the Viper, I found out there is a problem with the phone recovery (which currently appears to be stock).
Every time I need to complete an action through recovery, like updating the ROm or just changing the boot logo, it gives me the red triangle almost instantly. The explanation it gives me is:
"Mount SDCard failed 1 times
Mount SDCard failed 2 times
Mount SDCard failed 3 times
Mount SDCard failed 4 times
Mount SDCard failed 5 times
Can not mount SD Card. (No such file or directory)
I:Write host_mod: 0 done"
When trying to "Apply from phone storage", it writes:
"Check cid failed!
--invalid operation--"
(My CID is "HTC_002" by the way).
Anybody got any idea to what is wrong with the recovery?
MXSteel said:
Hi
I recently bought a used HTC One M8.
The previous owner already rooted the phone, and had Viper 1.5 installed.
Now, trying to update the Viper, I found out there is a problem with the phone recovery (which currently appears to be stock).
Every time I need to complete an action through recovery, like updating the ROm or just changing the boot logo, it gives me the red triangle almost instantly. The explanation it gives me is:
"Mount SDCard failed 1 times
Mount SDCard failed 2 times
Mount SDCard failed 3 times
Mount SDCard failed 4 times
Mount SDCard failed 5 times
Can not mount SD Card. (No such file or directory)
I:Write host_mod: 0 done"
When trying to "Apply from phone storage", it writes:
"Check cid failed!
--invalid operation--"
(My CID is "HTC_002" by the way).
Anybody got any idea to what is wrong with the recovery?
Click to expand...
Click to collapse
Try reflashing recovery through hboot
exocetdj said:
Try reflashing recovery through hboot
Click to expand...
Click to collapse
Just finished flashing TWRP through the computer. I'll see if it worked and edit the resault.
Edit:
Now it no longer even enters recovery. Just shows that screen with the red legal warning at the bottom and "Entering recovery" at the top, and.. reboots, and boots straight to the OS.
That's from TWRP 2.7.1 for [m8].
Edit #2:
Nvm, I flashed TWRP 2.7.0.1 by accident.
Now flashed 2.7.1, and it at least entered it the first time. Gonna see if I can install my ROM updates through it
Edit #3:
Seems good. Thanks.
Yes, red triangle is stock recovery. Any idea how you got back to that?
Did you factory reset in bootloader, by any chance?
redpoint73 said:
Yes, red triangle is stock recovery. Any idea how you got back to that?
Did you factory reset in bootloader, by any chance?
Click to expand...
Click to collapse
That's how the last owner left it. Considering it didn't even work, I doubt you'd want to get back to that, not to mention TWRP is way better.
I assume if you factory reset all the phone, it'll probably return you to stock recovery mode as well.
MXSteel said:
That's how the last owner left it. Considering it didn't even work, I doubt you'd want to get back to that, not to mention TWRP is way better.
Click to expand...
Click to collapse
You are misunderstanding. The issue is not that stock recovery is "not working". Stock recovery is working as it should. Stock recovery is not for flashing custom ROMs and mods; it only works to flash specific items, such as official OTAs.
But the fact that the previous owner has a custom ROM installed, but stock recovery is a bit odd. Previous owner must have had custom recovery installed at one point, then installed stock recovery back to the device. Might be a botched attempt to return to stock before selling/trading with you.
MXSteel said:
I assume if you factory reset all the phone, it'll probably return you to stock recovery mode as well.
Click to expand...
Click to collapse
That assumption would be incorrect. "Factory reset" is a bit of a misnomer, all it does is delete the user data (/data) partition and cache. ROM, recovery, and everything else is actually untouched.
Also, the reason I ask is that factory reset in bootloader should never be done on a modded phone. There is a bug which corrupts the internal memory if you do so. If you want/need to ever do a factory reset, then do so either within the OS (in Settings) or in recovery. Reason I ask if this was done, was to try to troubleshoot your error message (mount SD failed), but as the phone apparently was placed in its current state by the previous owner, we don't really have a way of knowing.
What is the status of the phone as given in bootloader? Is the bootloader unlocked, relocked or locked? S-on or S-off?
redpoint73 said:
You are misunderstanding. The issue is not that stock recovery is "not working". Stock recovery is working as it should. Stock recovery is not for flashing custom ROMs and mods; it only works to flash specific items, such as official OTAs.
But the fact that the previous owner has a custom ROM installed, but stock recovery is a bit odd. Previous owner must have had custom recovery installed at one point, then installed stock recovery back to the device. Might be a botched attempt to return to stock before selling/trading with you.
That assumption would be incorrect. "Factory reset" is a bit of a misnomer, all it does is delete the user data (/data) partition and cache. ROM, recovery, and everything else is actually untouched.
Also, the reason I ask is that factory reset in bootloader should never be done on a modded phone. There is a bug which corrupts the internal memory if you do so. If you want/need to ever do a factory reset, then do so either within the OS (in Settings) or in recovery. Reason I ask if this was done, was to try to troubleshoot your error message (mount SD failed), but as the phone apparently was placed in its current state by the previous owner, we don't really have a way of knowing.
What is the status of the phone as given in bootloader? Is the bootloader unlocked, relocked or locked? S-on or S-off?
Click to expand...
Click to collapse
The bootloader was unlocked (and "Tempered"),and it's currently S-On, and I dont have any reason to change that. And of course, I wouldn't do a factory reset from bootloader or anywhere else, certainly not after all the trouble I went through installing TWRP and all the android SDK stuff to flash it.
MXSteel said:
And of course, I wouldn't do a factory reset from bootloader or anywhere else, certainly not after all the trouble I went through installing TWRP and all the android SDK stuff to flash it.
Click to expand...
Click to collapse
Again, you are misunderstanding what factory reset does. It only wipes the /data partition (user data) and doesn't even touch the other partitions including recovery.
redpoint73 said:
Yes, red triangle is stock recovery. Any idea how you got back to that?
Did you factory reset in bootloader, by any chance?
Click to expand...
Click to collapse
if you can still boot up into the phone i would download the newest full rom from viper. which is now 1.7.1. then i would restart into recovery run the viper install and just start from scratch. since you bought the phone used who knows whats still left on there. in the aroma there should be an option to wipe the phone before install. that will ensure a clean install and then you can OTA to the new 1.8.0. for some odd reason he has produced a full 1.8.0 rom but its not that big of a deal.
syaoran68 said:
in the aroma there should be an option to wipe the phone before install. that will ensure a clean install
Click to expand...
Click to collapse
Full wipe options are also available in custom recovery. Data, cache and Dalvik is usually all that is needed to be wiped.
32gb variant (H790).
I tried most of the solutions I've seen on this subforum so far - including doing a full flash-all.sh command as well as the flashing of individual files into my system.
So far I've been able to do so using the stock images from Google (Android N). However, I can never get Recovery to boot and my phone will not boot past "Google." (Not even the colorful animations show).
I am not sure what I can do - I unfortunately got this phone via a 3rd party and not Google's Store, so I'm not sure if they would honor an RMA request (maybe if I said it was a gift they would relent?).
I was reading this thread: http://forum.xda-developers.com/nexus-5x/help/req-help-to-unbrick-t3251740 and realized that this might be my last alternative, but I'm a bit concerned about going through all of this without giving it one more chance having access to at least the bootloader screen.
Does anyone have any suggestions on what I might be doing wrong? Should I attempt to flash the latest Android 6.0 image instead?
Is your boot loader locked? How did you flash the stock images?
Reboot into fastboot, run the flash all, reboot back to your bootloader when it's done and it. These commands....
Fastboot format cache
Fastboot format userdata
Then restart the phone
Corrupted bootloader partition, your phone is little piece of brick. EXT4 is the motive, HAHAHA.
I lost a ****ty device like you too.
Now i learned: (IF IS EXT4 , NO!)
Sent from my XT687 using xda premium
I am able to unlock bootloader. I flashed using both flash all as well as individual img at a time like described in this: http://forum.xda-developers.com/nexus-5x/general/guides-how-to-guides-beginners-t3206930
I ran format cache and userdata (which I think the full flash also does). I am unable to go past the Google screen.
I was able to reflash my rom again too, without errors, but the **** recused to boot up or boot recovery, your phone is death like the apocalyptical beast google inc!
Sent from my XT687 using xda premium
dcxgod said:
I am able to unlock bootloader. I flashed using both flash all as well as individual img at a time like described in this: http://forum.xda-developers.com/nexus-5x/general/guides-how-to-guides-beginners-t3206930
I ran format cache and userdata (which I think the full flash also does). I am unable to go past the Google screen.
Click to expand...
Click to collapse
Can you get TWRP installed via fastboot and boot into that?
Sent from my Nexus 5X using Tapatalk
Use the lg tot file method to recover. It has worked for some.
Sent from my Nexus 5X using Tapatalk
Try to flash TWRP with fasboot and see if you can boot it. There's an actual problem with the last versions of TWRP (TWRP 3.0.2-1 and 3.0.2-2), where if you backup then restore an EFS partition you end up with a phone where it doesn't get past the Google Screen (or crashes in the first frame of the bootanimation), lk panic apparently due to EFS corruption.
If this is your case (derped restoring EFS like that) and you can flash and boot on TWRP, try to flash TWRP 3.0.2-0 and restore and old backup of EFS.
maybe same problem
I have the same problem.
Before i flash manually my phone into android 7(factory image) it was rooted and unlock bootloader. I locked the bootloader again and until here everything works fine. I flashed the stock recovery mode by TWRP. after that the phone won't boot android and stock recovery mode. everything was lost except the bootloader.
I tried lots of tricks but don't answer(sideload ota update, format cache and userdata). I tried to flash stock recovery or custom recovery but i couldn't because in the process the phone restart and restart again and again. Even doesn't work temporarily boot, custom and stock recovery mode and phone has no reaction.
I only have access to the bootloader.
Would you have any suggestion?
*ps: When phone is boot up just shows a white google logo and after that shows a green bot with red alert and a message(no command) . In this point phone restart suddenly and the same process is repeated.