Here's the whole story:
I accidentally changed the file permission of the Permission folder, what happened was after rebooting other application suddenly stop working. So what I did
was factory reset the phone from the phone settings but the problem now is that the phone keeps rebooting over and over again. I did go to the recovery mode and factory reset and clear cache but the problem still persists. How can i fix this?? (
Phone specs:
Model : O+ 360
Ram: 1024mb
OS: Android Kitkat 4.4.2
Hi there
The thing is, when you modify your system file and it decides to cause issues. You can't fix it without the original file.
Factory resetting it will only make it worse as in this case you're now experiencing boot loops. Factory resetting will only revert the settings, remove installed apps, and user edited content.
However, it will not revert the changes you made to the system because it doesn't know what to revert back to.
In many cases, an easy fix can be attempted. This however varies on your device, you can install a different ROM using a custom recovery or... You can look for a factory image for your device and flash it (for those that have stock recoveries).
So I believe you should look around the net for a factory image for YOUR device.
Then flash it.
THANKS for the suggestion!! I'll try hard to look for that . I do have question what does "clear emmc" means?
Usually custom roms keeps the base from stock firmware rom.Well you can find any custom rom 4.2.2 for your model spec. extract from the zip your permission file and copy to your phone and then move it appropriate system folder and reboot .Don't forget to give permission file rw-r-r.
For all this procedure you must have Rooted phone.
DO NOT CLEAR EMMC!
Good luck
Sent from my SGH-317M using XDA Free mobile app
Can I use other O+ model cwm for my phone because i cant find a replacement . Sorry for being noob.
Well, you Can try this:
1.Go to recovery and check if there is "fix permissions" option.(maybe you will be Iucky)
2.Flash CWM recovery for your device and select "Fix permission"
3.You can go to recovery (stock) mode and fix permissions via adb (by using pc).
flashing an other recovery it's a bit risky
Sent from my SGH-317M using XDA Free mobile app
actually i press the clear emmc button once and nothing happens still the same.
my O+ 360 stock in BlackScreen After i Flash O+ 360 Rom , I Downloaded from Needrom.com ..
Related
I tried to go back to a stock rom and unroot my device by using the steps on the forum. What i have now is the unit comes on the asus logo shows but when it tries to boot up the screen is just black nothing happens. If i try to use an sd card with any thing on it doesn't read it. None of the files from the card show up in the menu. if have cleared the cache tried using the backup image that was on the device when i got it but still nothing. If you can help I would be grateful. I'm a noob to this rooting stuff. The only reason i brought it rooted was because of the price, I could not pass it up but after not getting some of the apps that i wanted to work if assume a rooted device is not for me.
jflynn0 said:
I tried to go back to a stock rom and unroot my device by using the steps on the forum. What i have now is the unit comes on the asus logo shows but when it tries to boot up the screen is just black nothing happens. If i try to use an sd card with any thing on it doesn't read it. None of the files from the card show up in the menu. if have cleared the cache tried using the backup image that was on the device when i got it but still nothing. If you can help I would be grateful. I'm a noob to this rooting stuff. The only reason i brought it rooted was because of the price, I could not pass it up but after not getting some of the apps that i wanted to work if assume a rooted device is not for me.
Click to expand...
Click to collapse
What instructions did you follow? Is the bootloader unlocked and can you boot into it? Does adb work? Need more info if we're going to help you.
It is rooted with
aokp-tf300t-build-38.
Android ver 4.0.4.
Kernel 2.6.39.4 g2bf1397-dirty.
Build IMM761.
bootloader unlocked
I was looking around in cwm menu before I tried to install the stock asus rom. Just going thru the menu's looking trying to familiarize myself with cwm. I went to backup and restore menu and there was Zip there. I hit to power button instead of the volume and it starting restoring the device. After that i have not been able to get it to do anything after the asus screen. But I can get into the menu of cwm. When i tried following the adb, i go into cmd on my computer and change directory it tells me the device is not ready. I tried putting a zip on a sd card but I cant get it to show on the device to install.
Try a factory reset in CWM, see if that helps.
tried the wipe data/factory reset several times with no luck. It goes through the process but still does not boot to any thing after asus logo.
jflynn0 said:
tried the wipe data/factory reset several times with no luck. It goes through the process but still does not boot to any thing after asus logo.
Click to expand...
Click to collapse
Can you flash a different ROM, maybe the stock one?
Had the same problem. Tried to flash stock from Twrp recovery.
Wipe do a factory reset, wipe system and than flash the aokp rom again.
Then reboot and when you are back in System you can put the rom you like on your internal SD.
Back to Recovery and flash the new rom.
I got adb working and it come up in devices list. How do i flash the aokp rom on the device. I'm learning this as i go along, after this i might get the hang of this . I cant seem to push files using adb either my directory is wrong. I unzip it into a folder (C:\romfolder\aokp_tf201_build-38.zip/sdcard) and all that comes up scrolling page of commands and help for adb when i push
this is the zip i dwl could not find built 38 for tf300 so i got tf201
http://aokp.co/index.php/releases/_/build-38-r24 also how do i make it an image to flash or can i download and image
jflynn0 said:
this is the zip i dwl could not find built 38 for tf300 so i got tf201
http://aokp.co/index.php/releases/_/build-38-r24 also how do i make it an image to flash or can i download and image
Click to expand...
Click to collapse
Do not flash a 201 rom or image. Thats for the prime. Never flash roms designed for another device no matter how similar they are.
ok I downloaded this on
http://goo.im/devs/termleech/tf300t/aokp_tf300t_unofficial_20120617_2100_build-39.zip
have to go to bed but when i get up this afternoon will try to get it o go to device.
How am I suppose to get it to the device if the sd card does not show up on file list in cwm?
Can you still use ADB? You can always push the files with that.
how do i use adb to push the file on to the device itself. because i can add it to the sdcard by just putting in on there and then placing sdcard in device but the menu as far as install zip from sdcard never shows any zips that are on the card itself. Only thing that shows up are list of directories that look like a standard list from cwm. Also if you choose any of directories from that list it returns no file found. If I choose apply update on sdcard no matter how many time i have called the file update.zip says "no such file or directory install aborted". Or how do i push and image to the restore section of the device and where do i find an image at?
well still no luck. I think I will give it a few more days and if I still cant get it guess will go to best buy and buy another on. Any thoughts on Toshiba excite?
Try this i posted a tutorial on how to fix this http://forum.xda-developers.com/showthread.php?t=1738825 hope it helps
The Problem:
When I select Clockwork Recovery Mod from the three button process, the phone reboots and the entire system gets a factory data reset.
What did I do wrong?
My mobile is rooted and running a Jelly Bean Rom. I did a Factory Data Reset from the system i.e. from within android not from Clockworkmod recovery menu and since then this problem has occured. It appears that factory data reset command is stuck somewhere in the boot.
Current Condition:
The Mobile is running perfectly fine without any problems. I can reboot and turn off the phone and it will load Android Jelly Bean Rom smoothly. The problem only happens when I try to access Clockworkmod recovery.
Solutions tried so far
I tried to reflash Clockworkmod image update from Mobile Uncle MKT tools, it rebooted the mobile and did a factory data reset of the system. The same thing happens no matter how many times I try.
I couldn't reflash Clockworkmod using rom manager as it does not recognize by device.
Was it working fine before?
Yes Clockworkmod was working absolutely perfect. I installed various roms from it and did backup of stock rom and even twice restored the stock rom.
Phone Specifications:
It is a local variant of a phone found in Germany going by the name of Mobistel Cynus T2 and as Micromax A110 Canvas 2 in India.
Would greatly appreciate any help.
You will be OK
Not psychic, but I think you loaded an incompatable version of CWM and then flashed, a buddy of mine just went through this, he didn't pay close enough attention or maybe its just some weird stuff in the universe-HA!
Ok, you are probably in recurring boot cycle, if you can get phone into boot mode, you know the combination of keys to be able to flash something!
Get to your computer and find the original OS that it came with out of the box, it will be a large download, it could be anywhere from 480 meg to darn near a gig.
Go get Odin 3.07 is the latest I think, anyway use Odin to flash the original OS. Start from out of the box fresh. It wouldn't hurt to stop by the play store after set up and get Triangle Away, it gets rid of the counter that is tripped when a custom rom is flashed.
Good Luck.
Fixed
1). Download the Stock Recovery Rom and CWM recovery Rom for Qmobile Noir A10 from here.
2). Download Mobile Uncle Tool from Play Store.
3). Rename the Stock Recovery Rom to "Recovery.img" and place it on the root of the SD Storage.
4). Open Mobile Uncle, grant it super user access and from its menu select Recovery Update.
5). Then select the Recovery.img (mentioned under the SD Card header), after which Mobile Uncle tool will prompt for a "Reboot in Recovery Mode" to which yes should be selected. If you have accidently selected "no" then you can select Reboot in Recovery from the main menu of the tool.
6). After the Reboot the mobile may not enter into Stock Recovery Mode and instead perform a Factory Data Erase of the android system so don't panic and repeat steps from 2-5. It happened with me therefore I am mentioning it here.
7). After you have successfully entered the stock recovery mode, reboot you mobile phone and let it load the Android Operating System.
8). Now rename the CWM Recovery Rom to "Recovery.img" and using it replace Stock Recovery Rom, mentioned in step 3, on the mobile's SD Card.
9). Open Mobile Uncle Tool again and repeat step no.5.
10). Upon reboot, your phone will be in CWM recovery mode.
Now do the robot dance and look like an idiot.
I recently changed back my build.prop to the original one that i backed up before. Then my device cannot boot anymore. It is stuck in the ASUS splash screen when i boot the device.
Then I flash the latest CWM recovery. But the latest version CWM cannot do anything like factory reset or flash zip.
After that, i tried to use the "wipe data" in the bootloader, it doesn't work either (still stuck in the splash screen).
And then i tried cold boot linux and it also doesn't work. Up to this point, I cannot find anyway to fix it.
However, I found that adb is somewhat working in CWM recovery. I tried "adb push build.prop /system/build.prop" (the build.prop is extracted from the US_epaduser_10_26_1_7_UpdateLauncher.zip package from ASUS official site), it doesn't work either.
I put the US_epaduser_10_26_1_7_UpdateLauncher.zip package from asus support site in sd card and tried to flash it by CWM recovery, it doesn't work either.
AFTER ALL THESE PROCEDURE, i think the system is corrupted because of some possible dirty wipe
IS THERE ANY WAY TO WIPE EVERYTHING AND RESET THE whOLE SYSTEM?
i feel like my device is completely dead... so i need help and solution asap
my device is unlocked, rooted, and updated to 10.26.1.7 android 4.3.
it is a US version.
btw i asked ASUS support and they said they would charge CAN$330 for fixing it (replacing the main board), which is.........
So is there any ways to fix it without sending it to asus repair ccenter?
I want to make sure that
1. The wipe data function in the bootloader works
2. Does wiping data in bootloader fix the build.prop problem
Or do anyone of you have any idea of solving tthis problem?
ANYWAY TO WIPE EVeRUTHING INCLUDES SYSTEM thROUGH BOOTLOADER?
sorry for my bad english
Have you tried to install Full Recovery Mode ?
First Enable USB Debugging and watch if your Device is correctly recognized on you Device Manager .
Search and install the software , for first use i suggest to search some Tutorials about this.
Then you can use the Full Recovery Mode and format / wipe cache and system .
So, my tablet, which has root access is stuck in a bootloop. I cause this doing the following: along the way I change the build.prop file to change the device ID in order to be able to install an app. Everything worked fine. I made a backup of the origininal build.prop file. Sometime later I replaced the altered buil.prop file with the original build.prop file. I rebooted the tablet and now it is stuck in a bootloop. I don't have any custom recovery installed and the computer doesn't recognize my device. I already tried factory reset and wipe cache numerous times. Nothing works. Ideas?
XDA Visitor said:
So, my tablet, which has root access is stuck in a bootloop. I cause this doing the following: along the way I change the build.prop file to change the device ID in order to be able to install an app. Everything worked fine. I made a backup of the origininal build.prop file. Sometime later I replaced the altered buil.prop file with the original build.prop file. I rebooted the tablet and now it is stuck in a bootloop. I don't have any custom recovery installed and the computer doesn't recognize my device. I already tried factory reset and wipe cache numerous times. Nothing works. Ideas?
Click to expand...
Click to collapse
Hello, and welcome to XDA! You could try to flash a custom recovery through fastboot, wipe and flash a rom. For your computer to recognise your device, you need to install the corresponding drivers on your pc.
Good luck!
Samsung Galaxy Tab 2
GT-P5110
Android version: 4.2.2.
Hi there, I have a rooted device running on CyanogenMod 10.1.3-p5110, with a custom recovery CWM 6.0.2.7
After 3 years (or so) of smooth operation it started to slow down and getting unstable from time to time, so I decided to factory reset.
I did the factory reset from CWM following the regular regular instructions, however after reset completion the devices booted back to the original CM10, with all the original data (nothing was cleaned at all or reset). I tried several times from - cleaning cache, date, system, dalvik cache, factory reset ... still the same result.
I also tried to replace the CWM with TWRP (GT-P5110_TWRP_3.0.0-0.tar.md5) - same result, it shows success but if I restart to recovery, it goes to CWM 6.0.2.7
If I boot into recovery (CWM) and flash any rom, it shows success and then reboots (guess what) into the original CM 10 like nothing happened.
I tried to flash the stock firmware using Odin. I got an original firmware "P5110XXDMI1_P5110OXXDMJ1_HOME.tar.md5" from a reliable source (sammobile)
Model:GT-P5110, Model name:GT-P5110, Country:Czech Republic, Version:Android 4.2.2, Changelist:1709803, Build date:Wed, 18 Sep 2013 06:13:11 +0000, Security Patch Level: N/A, Product code:XEZ, PDA: P5110XXDMI1, CSC5110OXXDMJ1
Every time I flash the original stock rom with Odin, the ID:COM box in Odin goes green and everything looks just fine but after reboot the tablet restarts to the original CM10. I was using Odin3-v1.85, as well as newer versions of the tool - namely Odin3_v3.07, Odin3_v3.11.1, all with the same result.
I even tried form very scratch - repartitioning the device using a .pit file "signed_espresso_20120220_16G.pit", flashing stock using Odin, same result.
I also tried flashing rom Heimdall Suite - same result
I have no problem to connect to the device using ADB shell and communicate with the device ...
However, I am not any Android guru, so I cannot "decode" what I get.
To me it seems like I somehow messed up my partitions or mounts and thats the reason for the strange behaviour.
So now I am stuck in strange state, which I cannot call a bootloop ... seems like I am running some sort of cached system or someting and I am unable to get out of with any standard tool available. As I said ... device is rooted, running CWM and I can boot to any mode I want ... download, recovery, system.
Any help will be more than appreciated.
You could have an faulty emmc firmware or your emmc reached end of life.
You are from europe? I know someone who can fix it for you.
You can also read the faq on my github userpage for more information about your bug.
kozyn said:
Samsung Galaxy Tab 2
GT-P5110
Android version: 4.2.2.
Hi there, I have a rooted device running on CyanogenMod 10.1.3-p5110, with a custom recovery CWM 6.0.2.7
After 3 years (or so) of smooth operation it started to slow down and getting unstable from time to time, so I decided to factory reset.
I did the factory reset from CWM following the regular regular instructions, however after reset completion the devices booted back to the original CM10, with all the original data (nothing was cleaned at all or reset). I tried several times from - cleaning cache, date, system, dalvik cache, factory reset ... still the same result.
I also tried to replace the CWM with TWRP (GT-P5110_TWRP_3.0.0-0.tar.md5) - same result, it shows success but if I restart to recovery, it goes to CWM 6.0.2.7
If I boot into recovery (CWM) and flash any rom, it shows success and then reboots (guess what) into the original CM 10 like nothing happened.
I tried to flash the stock firmware using Odin. I got an original firmware "P5110XXDMI1_P5110OXXDMJ1_HOME.tar.md5" from a reliable source (sammobile)
Model:GT-P5110, Model name:GT-P5110, Country:Czech Republic, Version:Android 4.2.2, Changelist:1709803, Build date:Wed, 18 Sep 2013 06:13:11 +0000, Security Patch Level: N/A, Product code:XEZ, PDA: P5110XXDMI1, CSC5110OXXDMJ1
Every time I flash the original stock rom with Odin, the ID:COM box in Odin goes green and everything looks just fine but after reboot the tablet restarts to the original CM10. I was using Odin3-v1.85, as well as newer versions of the tool - namely Odin3_v3.07, Odin3_v3.11.1, all with the same result.
I even tried form very scratch - repartitioning the device using a .pit file "signed_espresso_20120220_16G.pit", flashing stock using Odin, same result.
I also tried flashing rom Heimdall Suite - same result
I have no problem to connect to the device using ADB shell and communicate with the device ...
However, I am not any Android guru, so I cannot "decode" what I get.
To me it seems like I somehow messed up my partitions or mounts and thats the reason for the strange behaviour.
So now I am stuck in strange state, which I cannot call a bootloop ... seems like I am running some sort of cached system or someting and I am unable to get out of with any standard tool available. As I said ... device is rooted, running CWM and I can boot to any mode I want ... download, recovery, system.
Any help will be more than appreciated.
Click to expand...
Click to collapse
Once I had same problem with Motorola xoom and guess what was realy the problem. It was the external SD memory remove it then flash the stock rom.. If problem persists see with Andi
Thank you for your response. To me it also seems like faulty emmc. I have check the frequently asked questions on your blog and the description there exactly matches with what I'm experiencing on my device. Yes I am from Europe, Czech Republic. I have already tried to get in touch with two people who have the proper tooling to flash the firmware (JTAG). Hope I get some response fast and the solution is going to work. Still if you have someone in the CZ that you can recommend I'm grateful for any advice.
@zidane: All of the above steps where performed without external SD card.
kozyn said:
@zidane: All of the above steps where performed without external SD card.
Click to expand...
Click to collapse
Don't lose hope Try latest recovery 3.0.2.5 and the cm13 22/9 by Andi (made specially for certain cases like yours the files are in his folder the link in his signature ) if nothing happens then I guess dev Andi will be glad to help you fix your Emmc. contact him to provide you with the contacts..
Good luck
zidane01 said:
Don't lose hope Try latest recovery 3.0.2.5 and the cm13 22/9 by Andi (made specially for certain cases like yours the files are in his folder the link in his signature ) if nothing happens then I guess dev Andi will be glad to help you fix your Emmc. contact him to provide you with the contacts..
Good luck
Click to expand...
Click to collapse
@zidane01: thanx for cheerin' up
I have tried to replace my CWM 6.0.2.7 with TWRP 3.0.2.5, 3.0.2.6. from a .zip file using current recovery. Result is the same as described - after I reboot to recovery (using advanced option in CWM) it boots back to the original CWM 6.0.2.7. Flashing latest CM13 (as of 27/9/2016, downloaded from Andi's site) from CWM 6.0.2.7 ends with error. The tablet seems like READ ONLY not matter what I do. Maybe I am doing something wrong. I can describe the procedure step by step in detail, if you wish.
kozyn said:
@zidane01: thanx for cheerin' up
I have tried to replace my CWM 6.0.2.7 with TWRP 3.0.2.5, 3.0.2.6. from a .zip file using current recovery. Result is the same as described - after I reboot to recovery (using advanced option in CWM) it boots back to the original CWM 6.0.2.7. Flashing latest CM13 (as of 27/9/2016, downloaded from Andi's site) from CWM 6.0.2.7 ends with error. The tablet seems like READ ONLY not matter what I do. Maybe I am doing something wrong. I can describe the procedure step by step in detail, if you wish.
Click to expand...
Click to collapse
sounds like that you have a faulty emmc. same what android-andi said.
@kozyn Hi buddy.. have the same thing on a p5110 -- emmc is in read only mode and I can't seem to PM Andi for some contacts.
Can you help me recover this galaxy tab2 pls? Appreciate your time