Hey,
i just re-rooted my One after updating to 38r some days ago, and as it booted up, i got the "audiofx has stopped" bug and the "CM Lockscreen has stopped" bug at the same time. i tried to reset with twrp, reflash the rom and whatnot. I also cant flash roms with toolkits as i can not unlock my Bootloader. Today i finally managed to install a modified 38r via USB Otg after some other rom installations failed (also with USB Otg). I'm all like "Hell Yeah, fvck yeah OnePlus support!" (I wrote to them some days ago but they have not replied). I euphorically booted up my device and waited until the cyanogenmod logo pops up. i waited all the time. And its in a Bootloop now. I tried resetting my device and reflashing the ROM but none works. Can anyone help me please?
Sorry for the typos, i got not much time right now so i had to type fast.
thanks in advance
Have you tried a full wipe and clean flash of 38R?
Transmitted via Bacon
as i can not unlock my Bootloader
Click to expand...
Click to collapse
Could you please elaborate on this? You obviously already have a custom (TWRP) recovery, so you either flashed when sideloading was still possible or your bootloader is unlocked.
also cant flash roms with toolkits
Click to expand...
Click to collapse
A word of advise about using toolkits: don't. _Especially_ not if your phone has already issues as toolkits more often than not run the commands without checking (error) outputs. This has led to disastrous results for some people in the past so be careful!
I can recommend trying to re-flash the 38R via Fastboot after formatting the relevant partitions (cache, system ) to make sure you start from scratch.
d4fseeker said:
Could you please elaborate on this? You obviously already have a custom (TWRP) recovery, so you either flashed when sideloading was still possible or your bootloader is unlocked.
A word of advise about using toolkits: don't. _Especially_ not if your phone has already issues as toolkits more often than not run the commands without checking (error) outputs. This has led to disastrous results for some people in the past so be careful!
I can recommend trying to re-flash the 38R via Fastboot after formatting the relevant partitions (cache, system ) to make sure you start from scratch.
Click to expand...
Click to collapse
He can't flash via fastboot is his bootloader is locked. He'll have to just flash the recovery flashable version via TWRP.
Transmitted via Bacon
timmaaa said:
He can't flash via fastboot is his bootloader is locked. He'll have to just flash the recovery flashable version via TWRP.
Click to expand...
Click to collapse
That's why I asked for elaboration on his bootloader state and fastboot issues. Flashing with fastboot close to _always_ works unless the bootloader is borked which does not seem to be the case as he can at least start the recovery environment. "Does not work" is a rather broad subject from "I don't know how to do it" over "I don't get it working" up to "it shows an error".
d4fseeker said:
That's why I asked for elaboration on his bootloader state and fastboot issues. Flashing with fastboot close to _always_ works unless the bootloader is borked which does not seem to be the case as he can at least start the recovery environment. "Does not work" is a rather broad subject from "I don't know how to do it" over "I don't get it working" up to "it shows an error".
Click to expand...
Click to collapse
Fair enough, although for someone who's inexperienced I think using the flashable version will be an easier and quicker solution.
Transmitted via Bacon
timmaaa said:
Have you tried a full wipe and clean flash of 38R?
Transmitted via Bacon
Click to expand...
Click to collapse
d4fseeker said:
Could you please elaborate on this? You obviously already have a custom (TWRP) recovery, so you either flashed when sideloading was still possible or your bootloader is unlocked.
A word of advise about using toolkits: don't. _Especially_ not if your phone has already issues as toolkits more often than not run the commands without checking (error) outputs. This has led to disastrous results for some people in the past so be careful!
I can recommend trying to re-flash the 38R via Fastboot after formatting the relevant partitions (cache, system ) to make sure you start from scratch.
Click to expand...
Click to collapse
My bootloader is locked, as said. And i use toolkits because i experienced some bugs with the commands on Win8.1.
try...
TWRP.. Terminal Line..
make_ext4fs /dev/block/mmcblk0p15
Crime_Monkey said:
My bootloader is locked, as said. And i use toolkits because i experienced some bugs with the commands on Win8.1.
Click to expand...
Click to collapse
I can't help you if you don't even provide answers to specific questions you've been asked such as how TWRP got on the phone and why you "cannot" unlock your bootloader.
Do please note however that toolkits are not magical software, they just provide a nice clickable wrapper around the same low-level drivers and software such as adb and fastboot. If either of those have issues, so will the toolkits. And that's exactly where my word of caution kicks in; they often don't notice something went wrong. Worst-case you end up with a dead phone which I'm trying to avoid.
d4fseeker said:
I can't help you if you don't even provide answers to specific questions you've been asked such as how TWRP got on the phone and why you "cannot" unlock your bootloader.
Do please note however that toolkits are not magical software, they just provide a nice clickable wrapper around the same low-level drivers and software such as adb and fastboot. If either of those have issues, so will the toolkits. And that's exactly where my word of caution kicks in; they often don't notice something went wrong. Worst-case you end up with a dead phone which I'm trying to avoid.
Click to expand...
Click to collapse
I installed twrp with the toolkit by @manudroid19 when my phone was still functionable.
And the toolkit says that my bootloader is locked and i cannot unlock it. Every time i try to unlock it with the toolkit when in fastboot mode, the phone just boots up to twrp.
Have you tried the instructions in this thread:
http://forum.xda-developers.com/oneplus-one/help/fix-brickloop-audio-fx-fc-efs-corrupt-t2879061
r0ni3 said:
try...
TWRP.. Terminal Line..
make_ext4fs /dev/block/mmcblk0p15
Click to expand...
Click to collapse
I can not find the folder, with and without an OS installed.
Crime_Monkey said:
I can not find the folder, with and without an OS installed.
Click to expand...
Click to collapse
no folder ..
you just have to write that command
r0ni3 said:
no folder ..
you just have to write that command
Click to expand...
Click to collapse
I can't find this option in twrp either.
Crime_Monkey said:
I can't find this option in twrp either.
Click to expand...
Click to collapse
twrp version?
Advanced -> Terminal Command -> Click on SELECT
and write
make_ext4fs /dev/block/mmcblk0p15
r0ni3 said:
twrp version?
Advanced -> Terminal Command -> Click on SELECT
and write
make_ext4fs /dev/block/mmcblk0p15
Click to expand...
Click to collapse
I am on 2.8.0.1., after executing the command i tried to install the stock 38r update, failed.
Crime_Monkey said:
I am on 2.8.0.1., after executing the command i tried to install the stock 38r update, failed.
Click to expand...
Click to collapse
installa a nightly...
and gapps
you can adb push roms in twrp, so you dont have to resort to otg.
Related
deleted htc framework file and phone doesnot start.
After rooted my htc One X. In the process of removing at&t crap ware I accidentally deleted something that said htc frame work.
From then on my phone would not start. I unlocked my phone as well. How ever I didnot have any custom ROM installed or didnot have any back up done.
When I tried to reboot my phone after deleting the htc frame work file, it would not start. HTC icon would show up and it would not go further.
These are the things I did.
1. I flashed CWM.
2.I flashed TWRP.
3.I finally flashed CWM. 5.8.3
Then I went to fastboot mode and
removed Dalvik Cache, Erased the sd card
and tried to 'mount usb storage' but it would say
"unable to open ums lunfile(no such file or directory)SD card space free:10169MB"
My phone though shows as a removable disk , when i click on the icon it would say " Please insert disk into removable disk." I tried to save a custom ROM on my memory card and flash it but my system doesnot detect my phone.
Can some one please help me?
Thank you.
HTC Framework is part of the OS. You deleted part of the OS.
Install TWRP and mount USB, then load a custom ROM or one of the rooted stock ROMs in the Development forum.
Alternately, relock the bootloader and run the RUU.
Lock bootloader run ruu start over. Next time the very first thing you do is make a nandroid back up.
redpoint73 said:
HTC Framework is part of the OS. You deleted part of the OS.
Install TWRP and mount USB, then load a custom ROM or one of the rooted stock ROMs in the Development forum.
Alternately, relock the bootloader and run the RUU.
Click to expand...
Click to collapse
Thanks for the quick reply.
When I tried to mount my phone as usb it would not. I mentioned that as well.
briefmobile (dot) com/download-att-htc-one-x-stock-ruu
i found this link online. Without installing a custom ROM and run RUU , do you think my phone works
Adding a note to it. my phone is s-on and did not have android sdk installed on my machine. i tried all this using fastboot files and twrp img.
Thank You
in00b said:
When I tried to mount my phone as usb it would not.
Click to expand...
Click to collapse
You mentioned you tried to mount USB using fastboot (I've never mounted USB using fastboot, so I can't comment on that). Try mounting USB within TWRP, and see if that works. FYI, the USB mount feature in CWM does not work, and CWM does not really support our device, and has major issues. That's why its strongly recommended you use TWRP and not CWM.
in00b said:
briefmobile (dot) com/download-att-htc-one-x-stock-ruu
i found this link online.
Click to expand...
Click to collapse
Website seems to be too busy now. As long as its not 2.20, it should be okay. Normally, I would caution against randomly searching around the internet for things and flashing them, and instead getting them here instead. But briefmobile is Kenneth Penn's website, and he is a known developer on XDA.
in00b said:
Without installing a custom ROM and run RUU , do you think my phone works
Click to expand...
Click to collapse
You deleted part of the OS, so I'd say no. It doesn't boot does it? Then it doesn't work.
Also, please click "Thanks" to the post that help you.
the link you sent really helps. i flashed twrp then cwm then twrp. does it matter somehow flashing these things multiple times?
in00b said:
the link you sent really helps. i flashed twrp then cwm then twrp. does it matter somehow flashing these things multiple times?
Click to expand...
Click to collapse
No, you can only have one recovery. Flash one, you overwrite whatever you had before.
in00b said:
the link you sent really helps. i flashed twrp then cwm then twrp. does it matter somehow flashing these things multiple times?
Click to expand...
Click to collapse
I'd stay away from CWM. I know it used to cause problems, but I don't know if it does anymore.
Most everybody here (in the One XL forums) prefer TWRP anyways.
Thanks for you time everybody.
This is what I did last night.
Downloaded a RUU from here http://forum.xda-developers.com/showthread.php?t=1671237
and put my phone in the fastboot usb mode and ran RUU.
After a while my phone would have a blank screen with glowing "htc" logo on it, as shown in the RUU utility.
Nothing happens and my phone is still in the state of brick.
Thank You
in00b said:
Thanks for you time everybody.
This is what I did last night.
Downloaded a RUU from here http://forum.xda-developers.com/showthread.php?t=1671237
and put my phone in the fastboot usb mode and ran RUU.
After a while my phone would have a blank screen with glowing "htc" logo on it, as shown in the RUU utility.
Nothing happens and my phone is still in the state of brick.
Thank You
Click to expand...
Click to collapse
Did you lock your bootloader before running the RUU?
Butters619 said:
Did you lock your bootloader before running the RUU?
Click to expand...
Click to collapse
nope my phone was boot loader unlocked and s-on.
in00b said:
nope my phone was boot loader unlocked and s-on.
Click to expand...
Click to collapse
You must relock your bootloader temporarily or the RUU will fail. As long as you have your unlock token you can re-unlock once you RUU.
When you are in fastboot, type "fastboot oem lock"
Once it's locked, run the RUU.
Once that is done, re-unlock by flashing the token.
Butters619 said:
You must relock your bootloader temporarily or the RUU will fail. As long as you have your unlock token you can re-unlock once you RUU.
When you are in fastboot, type "fastboot oem lock"
Once it's locked, run the RUU.
Once that is done, re-unlock by flashing the token.
Click to expand...
Click to collapse
thanks i will try unlocking my phone and get back to you.
in00b said:
how do i relock my phone.that doesnt turn on at all. all i see is htc screen and it wouldnt go any further.
Click to expand...
Click to collapse
Go in to bootloader. You already said you were able to do that. Hold down the volume key when you boot your phone, go into bootloader, run the fastboot command.
Gunny stated that BL had to be locked at the start of the thread. Does anyone ever read anymore? I mean, seriously....
qwertyaas said:
Gunny stated that BL had to be locked at the start of the thread. Does anyone ever read anymore? I mean, seriously....
Click to expand...
Click to collapse
This is like the 3rd or 4th thread in the past couple weeks that Gunny or redpoint has told the OP to relock and RUU but they said it wasn't working still. And then I've come in and said they have to relock and the OP hadn't done it yet. So no, apparently people don't read lol.
But in almost every thread things have to be said 2-3 times which is ridiculous
Butters619 said:
Go in to bootloader. You already said you were able to do that. Hold down the volume key when you boot your phone, go into bootloader, run the fastboot command.
Click to expand...
Click to collapse
I cannot tell you how great ful Iam to the entire Android community . Thank you very much. problem solved.
This is what I did.
Went into fast boot.
typed fastboot
and typed fastboot oem lock -- to lock the phone.
Then I downloaded a RUU utility and ran it. My phone works superfine now.
Again. Thank You- All I can say.
in00b said:
I cannot tell you how great ful Iam to the entire Android community . Thank you very much. problem solved.
This is what I did.
Went into fast boot.
typed fastboot
and typed fastboot oem lock -- to lock the phone.
Then I downloaded a RUU utility and ran it. My phone works superfine now.
Again. Thank You- All I can say.
Click to expand...
Click to collapse
See that thanks button. Go through this entire thread and press it for everyone who helped you (aka everyone). Especially gunny.
And remember, things that sound important (framework, build., etc...) typically are important random assassinations typically get the shooter in trouble
18th.abn said:
random assassinations typically get the shooter in trouble
Click to expand...
Click to collapse
lol
---------- Post added at 10:25 AM ---------- Previous post was at 10:24 AM ----------
Butters619 said:
This is like the 3rd or 4th thread in the past couple weeks that Gunny or redpoint has told the OP to relock and RUU but they said it wasn't working still. And then I've come in and said they have to relock and the OP hadn't done it yet. So no, apparently people don't read lol.
Click to expand...
Click to collapse
Maybe he's more a fan of the Butters cartoon character than he is Totoro?
im trying to get back to complete stock to start over again because i cant get help with my 'no signal problem' but it wont start my factory restore even though i am using the right img.
the issues started when i tried to install Cataclysm (http://forum.xda-developers.com/showthread.php?t=2518660) they have a thing in there saying that its a known problem to not get signal when flashing twrp
(My mobile signal/radio isn't working anymore!
- There's a bug with TWRP that remove/corrupt your baseband during flash. Please refer to the twrp team for a fix.)
no link and i cant find it on google so any help would be appreciated
image attached its the error when trying to restore the factory image.
dudekiller said:
im trying to get back to complete stock to start over again because i cant get help with my 'no signal problem' but it wont start my factory restore even though i am using the right img.
the issues started when i tried to install Cataclysm (http://forum.xda-developers.com/showthread.php?t=2518660) they have a thing in there saying that its a known problem to not get signal when flashing twrp
(My mobile signal/radio isn't working anymore!
- There's a bug with TWRP that remove/corrupt your baseband during flash. Please refer to the twrp team for a fix.)
no link and i cant find it on google so any help would be appreciated
image attached its the error when trying to restore the factory image.
Click to expand...
Click to collapse
You can always try the second method for the "BACK TO STOCK" guide from here:
http://forum.xda-developers.com/showthread.php?t=2513701
Even better you can use the instructions from the second post of that thread to wipe clean all your partitions prior to flashing them via fastboot.
quendil said:
You can always try the second method for the "BACK TO STOCK" guide from here:
http://forum.xda-developers.com/showthread.php?t=2513701
Even better you can use the instructions from the second post of that thread to wipe clean all your partitions prior to flashing them via fastboot.
Click to expand...
Click to collapse
im still getting invalid bootloader img
dudekiller said:
im still getting invalid bootloader img
Click to expand...
Click to collapse
have you extracted all the images on C:/image-hammerhead-krt16m like the example?
Have you renamed "bootloader-hammerhead-XXXXXX.img" to "bootloader.img" and "radio-hammerhead-XXXXXX.img" to "radio.img"?
quendil said:
have you extracted all the images on C:/image-hammerhead-krt16m like the example?
Have you renamed "bootloader-hammerhead-XXXXXX.img" to "bootloader.img" and "radio-hammerhead-XXXXXX.img" to "radio.img"?
Click to expand...
Click to collapse
yes, it seems that twrp corrupted something and it doesnt recognize the device anymore.
dudekiller said:
yes, it seems that twrp corrupted something and it doesnt recognize the device anymore.
Click to expand...
Click to collapse
Oh damn...
On bootloader when you give the command fastboot devices does it show you anything?
i wonder if the TWRP bug is why i was getting bootloop when flashing Bootanimations the other day?
Wug's Nexus toolkit has been my lifeline with 4 nexus devices.
alright guys i figured it out i did a oem lock and unlock and then the factory image worked so im stock right now... it might stay that way for a bit.. lol
comicbookguy72 said:
Wug's Nexus toolkit has been my lifeline with 4 nexus devices.
Click to expand...
Click to collapse
and this is the problem with pretty much everything. people relying on toolkits, then when something screws up, they have no idea what happened.
Zepius said:
and this is the problem with pretty much everything. people relying on toolkits, then when something screws up, they have no idea what happened.
Click to expand...
Click to collapse
his first priority is fixing it. his second priority is possibly finding out why he borked it and not making the same mistake again. i've borked stuff learning and fixed it with toolkits.
not everyone wants to learn ADB or fastboot commands, or install the SDK, and NOT EVERYONE HAS TO. not everyone is a would-be developer
dudekiller said:
they have a thing in there saying that its a known problem to not get signal when flashing twrp
(My mobile signal/radio isn't working anymore!
- There's a bug with TWRP that remove/corrupt your baseband during flash. Please refer to the twrp team for a fix.)
Click to expand...
Click to collapse
So why did you flash via TWRP then?
Han Solo 1 said:
So why did you flash via TWRP then?
Click to expand...
Click to collapse
i didnt go through the faqs before installing, i looked at the rom and what it offered. it said stable so i wasnt to worried about bugs since i was coming from cm11
Some back story. My N5 was stock/rooted, with stock recovery. I had installed the beta Xposed framework, using this post as a guide. Following the install, during the reboot, my phone never restarted. Since then it has not been able to turn on.
Things I have tried:
I have done method 1 & 2 of this guide
I am able to lock and unlock the bootloader, it is currently locked.
I have tried the command fastboot -w
I am unable to perform a factory reset, it hangs at /data
If there is any ideas as to what I should do next, please don't hesitate to let me know.
If I am able to get the Tamper Flag reset, then my plan is to look into the RMA option.
Also, I have been following this thread for info.
jimburke57 said:
Some back story. My N5 was stock/rooted, with stock recovery. I had installed the beta Xposed framework, using this post as a guide. Following the install, during the reboot, my phone never restarted. Since then it has not been able to turn on.
Things I have tried:
I have done method 1 & 2 of this guide
I am able to lock and unlock the bootloader, it is currently locked.
I have tried the command fastboot -w
I am unable to perform a factory reset, it hangs at /data
If there is any ideas as to what I should do next, please don't hesitate to let me know.
If I am able to get the Tamper Flag reset, then my plan is to look into the RMA option.
Also, I have been following this thread for info.
Click to expand...
Click to collapse
when you unlock the phone, and reboot the bootloader, does it stay locked or is it unlocked?
Zepius said:
when you unlock the phone, and reboot the bootloader, does it stay locked or is it unlocked?
Click to expand...
Click to collapse
So earlier when i did this, the phone would freeze. Now it went through with it, and is now showing the animated android images, with a moving bar at the bottom. It has been there for about 4 minutes now.
jimburke57 said:
So earlier when i did this, the phone would freeze. Now it went through with it, and is now showing the animated android images, with a moving bar at the bottom. It has been there for about 4 minutes now.
Click to expand...
Click to collapse
this still does not answer my question.
it sounds like your phone is not dead however. please follow the return to stock thread in the general forum and you should be ok.
Zepius said:
this still does not answer my question.
it sounds like your phone is not dead however. please follow the return to stock thread in the general forum and you should be ok.
Click to expand...
Click to collapse
I have followed it already. The images on the first post are my result.
It is showing as unlocked at the booloader and on fastboot oem device-info.
follow the 2nd post, not the 2nd method in this thread and tell us the results.
http://forum.xda-developers.com/showthread.php?t=2513701
Zepius said:
follow the 2nd post, not the 2nd method in this thread and tell us the results.
http://forum.xda-developers.com/showthread.php?t=2513701
Click to expand...
Click to collapse
Same thing as before. All of the erase commands get processed, but when it gets the the system.img it fails to write it.
I think you've done her in. Can you get into recovery? You might be able to push the tamper zip and then run it in recovery.
jd1639 said:
I think you've done her in. Can you get into recovery? You might be able to push the tamper zip and then run it in recovery.
Click to expand...
Click to collapse
I am able to access recovery. This is exactly what I am trying to do at the moment, but now I cannot adb sideload the zip. For some reason the N5 is not being recognized by windows.
jimburke57 said:
I am able to access recovery. This is exactly what I am trying to do at the moment, but now I cannot adb sideload the zip. For some reason the N5 is not being recognized by windows.
Click to expand...
Click to collapse
Use Galaxy Nexus drivers, and make sure you have updated the SDK for the latest adb.
orangekid said:
Use Galaxy Nexus drivers, and make sure you have updated the SDK for the latest adb.
Click to expand...
Click to collapse
Are you talking about these drivers?
jimburke57 said:
Are you talking about these drivers?
Click to expand...
Click to collapse
No, I have had success getting the Nexus 5 working on ADB with the Samsung Galaxy Nexus drivers. Don't ask me why, but it works for me.
orangekid said:
No, I have had success getting the Nexus 5 working on ADB with the Samsung Galaxy Nexus drivers. Don't ask me why, but it works for me.
Click to expand...
Click to collapse
So an update, I am able to sideload the zip in recovery, however, during the install, it fails.
jimburke57 said:
So an update, I am able to sideload the zip in recovery, however, during the install, it fails.
Click to expand...
Click to collapse
Have you tried flashing stock kitkat (from google) via fastboot?
orangekid said:
Have you tried flashing stock kitkat (from google) via fastboot?
Click to expand...
Click to collapse
yes, many times
So this is just a shot in the dark, but the fastboot command screenshot you posted, you had the command "fastboot flash bootloader."
I haven't read the articles you're using, but is there a reason you're flashing a bootloader after unlocking it? Wouldn't that just lock the bootloader again?
I'd start fastboot oem unlock, fastboot flash recovery, and then adb sideload the .zip you are using once you're in recovery.
Good luck.
pantlessjim said:
So this is just a shot in the dark, but the fastboot command screenshot you posted, you had the command "fastboot flash bootloader."
I haven't read the articles you're using, but is there a reason you're flashing a bootloader after unlocking it? Wouldn't that just lock the bootloader again?
I'd start fastboot oem unlock, fastboot flash recovery, and then adb sideload the .zip you are using once you're in recovery.
Good luck.
Click to expand...
Click to collapse
I am just following the guide for How to return to stock. But to answer your question, no it does not re-lock the bootloader.
Here is some additional information. When I perform a factory reset in recovery it freezes while formatting /data. And when flashing the stock images, I am able to flash everything successfully except for the system.img
jimburke57 said:
I am just following the guide for How to return to stock. But to answer your question, no it does not re-lock the bootloader.
Click to expand...
Click to collapse
Have you tried just dirty flashing stock / rooted thru recovery?
edit: or restoring a backup?
Hi Guys
Originally unlocked and rooted my nexus 5. Then the OTA update seemed to remove the root. I havent really looked into re-rooting but i need to wipe the device and I thought I may as well do it now. Having issue though
- Device is still unlocked when I go into the bootloader I see its unlocked
- Try to flash a custom recovery and when I follow the steps it goes to red exclamation (Im assuming meaning corrupt custom recovery, probably the old CWM before the OTA)
- Read through forums and they say I need to remove reboot-from-recovery.p file from the /system
- however I cant remove it without root and I cant get root without removing it
Whats the options here?
Thanks
SORRY JUST REALISED THIS SHOULD BE IN Q&A
luppas said:
Hi Guys
Originally unlocked and rooted my nexus 5. Then the OTA update seemed to remove the root. I havent really looked into re-rooting but i need to wipe the device and I thought I may as well do it now. Having issue though
- Device is still unlocked when I go into the bootloader I see its unlocked
- Try to flash a bootloader and when I follow the steps it goes to red exclamation (Im assuming meaning corrupt bootloader, probably the old CWM before the OTA)
- Read through forums and they say I need to remove reboot-from-recovery.p file from the /system
- however I cant remove it without root and I cant get root without removing it
Whats the options here?
Than
Click to expand...
Click to collapse
hi, you're asking in the general section. which is wrong.
Just flash custom recovery again via fastboot and SuperSu via custom recovery http://forum.xda-developers.com/goo...ide-nexus-5-how-to-unlock-bootloader-t2507905
luppas said:
Hi Guys
Originally unlocked and rooted my nexus 5. Then the OTA update seemed to remove the root. I havent really looked into re-rooting but i need to wipe the device and I thought I may as well do it now. Having issue though
- Device is still unlocked when I go into the bootloader I see its unlocked
- Try to flash a bootloader and when I follow the steps it goes to red exclamation (Im assuming meaning corrupt bootloader, probably the old CWM before the OTA)
- Read through forums and they say I need to remove reboot-from-recovery.p file from the /system
- however I cant remove it without root and I cant get root without removing it
Whats the options here?
Than
Click to expand...
Click to collapse
the exclamation point is the stock recovery. once you take in an ota, it removes both root and your custom recovery. to get your custom recovery back so that you can flash a bootloader(and the supersu root binaries). you can flash a custom recovery while youre in your bootloader via fastboot on your desktop.
GUGUITOMTG4 said:
hi, you're asking in the general section. which is wrong.
Just flash custom recovery again via fastboot and SuperSu via custom recovery http://forum.xda-developers.com/goo...ide-nexus-5-how-to-unlock-bootloader-t2507905
Click to expand...
Click to collapse
Yeah just realised that. Sorry its my first post
luppas said:
Hi Guys
Originally unlocked and rooted my nexus 5. Then the OTA update seemed to remove the root. I havent really looked into re-rooting but i need to wipe the device and I thought I may as well do it now. Having issue though
- Device is still unlocked when I go into the bootloader I see its unlocked
- Try to flash a custom recovery and when I follow the steps it goes to red exclamation (Im assuming meaning corrupt custom recovery, probably the old CWM before the OTA)
- Read through forums and they say I need to remove reboot-from-recovery.p file from the /system
- however I cant remove it without root and I cant get root without removing it
Whats the options here?
Thanks
SORRY JUST REALISED THIS SHOULD BE IN Q&A
Click to expand...
Click to collapse
why don't you try twrp maybe you can flash twrp then remove the file then go back to cwm
Sent from my Nexus 5 using Tapatalk
luppas said:
Hi Guys
Originally unlocked and rooted my nexus 5. Then the OTA update seemed to remove the root. I havent really looked into re-rooting but i need to wipe the device and I thought I may as well do it now. Having issue though
- Device is still unlocked when I go into the bootloader I see its unlocked
- Try to flash a custom recovery and when I follow the steps it goes to red exclamation (Im assuming meaning corrupt custom recovery, probably the old CWM before the OTA)
- Read through forums and they say I need to remove reboot-from-recovery.p file from the /system
- however I cant remove it without root and I cant get root without removing it
Whats the options here?
Thanks
SORRY JUST REALISED THIS SHOULD BE IN Q&A
Click to expand...
Click to collapse
just read this again..when you are flash a custom recovery, and it still goes to the exclamation point, it means that you arent flashing the custom recovery right. its.. fastboot flash recovery recoveryname.img
GUGUITOMTG4 said:
hi, you're asking in the general section. which is wrong.
Just flash custom recovery again via fastboot and SuperSu via custom recovery http://forum.xda-developers.com/goo...ide-nexus-5-how-to-unlock-bootloader-t2507905
Click to expand...
Click to collapse
Thats what I was trying to explain. I tried flashing custom recovery as per instructions but nothing happens. From what I am reading this is because of the reboot-from-recovery.p file which needs to be deleted BUT I cannot do this without root!
luppas said:
Thats what I was trying to explain. I tried flashing custom recovery as per instructions but nothing happens. From what I am reading this is because of the reboot-from-recovery.p file which needs to be deleted BUT I cannot do this without root!
Click to expand...
Click to collapse
na, you dont need to delete that to flash a custom recovery(i never have, in my 6 years with android, and all my devices). is fastboot seeing your device? kkdo you see fastboot going through the process of flashing a recovery? if you are typing it right, and fastboot sees your device, you would have flashed a custom recovery. when you connect to fastboot, type.. fastboot devices. if it sees your device, its id number will be shown.
simms22 said:
just read this again..when you are flash a custom recovery, and it still goes to the exclamation point, it means that you arent flashing the custom recovery right. its.. fastboot flash recovery recoveryname.img
Click to expand...
Click to collapse
C:\Users\user\Downloads\android-sdk-windows\platform-tools>fastboot flash recovery recovery.img
I have it right mate. But nothing seems to be happening. Maybe drivers issue? When I do adb version I get the version so I assumed that means its working
luppas said:
C:\Users\user\Downloads\android-sdk-windows\platform-tools>fastboot flash recovery recovery.img
I have it right mate. But nothing seems to be happening. Maybe drivers issue? When I do adb version I get the version so I assumed that means its working
Click to expand...
Click to collapse
adb version and fastboot devices is different. adb is not fastboot and you can not use adb as fastboot. fastboot is fastboot.
simms22 said:
na, you dont need to delete that to flash a custom recovery(i never have, in my 6 years with android, and all my devices). is fastboot seeing your device? kkdo you see fastboot going through the process of flashing a recovery? if you are typing it right, and fastboot sees your device, you would have flashed a custom recovery. when you connect to fastboot, type.. fastboot devices. if it sees your device, its id number will be shown.
Click to expand...
Click to collapse
Yeah you were right. Driver issue. fastboot devices showed nothing. Reinstalled drivers and looks to be good now.
Thanks guys sorry for the post in wrong area
luppas said:
Yeah you were right. Driver issue. fastboot devices showed nothing. Reinstalled drivers and looks to be good now.
Thanks guys sorry for the post in wrong area
Click to expand...
Click to collapse
glad you got it
So, I got my Photon Q today and I've already unlocked it and I was trying to install TWRP but I messed up somehow.. It still boots into the stock Android ROM and works fine but whenever I try to go into the recovery/Fastboot (Whatever it's called) I get this screen with some info text. At the bottom it says this:
Failed to hab check for recovery: 0x56
Fastboot Reason: Boot Failure
Whenever I try to flash a recovery with an app it always succeeds but I still get this screen when I try to go into the recovery. Help me.
Have you tried doing 'fastboot flash recovery recovery.img' instead of using 'apps' to flash recovery?
arrrghhh said:
Have you tried doing 'fastboot flash recovery recovery.img' instead of using 'apps' to flash recovery?
Click to expand...
Click to collapse
I have. It says "Preflash validation failed" and nothing on the phone changes. This is really frustrating.
Cwazywazy said:
I have. It says "Preflash validation failed" and nothing on the phone changes. This is really frustrating.
Click to expand...
Click to collapse
Where do you get this error? I've never heard of fastboot spitting out such an error...
I assume you're in fastboot mode when you try this? What does 'fastboot devices' output?
arrrghhh said:
Where do you get this error? I've never heard of fastboot spitting out such an error...
I assume you're in fastboot mode when you try this? What does 'fastboot devices' output?
Click to expand...
Click to collapse
Nevermind, I figured out how to unlock the bootloader and TWRP finally installed successfully.
The only rooting/custom ROM stuff I've done is with my Nexus 7 and that wasn't as hard as this was.
Cwazywazy said:
Nevermind, I figured out how to unlock the bootloader and TWRP finally installed successfully.
The only rooting/custom ROM stuff I've done is with my Nexus 7 and that wasn't as hard as this was.
Click to expand...
Click to collapse
Oh, your bootloader was still locked...
That would do it! Glad you got it working. I hadn't seen that message before, but it makes sense now why I've never seen it before . My Q was unlocked immediately after unboxing!
arrrghhh said:
Oh, your bootloader was still locked...
That would do it! Glad you got it working. I hadn't seen that message before, but it makes sense now why I've never seen it before . My Q was unlocked immediately after unboxing!
Click to expand...
Click to collapse
I have a new problem.. I flashed the latest stable CyanogenMod and it wouldn't boot. (Boot animation just kept on going) So I went into TWRP and tried to do a wipe. For some reason it says "Unable to mount /data" or "internal storage". Even if I go into advanced wipe and choose everything but the external SD card it fails to mount any of it..
Cwazywazy said:
I have a new problem.. I flashed the latest stable CyanogenMod and it wouldn't boot. (Boot animation just kept on going) So I went into TWRP and tried to do a wipe. For some reason it says "Unable to mount /data" or "internal storage". Even if I go into advanced wipe and choose everything but the external SD card it fails to mount any of it..
Click to expand...
Click to collapse
I've heard of other people complaining about this on TWRP.
You should either a) use OpenRecovery or another recovery... or b) use an older version of TWRP. I'm on 2.6.3.1 and it works _flawlessly_.
I haven't had time to update to the latest versions of TWRP to investigate this issue.
As for your CM issue, make sure you wipe (using a recovery that works haha) and also make sure you give it plenty of time to do the first boot - there is sometimes a fsck process which runs at boot and takes a lot longer than usual for the device to actually boot up.
Please help me. I can't find any solution and I can't boot into CMod.
Cwazywazy said:
Please help me. I can't find any solution and I can't boot into CMod.
Click to expand...
Click to collapse
I gave you a solution, please at least try it.
arrrghhh said:
I gave you a solution, please at least try it.
Click to expand...
Click to collapse
Oh. I didn't see that, sorry. Trying it now.
arrrghhh said:
I gave you a solution, please at least try it.
Click to expand...
Click to collapse
Nope. Didn't work. Gave CM about 30 minutes to boot with no luck.
Cwazywazy said:
Nope. Didn't work. Gave CM about 30 minutes to boot with no luck.
Click to expand...
Click to collapse
Without logs I don't know what the issue would possibly be...
I would suggest trying CM10.2 perhaps? Or pull logs (adb logcat) from the failed boot of CM11. Like I said, that fsck process can take a very long time. I haven't personally experienced it, but I recall hearing reports of it taking upwards of an hour - either way, without logs, we don't really know what is going on.
arrrghhh said:
Without logs I don't know what the issue would possibly be...
I would suggest trying CM10.2 perhaps? Or pull logs (adb logcat) from the failed boot of CM11. Like I said, that fsck process can take a very long time. I haven't personally experienced it, but I recall hearing reports of it taking upwards of an hour - either way, without logs, we don't really know what is going on.
Click to expand...
Click to collapse
Here you go. Thanks for trying to help me (I zipped the file so I could use the uploader.)
Cwazywazy said:
Here you go. Thanks for trying to help me (I zipped the file so I could use the uploader.)
Click to expand...
Click to collapse
Not what I was expecting, but this does show an issue with recovery... What is the issue, I am a bit baffled by. I was hoping for a logcat from the CM11 failed boot.
Can you try another recovery? TWRP seems to be failing all over the place for you, even the version that is working fine for me
TWRP is failing to mount a lot of partitions, which is obviously unacceptable. I'm still not sure why the older version wouldn't work for you...
arrrghhh said:
Not what I was expecting, but this does show an issue with recovery... What is the issue, I am a bit baffled by.
Can you try another recovery? TWRP seems to be failing all over the place for you, even the version that is working fine for me
Click to expand...
Click to collapse
I don't know, I tried Clockwork mod which had the same problems. Are there any others I can try?
I was an idiot and I forgot to back up the stock ROM before I flashed CMod..
Cwazywazy said:
I don't know, I tried Clockwork mod which had the same problems. Are there any others I can try?
I was an idiot and I forgot to back up the stock ROM before I flashed CMod..
Click to expand...
Click to collapse
OpenRecovery?
arrrghhh said:
OpenRecovery?
Click to expand...
Click to collapse
I downloaded TWRP from here: http://goo.im/devs/OpenRecovery/asanti which has OpenRecovery in the name so I dunno...
Cwazywazy said:
I downloaded TWRP from here: http://goo.im/devs/OpenRecovery/asanti which has OpenRecovery in the name so I dunno...
Click to expand...
Click to collapse
No, not TWRP... OpenRecovery.
[25-11-2013] Photon Q Open Recovery 2.09
The links may not work in the OP, see here.
It's similar to CWM, but made specifically for the Q. Doesn't seem to have issues like TWRP, as it hasn't been updated in a while and it "just works". I'm still trying to sort out the issues with TWRP, why they affect some devices but not all.
arrrghhh said:
No, not TWRP... OpenRecovery.
[25-11-2013] Photon Q Open Recovery 2.09
The links may not work in the OP, see here.
It's similar to CWM, but made specifically for the Q. Doesn't seem to have issues like TWRP, as it hasn't been updated in a while and it "just works". I'm still trying to sort out the issues with TWRP, why they affect some devices but not all.
Click to expand...
Click to collapse
Ugh. Not working.
It says failed to mount /whatever (Invalid argument)