Related
Hey all XDA members
Im sorry to ask any of you this but please help me !!
I had no problems rooting my phone with unrevoked and just left it at that but knowing me i downloaded a app on android market place called... ROM MANAGER - clockworkmod or whatever .. it seemed ok i went to backup my phone to my sd card and it said i had 897mb of storage left ... so i thought great ill back it up now so i wont brick my phone and if i ever did i could back up it said it finished succesfully or what not turns off my phone then every time it boots i get telstra next G boot logo then after abit it re F$#cking starts.. excuse my french i can access recovery menu and even clockworksmod recovery tryed formating the cache and everything
ATM im paying for a brick per month and it just seems so easy to fix but im obviously mistaken .. I really dont know what to do i wanna send it to htc but dont know how they would respond if they found clockworkmod in the recovery menu I dont even care if i have to pay them just so i can get my desire back ...
FAQS that ive learnt about this issue so far
#1 it makes a bootloop because i didnt have enough storage on my sd card so im puting the blame atm with the guys at clockmod for not giving users a clear warning that if you dont have enough memorey it will cause a boot loop ... and they make you pay for the app ... go figure >.>
There is no one to blame but you, you should know what you are doing with a rooted phone. Also your paying argument is stupid, who pays for a app you don't know before trying the free alternative?
Now to your problem:
Pull the battery.
Hold VolDown+POWER.
Go to recovery.
Go to backup and restore.
Restore.
Find the file of your backup. (either a data and time or a name you gave)
Click it.
Wait till it's done.
Reboot system now.
In recovery use the trackpad to navigate and confirm and in hboot, i think, volume up and down to navigate and power to confirm.
If there is no backup file at step 6, wipe dalvik cache under advanced (also in recovery), reboot and see if that fixed it. If not do a full wipe in recovery, data/factory reset, cache and dalvik cache under advanced. Keep in mind this will wipe everything of your phone. Sd card is not affected.
Thanks for the reply first off i know its my fault i program computers for a living and find it quite frustrating when i cant get a linux based phone to boot..
also to recovering the backup in clocksworkmod ... it didnt work, but it is probably corrupted from not being able to do a full backup of my phone.... if you or anyone else here who has a back on a htc desire please feel free to send me it
also to factory restore, formating cache still a no go im starting to lose hope already the phone hardware sense it fine its just the operating system thats bonkers
and finally i can understand you defending clocksmod and they have done a very good job but maybe next time they should warn us about this big bug thats in the backup process because this little piece of software has proberly bricked my phone from a tiny bug in the software
Well almost 900Mb is enough to back up your entire phone, unless you have a massif ext partition. So I doubt that is the problem but whatever.
If both the above steps didn't work (and you also clear dalvik cache) I suggest you just install a custom rom. If you don't know what you want or where to start, I suggest you start with Leedroid. If you have a ext partition on your sd card use the A2SD version, if you don't use NoA2SD version.
To install:
Download the rom.
Boot in to recovery.
Connect the phone to the pc.
Go to mounts and mount the sd as mass storage (or whatever it's called, should be the last option in the list if I remember correct)
Copy the rom to the sd. (not in any folder, just on the sd card)
Safely remove and unmount again.
Wipe data/factory rest, cache and dalvik again just to be sure.
Go to install zip form sd.
Chose zip form sd
Find the zip you just transferred and flash it.
Wait till it's done.
Reboot system. (this can take up to 10 minutes)
This should give you a booting phone again.
TheGhost1233 said:
Well almost 900Mb is enough to back up your entire phone, unless you have a massif ext partition. So I doubt that is the problem but whatever.
If both the above steps didn't work (and you also clear dalvik cache) I suggest you just install a custom rom. If you don't know what you want or where to start, I suggest you start with Leedroid. If you have a ext partition on your sd card use the A2SD version, if you don't use NoA2SD version.
To install:
Download the rom.
Boot in to recovery.
Connect the phone to the pc.
Go to mounts and mount the sd as mass storage (or whatever it's called, should be the last option in the list if I remember correct)
Copy the rom to the sd. (not in any folder, just on the sd card)
Safely remove and unmount again.
Wipe data/factory rest, cache and dalvik again just to be sure.
Go to install zip form sd.
Chose zip form sd
Find the zip you just transferred and flash it.
Wait till it's done.
Reboot system. (this can take up to 10 minutes)
This should give you a booting phone again.
Click to expand...
Click to collapse
Thanks again for the fantasitic help I will get right on it.. havent got much to lose now haha sorry for the late reply I was called to work I will post a video here to show some what the issue is before i install a custom rom thanks again
Oh and do you have paypal cause if it works i will pay you 20-50 or somthing LOl
I lost all my internal storage. I am like 99% sure I did not select wipe internal storage in recovery, but here we are. So, in the process of trying to flash JB lifeless I wiped system...now, it still would not install so I decided to install an older version of lifeless so
I could boot and be fine until I figured what was wrong. However, if you recall, I wiped internal stored ergo I have no zip to flash. No problem right? Just adb sideload; here's where my current issue comes in *cannot read 'sideload' * I have no idea what I am doing wrong. I am in recovery, in sideload mode...help.
Get on IRC for help. The folks/devs on there are phenomenal.
http://forum.xda-developers.com/showthread.php?t=1984622
RE: losing data, that may be a result of downgrading from JB to ICS.
easytheezy said:
I lost all my internal storage. I am like 99% sure I did not select wipe internal storage in recovery, but here we are. So, in the process of trying to flash JB lifeless I wiped system...now, it still would not install so I decided to install an older version of lifeless so
I could boot and be fine until I figured what was wrong. However, if you recall, I wiped internal stored ergo I have no zip to flash. No problem right? Just adb sideload; here's where my current issue comes in *cannot read 'sideload' * I have no idea what I am doing wrong. I am in recovery, in sideload mode...help.
Click to expand...
Click to collapse
i would suggest lgnpsting to get your system back than unlock and install from there. that sucks you lost everything tho.
So, I have an N7100. I have rooted my phone a few times. The last time was over a year ago and it worked fine. Yesterday, suddenly (I haven't attempted to flash anything) it restarted on its own and won't boot. I tried to go into the TWRP recovery I had installed over a year ago, but TWRP will only load for a second and then disappear and the phone would restart again and go into the bootloop. As a result, I can't wipe cache partition.
I can confirm that I can connect successfully to ODIN and flash a different version of TWRP. I have failed to flash CWM so far... maybe I couldn't find a correct version since my phone has knox???
I tried flashing a different kernel, but that didn't work either. Do I need a specific kernel?
The only thing I need to do is recover my files, whether it is through recovering the phone, or accessing the internal storage.
Can someone please help me? I don't want to do a complete wipe.
And in case this is relevant, my ROM is the custom OMEGA rom, I'm not sure which version though. Either 31, or 26, which is either for android 4.3 or 4.4.2.
Thanks
Hey,
I have the same problem, the phone just restarted on it's own yesterday, restarted again and is now stuck at the bootlogo.
Wiping Cache and Dalvik on it's own doesn't suffice, Wiping the system partition too (TWRP) gets the phone to boot, but it will restart again after a couple of minutes, again stuck at the boot logo.
I'm using the limbean ROM.
shadnixx, wiping the system partition does not mean that you're going to loose your data - you should try that, after the factory reset the phone is usable for a couple of minutes, I will now try to flash a newer ROM and gapps, maybe the problem will go away with that.
quickhash said:
Hey,
I have the same problem, the phone just restarted on it's own yesterday, restarted again and is now stuck at the bootlogo.
Wiping Cache and Dalvik on it's own doesn't suffice, Wiping the system partition too (TWRP) gets the phone to boot, but it will restart again after a couple of minutes, again stuck at the boot logo.
I'm using the limbean ROM.
shadnixx, wiping the system partition does not mean that you're going to loose your data - you should try that, after the factory reset the phone is usable for a couple of minutes, I will now try to flash a newer ROM and gapps, maybe the problem will go away with that.
Click to expand...
Click to collapse
Thanks for replying. I can't wipe the partition. That requires that I get into recovery, right? I can't even get into recovery. TWRP loads for just 1 second and then the phone reboots.
shadnixx said:
Thanks for replying. I can't wipe the partition. That requires that I get into recovery, right? I can't even get into recovery. TWRP loads for just 1 second and then the phone reboots.
Click to expand...
Click to collapse
have you tried to reinstall TWRP recovery? Maybe yours is corrupted, try to flash the latest version again. If that help you boot in recovery, things will be easier to haddle after.
https://dl.twrp.me/t03g/twrp-3.0.2-0-t03g.img.tar.html
also see this if it can help you
http://techbeasts.com/install-latest-twrp-recovery-on-samsung-galaxy-note-2-all-variants/
logosA said:
have you tried to reinstall TWRP recovery? Maybe yours is corrupted, try to flash the latest version again. If that help you boot in recovery, things will be easier to haddle after.
also see this if it can help you
Click to expand...
Click to collapse
Yeah I already tried that. Thanks though
@shadnixx Well use every possible way to flash and enter custom recovery. Try Philz, TWRP, CWM, everything...
If everything fails you'lll have to reflash Stock ROM using Odin. I've heard is wipes data but not internal storage but I'm not sure and don't balme me if it happens. Search xda a little.
See these threads: http://forum.xda-developers.com/showthread.php?t=2583588
http://forum.xda-developers.com/showthread.php?t=1121817
If that fails then the phone has hardware damage I think. Needs to go to service.
Option58 said:
@shadnixx Well use every possible way to flash and enter custom recovery. Try Philz, TWRP, CWM, everything...
If everything fails you'lll have to reflash Stock ROM using Odin. I've heard is wipes data but not internal storage but I'm not sure and don't balme me if it happens. Search xda a little.
See these threads: http://forum.xda-developers.com/showthread.php?t=2583588
http://forum.xda-developers.com/showthread.php?t=1121817
If that fails then the phone has hardware damage I think. Needs to go to service.
Click to expand...
Click to collapse
Thanks for your reply. That's what I'm trying to do. One question... do I have to have a specific CWM version that is compatible with my ROM?
Progress
OK, while flashing TWRP failed to help, flashing Philz Touch enabled me to get into recovery. I was able to mount the external SD card and browse the files, but the real problem is with the internal storage, since the SD card is removable. I couldn't manage to mount it. Can someone help with that?
Wiping the cache partition didn't help either.
You tried different tar versions of twrp?
What is the error message in Odin when trying to flash twrp?
Tried flashing twrp with different USB cables and USB ports?
audit13 said:
You tried different tar versions of twrp?
What is the error message in Odin when trying to flash twrp?
Tried flashing twrp with different USB cables and USB ports?
Click to expand...
Click to collapse
I'm sad to report, after I wiped the cache and restarted my phone, Philz would behave like TWRP did, which is to load for 1 second then reboot. Yes, I tried 4 different versions of TWRP, same result. Odin doesn't give any errors. It says that flashing was successful. Tried different cables and ports too, yes.
Possible power button or battery problem?
audit13 said:
Possible power button or battery problem?
Click to expand...
Click to collapse
Don't think so. I just replaced the battery... still same problem. And when I enter Odin "Download" mode, it doesn't keep restarting, so I don't think it's the power button.
I got a small update though...
Flashed another version of philz, which works every time I boot to recovery. A few problems though...
1. I can wipe cache partition, no problem. But When I try to wipe Dalvik, the phone reboots as soon as I try.
2. Aroma file explorer doesn't show any files.
3. I can mount external SD, but I can't mount internal storage
4. When using ADB, it could finally initiate pulling files from the internal storage (or that's what it appears to be doing), but only while on recovery mode. A few seconds after it says "listing files" or something, the phone reboots and the ADB operation aborts. It doesn't behave like this when I access other sections of philz recovery.
Any thoughts?
Another small update...
While using philz, I clicked the "install zip from sdcard" and it showed my folders. I think my files are intact, but I guess I can't be certain.
Small update again...
I flashed Aroma File Explorer from Philz, I managed to enter my internal storage browse around for a bit, but then the phone rebooted again. I tried to repeat so I could copy my internal storage, but now my internal storage says symlink error.
shadnixx said:
OK, while flashing TWRP failed to help, flashing Philz Touch enabled me to get into recovery. I was able to mount the external SD card and browse the files, but the real problem is with the internal storage, since the SD card is removable. I couldn't manage to mount it. Can someone help with that?
Wiping the cache partition didn't help either.
Click to expand...
Click to collapse
Listen up - Transfer any ROM to your external SD card, touchwiz based to avoid any complications if you can.
When you get into recovery (at least on TWRP 3 on my Galaxy Note 2 LTE this works) you can connect your phone to PC and transfer all the files, it just gets recognised.
If that fails then wipe /data and /cache partition and see if it boots. If that fails/succeeds then try to flash new ROM and wipe /data and see if it will boot. Data is not the same as internalSD. Data is your apps and settings, you can reinstall that later. InternalSD is your pictures and all. You want your pictures, not your apps, right? It is different.
But who knows what happened here. Malware? Corrupt partition? Hardware failure of some kind? Don't blame me if flashing a new ROM breakes everything even more.
Option58 said:
Listen up - Transfer any ROM to your external SD card, touchwiz based to avoid any complications if you can.
When you get into recovery (at least on TWRP 3 on my Galaxy Note 2 LTE this works) you can connect your phone to PC and transfer all the files, it just gets recognised.
If that fails then wipe /data and /cache partition and see if it boots. If that fails/succeeds then try to flash new ROM and wipe /data and see if it will boot. Data is not the same as internalSD. Data is your apps and settings, you can reinstall that later. InternalSD is your pictures and all. You want your pictures, not your apps, right? It is different.
But who knows what happened here. Malware? Corrupt partition? Hardware failure of some kind? Don't blame me if flashing a new ROM breakes everything even more.
Click to expand...
Click to collapse
I'll try that, thanks.
I was running oos based nougat custom rom with blu spark recovery. Then flashed official ob1, didnt like it, wiped cache/data/system and reinstalled my old oos nougat rom (audax 4.7.6). Now i get the above mentioned message..
Things i tried:
- addionally wipe internal storage and media (installed rom via adb sideload then)
- reformat system/cache/date with ext4
I googled the error and for most people (threads werent particularly concerning the op5t however) it seems that just wiping data and reinstalling the rom did the trick. Not for me though..
What can i do now?
Solution: reformating the data partition with ext4 is not enough. I had to format to FAT and right after that again to ext4, reboot to system and boom, it worked!
PS: i wonder what data is on the internal storage partition that i deleted? I didnt have any data on the phone, i just wonder.. It isnt somehow crucial to the phone?!
I think the decryption key is somehow embedded into the internal storage as wiping /data does not delete the PIN/pattern. Might be a hidden partition or something similar that is not wiped when wiping /data as long as it is ext4.
Your data is gone. It failed to completely encrypt and now there's nothing that can be done. Format /data as ext4 and let it try encrypting again
I have the same problem exactly. Can you explain in steps you have installed then format or how?
I have the same problem exactly. Can you explain in steps you have installed then format or how?
Click to expand...
Click to collapse
I had the exact same problem. But it is an easy fix but does require wiping your internal storage.
So the save way of doing this would be:
1. Backup all your data by going to TWRP or your ROM if that still works. Plug in an USB cable and use MTP or the adb pull command to backup your data
2. Reflash OB1 with no root (like Magisk of SuperSU) if you have TWRP. This will cause you to have the stock recovery again. I also recommend to do a clean flash (Wiping system and data before flashing the rom).
3. Download the rollback build from Oneplus [HERE] and copy this to the internal storage.
4. Boot into the stock recovery flash the rollback build. THIS STEP WILL WIPE YOUR INTERNAL STORAGE.
5. Now you have OxygenOS 4.7.5. Download OxygenOS 4.7.6 Incremental Update [HERE]
6. Go back to the Stock recovery and flash the incremental 4.7.6 zip.
7. You have the latest version now. So boot to fastboot reflash TWRP and flash SuperSU or Magisk in TWRP to regain root
Guys I did a fail, i had OB3 installed, and I wanted to try RR so I wiped system and when I tried to install I have seen error 7 saying its for dumpling not for oenplus5t.
So I restored.... But instead restoring OB3 I have restored stock Nougat rom -.- I have even stock recovery now, what is the best way to fix it?
Can i change to FAT and stay and dont go back to ex4 again?
Hi i don't know if u r reading this but if you are please help me cause I'm so lost and confused over this since yesterday...
so 2 days ago my phone started lagging and hanging and freezing until i realized i have got this issue with data encryption
i have a rooted sony z2 with TWRP Custom recovery
first i didn't know it was with data encryption failure so i literally factory reset and installed all my apps and data again and again!!! after every time my phone started to lag !!
after one whole day of trying everything i finally realized its actually with the data encryption and i should change my ex4 to something else... so here again i wiped the phone and changed to ex3 and installed and all my data and apps all over again
but after a couple hours...same problem again.....
im literally so tired of not knowing what to do ! my head hurts so much due this ugh....
i havent changed to FAT from ex3 so im wondering if it will finally solve my problem permanently if i change to FAT ??
And if it did can i just keep it on FAT forever ?
Please guide me thanks ...!
Lasersdude said:
I was running oos based nougat custom rom with blu spark recovery. Then flashed official ob1, didnt like it, wiped cache/data/system and reinstalled my old oos nougat rom (audax 4.7.6). Now i get the above mentioned message..
Things i tried:
- addionally wipe internal storage and media (installed rom via adb sideload then)
- reformat system/cache/date with ext4
I googled the error and for most people (threads werent particularly concerning the op5t however) it seems that just wiping data and reinstalling the rom did the trick. Not for me though..
What can i do now?
Solution: reformating the data partition with ext4 is not enough. I had to format to FAT and right after that again to ext4, reboot to system and boom, it worked!
PS: i wonder what data is on the internal storage partition that i deleted? I didnt have any data on the phone, i just wonder.. It isnt somehow crucial to the phone?!
Click to expand...
Click to collapse
Finally. Thank you so much!
I have watched a lot of tutorials but nothing is working please someone help
I made a video of the problem and what I tried. Can anyone understand what happened
https://www.youtube.com/watch?v=VaN-y-Worlg
Update: In Data i Changed the file system and went back to original. Didn't work.
I even wiped system. But i guess the only problem is to fix the "data". Since it shows 0 Mb size. But i can't find any way or guide. The ones i did find are too advanced and use cmd commands and toolkits which i don't think an inexperienced user like me should be following.
Some background information: i attempted to install Open gApps and enable Camera2 API. I Entered "read only" mode.
The adb shell commands for enabling it wasn't working (some "proprietary" something shown )
So I tried another method. I downloaded the latest Magisk and flashed it. Then i tried gApps. I don't remember when i started to think what went wrong but yeah..
I found this and I think it may be related.
But I don't understand it properly.
And its and Old post for some other Recovery
https://forum.xda-developers.com/go...o-repairing-corrupted-data-partition-t2577447
See if this will help you
https://forums.oneplus.com/threads/closed-solved-twrp-unale-to-mount-storage-help.544878/
Essentially reboot twrp then wipe-> format data
jaybeeee said:
See if this will help you
https://forums.oneplus.com/threads/closed-solved-twrp-unale-to-mount-storage-help.544878/
Essentially reboot twrp then wipe-> format data
Click to expand...
Click to collapse
DId that in the video. Doesn't work
Did you reboot twrp first? I don't see that
jaybeeee said:
Did you reboot twrp first? I don't see that
Click to expand...
Click to collapse
Oh yeah didn't do it in the video.. But yeah no good.
Crap, sorry to hear it, hopefully someone better than me chimes in. Good luck!
Why did you wipe internal storage? And what are you trying to mount. If you are trying to install a new rom all you need to wipe is cache, dalvik, system and data. Wiping internal storage removes everything from the internal SD card and if you do this then you have no OS.
Sent from my iPad using Tapatalk
Stransky said:
Why did you wipe internal storage? And what are you trying to mount. If you are trying to install a new rom all you need to wipe is cache, dalvik, system and data. Wiping internal storage removes everything from the internal SD card and if you do this then you have no OS.
Click to expand...
Click to collapse
At this point i can't care less about the data in internal storage. I just need to flash the official MIUI ROM back, enable Camera2 API and live in peace. At this moment I'm halfway through downloading the ROM but I'm not sure if i can flash it due to the Mount Issue of internal storage. I plan on transferring it to my micro SD card and flashing it from there to System Image. Will it work? And Internal Storage formatting failed in case you didn't notice. Practically nothing worked except the file system change of "data". And even that didn't fix the unable to Mount issue.
Stransky said:
Why did you wipe internal storage? And what are you trying to mount. If you are trying to install a new rom all you need to wipe is cache, dalvik, system and data. Wiping internal storage removes everything from the internal SD card and if you do this then you have no OS.
Click to expand...
Click to collapse
Btw i gave more information on the first post.
Have you tried redwolf recovery? If it has the same error then flash your phone with fastboot rom
devcon69 said:
Have you tried redwolf recovery? If it has the same error then flash your phone with fastboot rom
Click to expand...
Click to collapse
Hevent tried redwolf recover. Just Fastboot flashed the ROM on intuition. And it Worked!!