Related
Recovery: ClockworkMod 5.5.0.2
ROM: MCR Ir4
So, I've had my GN for about 5 days now, and wanted to experiment with the device encryption option. So, I followed the steps, and let the phone do it's thing, and an hour later it was encrypted. Now when the phone boots, it shows the boot animation, then prompts for the passcode, then remounts the unencrypted partitions as expected.
So, I starting having a look at how this impacts the usability, and now I have a bit of a problem. Firstly, as (at least) the whole /data partition is encrypted, it's not possible to access the 'sd card' from recovery, meaning that it's not possible to either create a backup or restore from one (as CWM can't mount the sdcard to do so). On realising this, I decided that I was done experimenting, and wanted to go back to the unencrypted state. How? Well, I can't.
If you go back to the security menu, the area that was used to start encryption is grayed out...it seems to have been a one-way process. At the time it mentionted that the only way to access the device if the encrytion passcode was lost would be to do a Factory Reset, so, this was what I tried next. The device restarted, showed the android with his front open and the cog on display for a few seconds, then restarted again, but took me back to where I was before - the wipe had not occurred.
Next, I tried to do a wipe from CWM - here I at least got a bit more feedback as to what was going on. It seems CWM needs to mount a given partition before it can wipe it, and as it can't do that, it couldn't wipe anything, so that didn't achieve anything either.
So, I'm now in a position where I have an encrypted device that I can't wipe, either through the normal factory reset in the Android UI, or via CWM recovery. I know that the collective smarts of this forum is a power to be reconed with, and as I've now reached the limits of my knowledge of working with this kind of thing, I'm hoping someone will be able to help me out.
My thinking so far: As the suggested method of recovering from an encrypted state is to do a factory reset, it would suggest that there is either
a) a bug in ICS that isn't handling the wipe of an encrypted device correctly
b) an incompatibility with CWM that is conflicting with the OS' ability to execute the wipe (as CWM can't interact with the encrypted partitions)
c) a bug in Paul's MCR ROM (much less likely IMO)
I hope that all makes sense, and that someone has some thoughts on where to go from here - thanks!
Flash stock images through fast boot?
Sent from my Galaxy Nexus using xda premium
I've just been reading up on fastboot since posting (I think I've only ever used it via other people's scripts before), and assuming that it can overcome the problem, I was thinking that maybe it would be able to do the wipe (though obviously I don't want to end up with a £500 paperweight...)
If I were to flash a stock image, how would I go about that? (It's been a long time since I've loaded a rom not via a recovery)
EDIT: Going to try a manual nandroid restore (from a backup made just before encrypting) as described here - http://wiki.cyanogenmod.com/wiki/Fastboot
Ok, flashed a stock image and back to factory state again so now all working (phew) - thankful I was doing this on a Nexus device where fastboot was easily available.
While this has solved the problem, it didn't really identify the cause - I'd be curious to hear of others' experiences with using the encryption in 3.0+.
Please keep questions out of the development section. Thank you
Sent from the MIUI powered 3d
jayharper08 said:
Please keep questions out of the development section. Thank you
Sent from the MIUI powered 3d
Click to expand...
Click to collapse
Apologies - posted here as thought it could have been development related (Possible CWM/MCR bug).
Don Vincenzo said:
Apologies - posted here as thought it could have been development related (Possible CWM/MCR bug).
Click to expand...
Click to collapse
No worries. Dev section is just for strictly developed roms and kernels and such. No biggie
Wish I could help you with the answer though :/
Sent from the MIUI powered 3d
Don Vincenzo said:
Recovery: ClockworkMod 5.5.0.2
ROM: MCR Ir4
So, I've had my GN for about 5 days now, and wanted to experiment with the device encryption option. So, I followed the steps, and let the phone do it's thing, and an hour later it was encrypted. Now when the phone boots, it shows the boot animation, then prompts for the passcode, then remounts the unencrypted partitions as expected.
So, I starting having a look at how this impacts the usability, and now I have a bit of a problem. Firstly, as (at least) the whole /data partition is encrypted, it's not possible to access the 'sd card' from recovery, meaning that it's not possible to either create a backup or restore from one (as CWM can't mount the sdcard to do so). On realising this, I decided that I was done experimenting, and wanted to go back to the unencrypted state. How? Well, I can't.
If you go back to the security menu, the area that was used to start encryption is grayed out...it seems to have been a one-way process. At the time it mentionted that the only way to access the device if the encrytion passcode was lost would be to do a Factory Reset, so, this was what I tried next. The device restarted, showed the android with his front open and the cog on display for a few seconds, then restarted again, but took me back to where I was before - the wipe had not occurred.
Next, I tried to do a wipe from CWM - here I at least got a bit more feedback as to what was going on. It seems CWM needs to mount a given partition before it can wipe it, and as it can't do that, it couldn't wipe anything, so that didn't achieve anything either.
So, I'm now in a position where I have an encrypted device that I can't wipe, either through the normal factory reset in the Android UI, or via CWM recovery. I know that the collective smarts of this forum is a power to be reconed with, and as I've now reached the limits of my knowledge of working with this kind of thing, I'm hoping someone will be able to help me out.
My thinking so far: As the suggested method of recovering from an encrypted state is to do a factory reset, it would suggest that there is either
a) a bug in ICS that isn't handling the wipe of an encrypted device correctly
b) an incompatibility with CWM that is conflicting with the OS' ability to execute the wipe (as CWM can't interact with the encrypted partitions)
c) a bug in Paul's MCR ROM (much less likely IMO)
I hope that all makes sense, and that someone has some thoughts on where to go from here - thanks!
Click to expand...
Click to collapse
just connect via adb in recovery and format it via mkfs.ext4...
and... then what? Once the partition is formatted - it seems it would need to be populated? Or does some subsequent restoration - once the /data partition is accessible - will re-create any files / folder structure in this filesystem?
I rooted my Kindle Fire using KFU 0.9.5 and flashed a custom ROM. It worked fine for a few days and then just crashed -- The options bar located on the bottom disappeared and the error message was: System UI has crashed. (I have attached two pictures for better clarity)
Also, whenever I boot up, there is no yellow flame that appears, it goes to the moving colourful discs straight on.
I tried using terminal emulator and entered many codes in some hope of mounting USB Mass Storage so that I can use KFU and restore my Kindle, but in vain.
I have tried EVERYTHING. I've been at this for 6 days now and am at wits end. :crying: I have read up close to a 100 articles; this was my last resort.
I just want to get the Kindle's stock OS back - no root, nothing.
And the only was is, I suppose, if I am able to mount my Kindle as USB Mass Storage onto my computer.
ANY help is appreciated!
AndroBoss.
I don't have a kindle but did you try wiping it and reinstalling it?
Sent from my SPH-L710 using xda app-developers app
jr71x said:
I don't have a kindle but did you try wiping it and reinstalling it?
Sent from my SPH-L710 using xda app-developers app
Click to expand...
Click to collapse
As it now runs on ICS, there is no Gingerbread for Kindle anymore on it. I can't wipe it clean from the device or atleast I don't know how to, please help?
All the wipes you should need to perform can be done in twrp recovery. Wipe factory reset , wipe cache , wipe dalvik and wipe the system. Reflash ROM , reflash gapps , reboot then system if prompted and you should be good to go.
Edit: failing to use the correct method to return to stock will just cause more problems. Rather than trying to go back to pure stock without fff and twrp I suggest you perform the above wipes and flash this instead http://forum.xda-developers.com/showthread.php?t=1439916 its just modified stock with Google play and it will not wipe out your recovery and bootloader.
Thepooch said:
All the wipes you should need to perform can be done in twrp recovery. Wipe factory reset , wipe cache , wipe dalvik and wipe the system. Reflash ROM , reflash gapps , reboot then system if prompted and you should be good to go.
Edit: failing to use the correct method to return to stock will just cause more problems. Rather than trying to go back to pure stock without fff and twrp I suggest you perform the above wipes and flash this instead http://forum.xda-developers.com/showthread.php?t=1439916 its just modified stock with Google play and it will not wipe out your recovery and bootloader.
Click to expand...
Click to collapse
Okay, I will flash what you suggested but that's the problem. I am unable to access TWRP recovery from my Kindle. When it boots up there is no yellow flame that appears as the custom ROM is ICS 4.0.
I tried mounting a twrp.img on to the SD Card after downloading one straight onto the tab but of no avail :/
What do you suggest? Is there any way I can get the TWRP Recovery to come up so that I can get the modified stock that you suggested?
Thanks for your help, regardless
Androboss1994 said:
Okay, I will flash what you suggested but that's the problem. I am unable to access TWRP recovery from my Kindle. When it boots up there is no yellow flame that appears as the custom ROM is ICS 4.0.
I tried mounting a twrp.img on to the SD Card after downloading one straight onto the tab but of no avail :/
What do you suggest? Is there any way I can get the TWRP Recovery to come up so that I can get the modified stock that you suggested?
Thanks for your help, regardless
Click to expand...
Click to collapse
I know you said you read "close to a 100 articles" in your OP, but I suggest you do a little more reading. Get yourself acquainted with the key software components of the Kindle Fire and how they work together. Some of the things you say in your posts suggest you would benefit from the first post here...
http://forum.xda-developers.com/showthread.php?t=1552547
- The yellow flame you are looking for is an older version of the FireFireFire (FFF) bootloader, but there is a newer/better version.
- The KF cannot go to "the moving colorful discs straight on" because the first thing you will see is the bootloader's bootlogo.
- You must determine what bootloader is currently installed on the device because it is key in determining how you can get into recovery (TWRP).
- "Mounting" sdcard means to make the storage space available to either the host computer or the Kindle Fire, but it almost always means the former. Your comment about having "tried mounting a twrp.img on to the SD Card" doesn't make sense.
My guess is you do not have FFF installed and the device is booting with the stock bootloader. Odds are you will still be able to boot into your current ICS system and execute an adb command to set the bootmode to recovery (5001). Then a reboot should take you into TWRP. At that point, you should try to mount the sdcard partition onto your computer and transfer the latest FFF and whatever ROM you want to flash. Be sure to install FFF as soon as possible. This will allow you to get back into TWRP even if your system software becomes unbootable. Only when you are comfortable with FFF and TWRP should you consider flashing another ROM onto the device.
In broad strokes, the above paragraph contains the steps you will take to get your device running properly again. If any part of it doesn't make much sense to you, I suggest you read the above article again. Then, you can figure out the specifics commands from the third post of the link above and the following...
http://forum.xda-developers.com/showthread.php?t=1638452
kinfauns said:
I know you said you read "close to a 100 articles" in your OP, but I suggest you do a little more reading. Get yourself acquainted with the key software components of the Kindle Fire and how they work together. Some of the things you say in your posts suggest you would benefit from the first post here...
http://forum.xda-developers.com/showthread.php?t=1552547
- The yellow flame you are looking for is an older version of the FireFireFire (FFF) bootloader, but there is a newer/better version.
- The KF cannot go to "the moving colorful discs straight on" because the first thing you will see is the bootloader's bootlogo.
- You must determine what bootloader is currently installed on the device because it is key in determining how you can get into recovery (TWRP).
- "Mounting" sdcard means to make the storage space available to either the host computer or the Kindle Fire, but it almost always means the former. Your comment about having "tried mounting a twrp.img on to the SD Card" doesn't make sense.
My guess is you do not have FFF installed and the device is booting with the stock bootloader. Odds are you will still be able to boot into your current ICS system and execute an adb command to set the bootmode to recovery (5001). Then a reboot should take you into TWRP. At that point, you should try to mount the sdcard partition onto your computer and transfer the latest FFF and whatever ROM you want to flash. Be sure to install FFF as soon as possible. This will allow you to get back into TWRP even if your system software becomes unbootable. Only when you are comfortable with FFF and TWRP should you consider flashing another ROM onto the device.
In broad strokes, the above paragraph contains the steps you will take to get your device running properly again. If any part of it doesn't make much sense to you, I suggest you read the above article again. Then, you can figure out the specifics commands from the third post of the link above and the following...
http://forum.xda-developers.com/showthread.php?t=1638452
Click to expand...
Click to collapse
WOW! Okay, thank you so much; I'll keep you updated. I'll do all this tonight! Cheers :good:
Kindle Fire 1st Generation.
I have a bad USB Port. Cannot charge... cannot connect to PC. Device is Rooted and need to go back to Amazon for Warranty Exchange. How should i proceed?
I really don't want to send it rooted.
I have another Kindle.. If i swap the Motherboard, will i be able to restore back to factory settings?? Is the memory attached to the Motherboard?
So, by just swapping the board, will i get the old Cyanogenmod rom back?? or will it give me the new Kindle since the memory is physically attached to the board??
Thanks for any insights.
JP
Do you have enough battery to follow these instructions?
http://forum.xda-developers.com/showpost.php?p=22663761&postcount=7
chris_m128 said:
Do you have enough battery to follow these instructions?
http://forum.xda-developers.com/showpost.php?p=22663761&postcount=7
Click to expand...
Click to collapse
No Battery left ... i get that warning "battery to low to power on", plus USB port it dead... no way to charge ...no way to connect to PC. Plus when i rooted the device (one year ago) i do not remember what process was used ...but it seems that i do not have any recovery on the device... I could open and swap with a full battery. in order to Flash the Update.zip... but without a recovery... no idea how to do it.. that is why i thought about the motherboard swap...but then comes the question ..."where is the internal memory attached to...??? on the board???if i swap ...will i still get the Cyanogenmod rom that i had.???
Thanks
JP
Even if you swapped boards there is the problem of the serial number so it wouldn`t do you any good for return purposes. You could swap batteries though and apply update.zip after a full wipe then return the working battery to the unit you wish to keep. Send them the dead battery and the factory restored unit with the correct serial number board. As far as getting update.zip to the device simply upload it to Google drive or Dropbox then download it directly to the device and move it from your download folder to the root of your sdcard. wipe factory reset, wipe cache, wipe dalvik, wipe system, flash update.zip select reboot system. The only risk is corrupting update.zip in the process make sure to perform an md5 check prior to upload and prior to flashing. You can acquire update.zip from kfu just don`t use the extracted version the one you want is update.zip it is a zipped folder ready for the purpose of flashing.
Thepooch said:
Even if you swapped boards there is the problem of the serial number so it wouldn`t do you any good for return purposes. You could swap batteries though and apply update.zip after a full wipe then return the working battery to the unit you wish to keep. Send them the dead battery and the factory restored unit with the correct serial number board. As far as getting update.zip to the device simply upload it to Google drive or Dropbox then download it directly to the device and move it from your download folder to the root of your sdcard. wipe factory reset, wipe cache, wipe dalvik, wipe system, flash update.zip select reboot system. The only risk is corrupting update.zip in the process make sure to perform an md5 check prior to upload and prior to flashing. You can acquire update.zip from kfu just don`t use the extracted version the one you want is update.zip it is a zipped folder ready for the purpose of flashing.
Click to expand...
Click to collapse
Well the swapping would just be temporary to restore the Official ROM...but i need to be sure that the memory isn't on the board..
And what about TWRP??? how do i load it without KFU?? If i rooted with KFU and TWRP, does it still have to be there??
JP
All data and perspective partitions are stored on the board and no where else if you have cm10, fff, and twrp on the board it will be there still. It's far easier to just change batteries momentarily to restore the device you wish to return.
chris_m128 said:
Do you have enough battery to follow these instructions?
http://forum.xda-developers.com/showpost.php?p=22663761&postcount=7
Click to expand...
Click to collapse
Thepooch said:
All data and perspective partitions are stored on the board and no where else if you have cm10, fff, and twrp on the board it will be there still. It's far easier to just change batteries momentarily to restore the device you wish to return.
Click to expand...
Click to collapse
Well that is exactly what i will do.. Thanks chris_m128 and Thepooch for your help... will open my refurbished unit, take the battery out.. put it in the damaged unit.. download the updated.zip... check md5 then turn it off and try to start TWRP .. (will check on the internet the proper steps to get there) then do the whole clear cache and reset factory then flash update.zip.. Does that sound about right?? And I should have TWRP if i have already installed Cyanogen mod Right?? Last time i booted i did not have the FireFireFire BootLoader..
I i don't have this bootloader...how to i get to the TWRP screen??
Thanks guys!!! It is really incredible how many people have complained about this bad USB ports.. Amazon should do a Recall!!!
PS: anyway to recharge the battery without having to disassemble my new Kindle?? Like a third party charger??
JP
Actually interesting you should mention fff version 1.4a was designed with a particular failsafe for low level charging via USB some it works for some it doesn't. The two methods I have heard mentioned first simply power it off then plug to PC others say to power it off after it comes on connected to PC, both with varied results. Which ever works I guess. As for the lack of the fff bootloader there is an older form of smirkit that can be ran just by simply placing a folder on your sdcard and running a script let me know when your are near that point and I can assist you in getting that accomplished with jrummy`s root browser. Also I have dropboxed update.zip for download purposes just want to make sure the md5 checks out beforehand.
I managed to fully charge it by certain angle last night.
Now I can revert it back to stock before sending it back.
The replacement is on its way.
Good point I was going to mention the use of tape to lean the usb connection to an angle to get connection sometimes this will work sometimes it`s simply toast.
Hoping someone here can give me some help. Sometime last night my phone crashed - had an error message on the screen asking me if i wanted to restart - basically the android version of a blue screen.
I rebooted and when it started up it tried to activate but failed. Tried it a few times, never activated. I called sprint and they had me type in 2 different codes:
##72786# which didn't get an error but didn't help anything
They had me try a 2nd 6 digit number, which I'm not sure if it's unique to my phone or not so I wont post it here but that did nothing at all - typed in the ##______# and nothing happened. They claimed it was because the phone is rooted, but the phone is ONLY rooted. I haven't installed a new OS it's the stock rom as far as i can tell.
Anyone have any ideas whats going wrong here or how to fix it?
thanks
edit: and apparently now I wiped the OS from the phone since it wont go past the LG logo. Is there some way for me to either copy a rom onto the phone from TWRP or copy a backup onto the phone? I've got a couple of TWRP backups saved on my pc, but since the phone wont start up I don't have any way of copying them onto the phone - damn non-user removable sd cards.
merkk said:
Hoping someone here can give me some help. Sometime last night my phone crashed - had an error message on the screen asking me if i wanted to restart - basically the android version of a blue screen.
I rebooted and when it started up it tried to activate but failed. Tried it a few times, never activated. I called sprint and they had me type in 2 different codes:
##72786# which didn't get an error but didn't help anything
They had me try a 2nd 6 digit number, which I'm not sure if it's unique to my phone or not so I wont post it here but that did nothing at all - typed in the ##______# and nothing happened. They claimed it was because the phone is rooted, but the phone is ONLY rooted. I haven't installed a new OS it's the stock rom as far as i can tell.
Anyone have any ideas whats going wrong here or how to fix it?
thanks
edit: and apparently now I wiped the OS from the phone since it wont go past the LG logo. Is there some way for me to either copy a rom onto the phone from TWRP or copy a backup onto the phone? I've got a couple of TWRP backups saved on my pc, but since the phone wont start up I don't have any way of copying them onto the phone - damn non-user removable sd cards.
Click to expand...
Click to collapse
Can you boot to recovery?
If you can, then flash a newer TWRP build, they have MTP support, you can mount it while connected to your PC, copy a ROM zip over (there is a stock on in these threads somewhere), flash it from recovery, wipe everything first. Then you should be able to boot into a working device.
Yes I can boot into twrp, but I'm not sure how to copy files that way. I tried using adb but it couldnt find the phone. Can you give me some tips on how to copy a new ROM or twrp backup to the phone?
Thanks
merkk said:
Yes I can boot into twrp, but I'm not sure how to copy files that way. I tried using adb but it couldnt find the phone. Can you give me some tips on how to copy a new ROM or twrp backup to the phone?
Thanks
Click to expand...
Click to collapse
Yes, first thing is to flash this.
http://cubegamemc.de/kevinjoa/lollipop/recovery-geehrc/twrp/
You can flash it through fastboot.
follow these steps:
1. Download and place the file on your PC.
2. Reboot your device into Fastboot Mode. To do that, simply hold down the Volume DOWN+Power buttons together.
3. Once inside the Fastboot mode, connect your device to your PC via USB cable.
4. Launch a Command Prompt Window in the folder you saved the recovery image to. You can do that by holding down the Shift button on your keyboard and right-click on any blank area on the screen, then select Open command window here.
4. Enter the following command into the Command Prompt Window. You need to replace recoveryfilename.img with the actual name of the Recovery Image you downloaded.
Code:
fastboot flash recovery recoveryfilename.img
5. Once it is done, reboot your device
Code:
adb reboot recovery
should do it. If not, just hold down the power button, and get back to recovery.
at that point you should have the newest recovery. This recovery has MTP enabled so you can transfer files just like you can if you had a running device.
Once it shows up on you PC you can transfer a ROM zip or a backup to the internal SD. From there you I am sure you know how to flash a zip or restore a backup. It is the same as an older version. MTP should be under the "MOUNT" section of TWRP. I don't remember because I have a different device now.
Good luck!
If this doesn't work, follow the thread here: You would need the super big full bin file if you do though because you do not have a working ROM or zip currently on your internal SD card and this contains a very old recovery, but it does work.
http://forum.xda-developers.com/showthread.php?t=2230106
edit: I altered the directions from the source here for the att version. Don't worry, I changed them to suit your current need.
http://theunlockr.com/2013/03/26/how-to-install-twrp-recovery-on-the-lg-optimus-g-att/
My phone seems to behave a little differently than what you describe. Holding down the volume down and power button just turns it on. Holding vol up and power puts me into a screen with the android bot on it with the option to restart bootloader, go into recovery, or power off. and at the bottom there's some text indicating fastboot mode is on.
I was able to use the fastboot command to load the newer recovery. But for some reason, none of the adb commands work on my phone.
I'm copying a twrp backup to the phone now and i'll restore that. Hopefully that'll fix the issue of the phone not booting and if i am really lucky, fix the issue of the phone not being activated, but I'm not too hopeful about that.
Thanks again for all your help
hey - just wanted to say thank. Got my phone to boot back up again. Unfortunately the backup restore doesnt seem to have fixed my initial problem. Phone is back to saying it needs to be activated. Any ideas about that? It's also showing zero bars - not sure if that's what it's supposed to show when it's not activated.
Thanks again for your help
merkk said:
hey - just wanted to say thank. Got my phone to boot back up again. Unfortunately the backup restore doesnt seem to have fixed my initial problem. Phone is back to saying it needs to be activated. Any ideas about that? It's also showing zero bars - not sure if that's what it's supposed to show when it's not activated.
Thanks again for your help
Click to expand...
Click to collapse
EDIT:: TRY THIS FIRST<
Do a full wipe of the system and data, not internal. GO to recovery, select wipe, then factory reset. Then boot your phone. You will have to setup everything again but it might help. If it does not, you can always restore your backup again.
^^^^^^^^^^^^^^^^^^^^^^^
Interesting that your phone was the opposite for the buttons. Maybe I had it backwards, or maybe my source did. Either way I am glad you have a device that boots now.
Check this...
Go to the about section and see if your imei and other information are blank or have 0's. I am almost certain that there are 0000's.
If that's the case then you lost your EFS some how. and there is a way to recover that as long as you have a backup somewhere. You should have one somewhere if you used freegee to unlock your phone in the beginning. If not, perhaps an earlier backup you had of your device. A lot of the recoveries for this device make a backup of the EFS.
well i just dropped the phone off at a sprint repair store to see if they could do anything with it now that it actually boots. If they can't fix it, I'll try what you suggested. Although i already tried a factory reset and that didn't help.
well you are right about the esn/meid/IMEI - they are all zeros
I did a restore and then used freegee to restore the efs. Will free tell you if there is no backup of the EFS? Because i restored it, it finished pretty much instantly, and then i restarted the phone just be safe. Unfortunately it didn't fix it.
Phone still says searching for service, and now there's a little red x over the bars. Before the bars were blank but there was no red x. Not sure if that makes any difference.
Also, something else weird is going on now. I just tried copying a newer backup to the phone to try and restore the newer one. I don't seem to be able to copy files now. When i drag the folder windows , it says the device has stopped responding. If i try and copy each individual file in the backup folder, it starts to copy, and then just sits there like it froze, or like it's copying so slowly it might as well be frozen. I had to reflash twrp to the newer version and then I'm able to copy files.
Reloaded the efs backup again but still can't activate/have all zeros.
I have a Htc M8 that i cant get to do anything possible I cant make folders to download things to fix it i cant go into download mode correctly and its a real headache all i want to do is go back to stock and move from there all i need ins the first step in to doing so Im not familiar with htc what so ever and i got this device trying to replace my old broken one i got it from a person who if i tell him abut the problem with the phone he will not help me at all and just laugh in my face for not being able to fix it i would be able to work off the steps anyone is willing to help me out with but as of now heres the facts.
Android Version: 6.0
Htc Sense Version: 7.0
Software number : SkyDragon M8 v2.0.0 Sense 7MM
Kernel Version: [email protected]#1 SMP PREEMPT
Build #: 6.12.401.4 cl66 2736 relese-keys
When i plug into computer No files show up in the internal storage nor does it show up in the phone when using the file manager.
cant download chrome or any other internet bowers other than dolphin browser (wont open)
so yeah if anyone can help that would be great
Tensaz said:
its a real headache all i want to do is go back to stock and move from there
Click to expand...
Click to collapse
Always make a backup of the current (known good, working) ROM in TWRP, before flashing a new ROM. That way, you always have an easy way to restore to stock or the previous working ROM, if something goes wrong.
I'm always surprised at how many folks skip this step. It should be a cardinal rule for any rooting, ROM flashing, etc.
But I also don't think that returning to stock would solve your issue. I think your internal storage is corrupt. I assume you don't have any data you want to try to recover (it probably can't be retrieved at this point, anyway)? Boot into TWRP, press the Wipe button, then select the "Format data" button. Don't mess with the Advanced button (and wipe options therein) unless we tell you.
After format data, reboot and see if the issues with writing to storage is fixed, and let us know.
Tensaz said:
i cant go into download mode correctly
Click to expand...
Click to collapse
HTC devices don't have download mode. It has hboot (bootloader) and you can select fastboot mode, or go to recovery from there. But no download mode.
redpoint73 said:
Always make a backup of the current (known good, working) ROM in TWRP, before flashing a new ROM. That way, you always have an easy way to restore to stock or the previous working ROM, if something goes wrong.
I'm always surprised at how many folks skip this step. It should be a cardinal rule for any rooting, ROM flashing, etc.
But I also don't think that returning to stock would solve your issue. I think your internal storage is corrupt. I assume you don't have any data you want to try to recover (it probably can't be retrieved at this point, anyway)? Boot into TWRP, press the Wipe button, then select the "Format data" button. Don't mess with the Advanced button (and wipe options therein) unless we tell you.
After format data, reboot and see if the issues with writing to storage is fixed, and let us know.
HTC devices don't have download mode. It has hboot (bootloader) and you can select fastboot mode, or go to recovery from there. But no download mode.
Click to expand...
Click to collapse
okay so i followed the steps you gave me and was able to download to my internal and load another rom onto it. also it wasn't me who had wiped the phone entirely it was the person i got the phone from he said he wiped everything on twerp except the system..........which in itself was stupid cause that means you wiped everything on the phone from the recovery options to basic system stuff. i am now running bliss pop v 6.2 i think but i may chage that to cm 13 due to an error for Pokemon go , King Tongue, and YouTube Vr. Pokemon go and Youtube vr gets a blue circle in the middle of the screen and keeps you from playing the game or using your onscreen buttons to leave the app the only way to leave is to put the phone to idle mode (press the power button) then unlock the phone and then quickly press the home button.. but you have helped me with my issue thank you im to use to Samsung and Lg lol.
P.S. Do you buy any chance on how if i ever wanted to go back to stock on how i can do so ?
Tensaz said:
i got the phone from he said he wiped everything on twerp except the system..........which in itself was stupid cause that means you wiped everything on the phone from the recovery options to basic system stuff.
Click to expand...
Click to collapse
I don't know what you mean by "recovery options to basic system stuff". By not wiping system, the OS is kept fully intact. All the other options are various forms of user data.
But yes, wiping most/all the options in the TWRP "Advanced" wipe section is foolish. Folks often will do this, which wipes the ROM they want to flash, TWRP backups, and even system itself (then wonder why there is no OS!).
Tensaz said:
P.S. Do you buy any chance on how if i ever wanted to go back to stock on how i can do so ?
Click to expand...
Click to collapse
I do know, but I can't tell what "stock" is for your phone, besides that its Dev Edition. Do fastboot getvar all, and post the results (delete IMEI and serial number before posting).
redpoint73 said:
I don't know what you mean by "recovery options to basic system stuff". By not wiping system, the OS is kept fully intact. All the other options are various forms of user data.
But yes, wiping most/all the options in the TWRP "Advanced" wipe section is foolish. Folks often will do this, which wipes the ROM they want to flash, TWRP backups, and even system itself (then wonder why there is no OS!).
I do know, but I can't tell what "stock" is for your phone, besides that its Dev Edition. Do fastboot getvar all, and post the results (delete IMEI and serial number before posting).
Click to expand...
Click to collapse
I get the fast-boot thing but where is the option for the getvar all? is it in the first option after doing the button sequence power+vol down or after choosing fast boot?
fastboot getvar all is a command that you put in your PC, in CMD... you must have fastboot and adb drivers installed