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)
Related
Hi all,
I recently unlocked my VZW Xoom using the OEM unlock instructions found here: http://forum.xda-developers.com/showthread.php?t=967065
I then downloaded the most recent CWM (3.025) and followed the instructions found in this thread: http://forum.xda-developers.com/showthread.php?t=1038870
I was able to write CWM to the recovery partition with no errors showing in either ADB or on the device itself. I verified the checksum of recovery.img.
What happens now is that when I reboot to recovery from ADB, the red Moto logo shows up, and at first everything looks good. At the top it says "Reading ODM fuse 1".
Then, a green Android logo with a yellow exclamation mark on it appears over a black screen. It looks like some sort of error message. I have CWM on my phone so I know this isn't what it's supposed to look like
In any case, has anyone else seen this issue (or better yet, know how to fix it)? I should point out that after a few minutes, the Xoom automatically boots into HC and works just fine.
it kind of sounds like the recovery didn't flash. Have you tried to flash it again?
Jthom203 said:
it kind of sounds like the recovery didn't flash. Have you tried to flash it again?
Click to expand...
Click to collapse
Hi - thanks for the response.
Yes, I've tried that, rebooted the device, rebooted the PC, tried it again, etc. Still no dice
does it still boot? if so try installing rom manager and using it to flash CWR
Sic123 said:
does it still boot? if so try installing rom manager and using it to flash CWR
Click to expand...
Click to collapse
Yep, it still boots. I've never used ROM manager, but I did happen to just download it. I'll give that a shot.
Two other things I didn't mention in the OP:
- I do not have an SD Card in the slot.
- I also didn't 'root' the phone yet with the SuperUser APK, only unlocked the bootloader. Would either of those cause the issue?
I believe you have to root to flash recovery. Here is an easy way to do it http://forum.xda-developers.com/showthread.php?t=1011196 its the one click method just make sure your not doing anything else while running
Jthom203 said:
I believe you have to root to flash recovery. Here is an easy way to do it http://forum.xda-developers.com/showthread.php?t=1011196 its the one click method just make sure your not doing anything else while running
Click to expand...
Click to collapse
Already in the works I'll let you know how it turns out.
Initially, it seems odd that ADB/fastboot wouldn't return an error if root is needed for flashing recovery. Time will tell...
volta said:
Already in the works I'll let you know how it turns out.
Initially, it seems odd that ADB/fastboot wouldn't return an error if root is needed for flashing recovery. Time will tell...
Click to expand...
Click to collapse
Root was the answer. Duh. I feel dumb now.
Either way, once I get to 10 posts, I can post in the dev forum thread to make it clear that root, not just OEM unlock, is required to flash CWM so that dummies like me can get things working quickly
nice, glad that you got it working.
Be sure to install Tiamat 1.31 so you can use your SD card and get full access to CWM
Rom Manager question
Has anyone found a way to allow Rom Manager to "Manage Backups"? It appears that it isn't pointing to the correct directory/ folder.
Had the same issues after installing CWM from ROM Manager - used the adb method instead and this fixed the issue. (Xoom was already rooted and OEM unlocked)
Hey all, sorry if this seems like other questions being posted, but I can not get my phone to work even after attempting the other fixes posted on the forums. I rooted my phone and was running the stock rom that came preloaded with it. I attempted to install CM10 through Rom Manager to no success, so I then tried to manually flash it as well as Gapps. My phone initially got stuck at the CM10 bootloader, but i could still go into CWM Recovery 5.8.3.1. After trying to get the rom to work more, it seems as if all I can access is CWM Recovery and nothing else. My phone wont even boot into the bootloader anymore and all i have access to is CWM Recovery.
I am not the most tech savvy individual when it comes to this since it has been ages since i tinkered with roms, but I would really like to fix this. So heres the facts since my post is so long (sorry!):
-Phone WILL NOT go into bootloader
-Can ONLY ACCESS ClockworkMod Recovery (5.8.3.1)
-SD Card wont mount (I get error "E:Unable to open ums lunfile (No such file or directory)")
I really just want to go back to stock and root again from scratch to reduce any errors like this from occurring in the future and ANY help would be appreciated because I am totally lost and without a phone now. To make things even more difficult, I only have access to a Mac running Lion....although i do have Windows 8 through the use of a bootcamp program, so I CAN run windows programs. Thank you all for any information you may have!
Do you have NANDROID backup,if yes do NANDROID restore and see what happens
Sent from my HTC One S using xda app-developers app
luxandroid said:
Do you have NANDROID backup,if yes do NANDROID restore and see what happens
Sent from my HTC One S using xda app-developers app
Click to expand...
Click to collapse
I do NOT have a nandroid backup. I dont even have access to my SD Card since my phone wont recognize it. I dont know where to even start in terms of fixing this. Any additional information anyone needs who thinks they can help me can be provided.
Porgress (Sort of)
I can now access my bootloader if this helps with anyone answering my issue! As I said before, any additional information from me about my phone that can help can and will be provided...just ask if you think you may be able to help!
fragkiller1 said:
I can now access my bootloader if this helps with anyone answering my issue! As I said before, any additional information from me about my phone that can help can and will be provided...just ask if you think you may be able to help!
Click to expand...
Click to collapse
Well since you in bootloader flash TWRP and then boot.img and then reflash the rom just to make sure.
Progress!
Darknites said:
Well since you in bootloader flash TWRP and then boot.img and then reflash the rom just to make sure.
Click to expand...
Click to collapse
Here is the inexperienced flasher in me asking this: How would I go about doing that? Is there a simplified way you could explain this to me, or even a guide? Thanks so much for the reply!
fragkiller1 said:
Here is the inexperienced flasher in me asking this: How would I go about doing that? Is there a simplified way you could explain this to me, or even a guide? Thanks so much for the reply!
Click to expand...
Click to collapse
Sorry. Best would be the All-In-One Toolkit, TWRP is a recovery to replace CWM because its that what's messing you up and also TWRP is better. Toolkit will also flash the boot.img too.
Darknites said:
Sorry. Best would be the All-In-One Toolkit, TWRP is a recovery to replace CWM because its that what's messing you up and also TWRP is better. Toolkit will also flash the boot.img too.
Click to expand...
Click to collapse
Okay, will do! Also, where would I find the Boot.img?
And on a side note; my phone says S-ON...I thought when rooted it was supposed to be S-OFF. Could that be causing problems as well?
fragkiller1 said:
Okay, will do! Also, where would I find the Boot.img?
And on a side note; my phone says S-ON...I thought when rooted it was supposed to be S-OFF. Could that be causing problems as well?
Click to expand...
Click to collapse
Boot.img is in the rom zip. S-On is not the reason its CWM thats messing you up with getting into the bootloader but also not flashing boot.img is not helping too.
Darknites said:
Boot.img is in the rom zip. S-On is not the reason its CWM thats messing you up with getting into the bootloader but also not flashing boot.img is not helping too.
Click to expand...
Click to collapse
The toolkit isnt working for me. Im not sure why... It seems like ill never get this phone up and running again
fragkiller1 said:
The toolkit isnt working for me. Im not sure why... It seems like ill never get this phone up and running again
Click to expand...
Click to collapse
Does the bootloader say fastboot usb?
Darknites said:
Does the bootloader say fastboot usb?
Click to expand...
Click to collapse
Yes it says fastboot USB, but i can not access it on my computer. Also, every time I try to run the toolkit you mentioned earlier... it says something along the line on "command not recognized" in CMD Prompt.
fragkiller1 said:
Yes it says fastboot USB, but i can not access it on my computer. Also, every time I try to run the toolkit you mentioned earlier... it says something along the line on "command not recognized" in CMD Prompt.
Click to expand...
Click to collapse
Hmm not sure have you tried redownloading it or reinstalling the HTC drivers and if that dont work best ask in the toolkit thread.
Darknites said:
Hmm not sure have you tried redownloading it or reinstalling the HTC drivers and if that dont work best ask in the toolkit thread.
Click to expand...
Click to collapse
That was the problem. the toolkit now works (in terms of doing what its supposed to do), but I can no longer access fastboot....just my recovery. any advice on how to get fix this?
fragkiller1 said:
That was the problem. the toolkit now works (in terms of doing what its supposed to do), but I can no longer access fastboot....just my recovery. any advice on how to get fix this?
Click to expand...
Click to collapse
I see that you got the toolkit and bootloader working but did you end up using the RUU?
Success!
Darknites said:
I see that you got the toolkit and bootloader working but did you end up using the RUU?
Click to expand...
Click to collapse
Yes, i ran the RUU and my phone reverted to its stock factory state, no problems at all! Im going to unlock the bootloader again as well as root and install CM10. Thank you for all your help!
fragkiller1 said:
Yes, i ran the RUU and my phone reverted to its stock factory state, no problems at all! Im going to unlock the bootloader again as well as root and install CM10. Thank you for all your help!
Click to expand...
Click to collapse
Np but this time use TWRP as your recovery and once you up and running with CM10 you can use Flash Image GUI to flash the boot.img if you ever update the rom.
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
I am using a Nexus 5, and I tried to flash the CyanogenMod 11s from OnePlus One to my Nexus following instructions from here:
http://www.ibtimes.co.uk/nexus-5-gets-port-cyanogenmod-11s-featuring-android-4-4-4-1458608
My phone was not rooted, I performed a root and apparently succeeded, because I saw SuperSU installed on my device. I then proceeded to follow the instructions from the site mentioned above, performed a factory reset, and selected the ROM I downloaded to flash. The flashing failed and I am currently stuck in bootloop, afraid to proceed further and brick my phone.
Some of the signs I noted with my phone:
At the ROM installation screen, it says 'checking for MD5 file... Skipping MD5 check: No MD5 file found', 'symlink: some symlinks failed', ' E: Error executing updater binary in zip '/sdcar', and 'Error flashing zip '/sdcard/CyanogenMod_11S_ham'
At Reboot menu, upon tapping on 'Recovery' option it says 'No OS installed! Are you sure you wish to reboot?'
Please help me out, I'm sick at the moment, guess it is not a good idea to flash a ROM when you're sick huh? Been trying to find a solution and can't seem to find it, not sure if because I'm sick and too tired to read through or there really isn't a situation like this...
Thank you!
first option, adb push a rom and gapps to your phone(while youre in recovery), then flash it. second option, flash the factory img via fastboot while youre in the bootloader. it has nothing to do with being sick, it has everything to do about learning all about your device and how to take care of it, before you start modding your device.
All right, trying now. Did I make any mistakes during my initial process? Please enlighten me. Thanks.
I build my own ROM even when I'm sick, what do you mean?
Try redownloading as it had flashing issues before
jackhayden said:
All right, trying now. Did I make any mistakes during my initial process? Please enlighten me. Thanks.
Click to expand...
Click to collapse
no, you didnt actually. you could have had a bad download, that happens often enough(but i dont think its the case, as it wouldnt remove your rom), you also could have experienced a recovery bug, that also can happen from time to time. btw, did you mention which recovery youre using?
I'm using TWRP.
jackhayden said:
I'm using TWRP.
Click to expand...
Click to collapse
well, try to download it again, and push it to your drvice with adb, then reflash it. or try pushing another rom. or, you always have the failsafe of flashing the factory img. btw, did you happen to make a backup in recovery before you flashed? you should always make a backup in recovery if flashing something new, just in case. in your case, it would make thing extremely easy.
Unfortunately, I did not make a backup. I will learn from this mistake.
I took your advice and started to do a sideload using instructions from here: http://forum.xda-developers.com/google-nexus-5/general/how-to-wipe-internal-storage-install-t2575150
However, I am stuck at no.7, could you please point out how do I carry out instruction no.7?
Thank you so much.
jackhayden said:
Unfortunately, I did not make a backup. I will learn from this mistake.
I took your advice and started to do a sideload using instructions from here: http://forum.xda-developers.com/google-nexus-5/general/how-to-wipe-internal-storage-install-t2575150
However, I am stuck at no.7, could you please point out how do I carry out instruction no.7?
Thank you so much.
Click to expand...
Click to collapse
you need to bring up the ui for typing.. on my old windows computer at work, i find an empty space on the same page that adb is located on your computer, then i left click and press the shift button on that empty space, then i get a few option that pop up, and i press the option. but im using windows from like 2004-5, lol.
Wow, that's really old.
I saw one of the commands available is 'adb push 'file name', should I try that?
Sorry for the troubles!
yup. first do "adb devices" to make sure adb sees your phone.
Push command won't work. Neither does the sideload option. It keeps on saying 'cannot read sideload'.
jackhayden said:
Push command won't work. Neither does the sideload option. It keeps on saying 'cannot read sideload'.
Click to expand...
Click to collapse
is the rom zip in the same folder as adb is located? it should be if not. and did adb see your device in with adb devices?
Yeah, the ROM is in the same folder as the adb, and device is recognised as in 'sideload' mode.
jackhayden said:
Yeah, the ROM is in the same folder as the adb, and device is recognised as in 'sideload' mode.
Click to expand...
Click to collapse
hmm.. well, i dont know that error, ive never seen it
Finally managed to flash the ROM in! However, in the CyanogenMod 11s, there isnt any google play store, how do i get it??
jackhayden said:
Finally managed to flash the ROM in! However, in the CyanogenMod 11s, there isnt any google play store, how do i get it??
Click to expand...
Click to collapse
Flash gapps
jackhayden said:
Finally managed to flash the ROM in! However, in the CyanogenMod 11s, there isnt any google play store, how do i get it??
Click to expand...
Click to collapse
"first option, adb push a rom and gapps to your phone(while youre in recovery), then flash it."
as @Lethargy said, gapps(google apps), you need to flash them. the google apps are not open source, they are owned by google, and cm isnt allowed to add them to the rom. but you are allowed to flash them separately
Thanks a lot for all the helps given. Really appreciate them! :good:
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.