Hello, immediately sorry for my english I hope you understand me
Well... When I wanted to upload ROM into my Lenovo ive loaded TWRP, displays the recovery. After removing wipe, date, it turned out that I can not upload MIUI rom V6. So I reset the phone, switched to the main screen without a problem. Now, however, he does not see the recovery. When I click "update recovery" in the MTK Tools and click on to recovery, the phone resets twice and returns to the main screen. This is the first problem. The second problem is that when I made the root my phone and removed some applications the system appears in the bottom corner, "security problem" and pops up all the time to install Antivirus advertising. I'd most like to upload ROM if someone could help me I was grateful. Regards.
Related
I've had Cyanogenmod 9 nightlies on my SGS2 since April. I didn't install every single one, but pretty much only those with good ratings, specifically those that had no complains about battery drain and heating...
Currently on the 06-28-2012 nightly. This ran fine at first, but over time, it started to occasionally crash into Kernel Panic. I figured I'd just pick a new nightly, but then I ended up having to travel and installation of a new nightly got delayed.
Now I'm home, and I can't use the phone at all, cause it crashes into Kernel Panic almost as soon as I unlock the screen after Android finishes booting. The last thing I see up in the message bar is "WhatsApp error" and the screen goes dark. It won't stay on long enough for me to uninstall WhatsApp or select factory reset from the system menu.
I don't think its a problem with WhatsApp, cause WhatsApp used to run fine, while Kernel Panics originally mainly seemed to happen after I got a "storage full" message. In response, I deleted a load of pictures after rebooting, to make sure there's free space, but it kept crashing occasionally, till now, its just unusable.
I've tried to flash a stock Samsung ROM (I9100XWLPG_I9100XXLPX_I9100NEELP4_HOME.tar.md5) but that hasn't been working either.
Kies drivers are installed on my Laptop. Odin sees the phone too.
I followed the instructions from the rom page, changed no settings in Odin, just picked PDA and selected the ROM.
Odin goes "Added" when I plug in the phone, verifies the ROM, then the whole thing hangs on "setting up connection"
So I unplug, pull the battery and then reboot, which works fine, but once booted, it won't stay on longer than a few seconds.
Anyway, does anyone have any clever ideas how I can get out of this Kernel Panic loop?
Tsais said:
It won't stay on long enough for me to uninstall WhatsApp or select factory reset from the system menu.
<snip>
Anyway, does anyone have any clever ideas how I can get out of this Kernel Panic loop?
Click to expand...
Click to collapse
What's preventing you from factory resetting from recovery?
Lack of knowledge is preventing me!
How do you factory reset from the "Kernel Panic Download Mode"...?
Download Android Commander from here:
http://androidcommander.com/
Boot your phone, don't unlock.
Start Android Commander, navigate to /data/apps and delete WhatsApp's apk (com.whatsapp1.apk or something like that) or rename it to .apk.bak
Restart your phone without unlocking.
Hope the errors gone.
Hi everybody thanks for your help in advance,
My SGs2 is currently running siyah kernel v6.0.0.12 (the fancy one with touch recovery and dual boot).
The problems started when i recently switched from SuperSu to the open-source alternative Superuser. I'm using an app called live logcat (by Chainfire). It shows the logcat entries live as a boot animation. It was all hassle free when I used SuperSu with it. After switching to Superuser it kept getting root permission over and over for at least a minute (a previously common problem). So I was looking forward to getting it fixed since other users reported the same problem. So whenever a new version came out, I tried if it was finally fixed.
After updating to the latest version yesterday and starting the app once again, the phone crashed with the screen turning black (status bar still visible). It then rebooted and a message stating
Android is upgrading..
Starting applications
Click to expand...
Click to collapse
appeared. Whenever I reboot my phone this message appears and won't go away. I can access recovery but clearing cache and/or dalvik cache makes the window say: Optimizing application <x> out of <y>. When it is through with optimizing, 'starting applications' reappears.
I honestly have no idea what else to do.
So my question is how can I get that darn thing to boot correctly?
I'm looking for a solution which doesn't involve factory reset.
If anybody can help he/she is much appreciated.
Hi All
I've got a Samsung Galaxy S2 (GT-I9100G) for over 2 years UNROOTED , yesterday, I rooted it and all went successfully and smoothly in a way I didn't believe that I done it :angel: , but unfortunately I tried to change my System theme , boot animation and installed one of themes offered by "ROM Toolbox Lite" app , then it prompts me to reboot in order for the changes to take place, I done.
The Problem, when it reboots it didn't change any of the boot animation, and when I swipe the screen in (Swipe the screen to unlock) window It freezes and reboots again and again.
One of the solutions I've tried is to Unroot my mobile phone and all went successfully but the problem remains the same! Couldn't enter my home screen to remove the theme , moreover, I tried to wipe system/factory data, to return to main factory settings and nothing changes! , to make matters worse , I wiped the cache partition , when I reboot the phone I got an error message saying :
"App (COMANDROIDUI) stopped unexpectedly . Please try again later", I tabbed on "Force close" then the status bar vanishes and phone freezes for 4 seconds and reboots again :crying: , btw, it shows to me the screen of green android avatar which means that it successfully reset to default factory settings, I didn't flash any custom ROM or made any changes to kernel or firmware.
Now I couldn't open my phone any more :crying:
Any one help me pleaaase , U could assume am a noob
Thanks in advance
Solution From thread owner
Omar_Elboredy said:
Hi All
I've got a Samsung Galaxy S2 (GT-I9100G) for over 2 years UNROOTED , yesterday, I rooted it and all went successfully and smoothly in a way I didn't believe that I done it :angel: , but unfortunately I tried to change my System theme , boot animation and installed one of themes offered by "ROM Toolbox Lite" app , then it prompts me to reboot in order for the changes to take place, I done.
The Problem, when it reboots it didn't change any of the boot animation, and when I swipe the screen in (Swipe the screen to unlock) window It freezes and reboots again and again.
One of the solutions I've tried is to Unroot my mobile phone and all went successfully but the problem remains the same! Couldn't enter my home screen to remove the theme , moreover, I tried to wipe system/factory data, to return to main factory settings and nothing changes! , to make matters worse , I wiped the cache partition , when I reboot the phone I got an error message saying :
"App (COMANDROIDUI) stopped unexpectedly . Please try again later", I tabbed on "Force close" then the status bar vanishes and phone freezes for 4 seconds and reboots again :crying: , btw, it shows to me the screen of green android avatar which means that it successfully reset to default factory settings, I didn't flash any custom ROM or made any changes to kernel or firmware.
Now I couldn't open my phone any more :crying:
Any one help me pleaaase , U could assume am a noob
Thanks in advance
Click to expand...
Click to collapse
Finally, got a solution that suggested I download the original firmware and flash it.
I successfully done it and surprisingly, I got back my phone
If anyone got a problem like this feel free to ask about it
Hi
My friend sold a TeXet 9768HD to a someone.
Now the customer returned it with a wired problem.
When the tablet boots up and loads OS (Jellybean.rus.texet 4.2.2), "unfortunately fingerprint unlock has stopped working". It show this error nonstop, every time i click on "OK" it comes back in a blink, with lots of pain! i went to Settings then Apps and saw this "FingerPrint Unlock" there, But like system apps it doesn't have "Remove/Uninstall" option. I can't install anything on it, because this error message is on the screen all the time.
So i tried to use both "Force Stop" and "Disable" options, but regardless of that the error still comes up.
I've no idea what to do. My friend asked me to flash it, but since (obviously) TeXet no longer is active, there's no support.
"Wipe/factory reset" and "Clear cache" in recovery didn't solve the problem too.
When i pluged it to PC, it can't be recognized. But after installing "Rockchip Tool" not Flashing tools seems to show it.
Now the question is:
1st What is that problem and is there any way to solve it without flashing?
2nd if not what ROM would you suggest me to flash on it?
Thanks
Hi guys please help me i need to have my phone working back |:.... today i updated my wiko fever 4g but i got an error... now when i boot it an android icon shows with "no command." text. Tryed with v.39 program on wiko website but its not working for me... when arrow becomes green download wont start.
I'm thinking to recover system fom sd card but i cannot find roms please help me |: thanks in advance
Same issue here... Finally decided to upgrade the system from stock firmware, and got "error" when it rebooted the phone. Then "no command".
Darknezz89 said:
Hi guys please help me i need to have my phone working back |:.... today i updated my wiko fever 4g but i got an error... now when i boot it an android icon shows with "no command." text. Tryed with v.39 program on wiko website but its not working for me... when arrow becomes green download wont start.
I'm thinking to recover system fom sd card but i cannot find roms please help me |: thanks in advance
Click to expand...
Click to collapse
I solved my issue by restoring Lollipop (v.39) with the tool from the wiko website and then performing the update again; the phone started again (at v.41) and I was able to download Marshmallow from the next system update.
Issue was probably caused by some configuration or application.
Still slowly downloading Marshmallow now, so cannot say anything about the next update, but I guess that will go well, since the phone is reset now.
Just to follow up: Marshmallow is working fine on my Wiko Fever, much better than Lollipop. Amazing update.
Instructions for others after having read some comments from other people experiencing issues with the upgrade:
- BACKUP all your data before upgrading from Lollipop to Marshmallow, as if you would buy a new phone; I luckily did, as I wanted to set the microSD from removable to internal
- remove the microSD and (after having a backup of all your data as per step above) format the card as FAT32 on your PC; better to have a clean MicroSD card for after the upgrade I think
- reboot the phone in recovery mode and do a: wipe cache+reset to factory settings
- once the phone is reset and started, proceed with upgrading to Marshmallow
- don't know if needed after the upgrade to do an additional wipe cache+factory settings reset, doesn't harm to do it though
- be unhappy for the hours lost in restoring the phone data + apps + reconfigure everything
- be happy of the improved phone software
Questions upon questions.
So, i got the notification for the update last week, and i saved it until today to install it. The file downloaded was just 7 mb, i had enough battery for the intallation of the update (30% recomended by the software), something got messed up and an error message with the dead android character appeared. I know i lost all my things contacts and sd card... tried to hard reset the damn thing and nothing. I already googled the problem and i found nothing similar to what i get, i'm stuck in the recovery screen and the phone doenst shut down, every time i force it, it just boots back up after 15 30 seconds. I got to be honest i tought it was just another update but aparently its a "new" operating androind system. They could have told me with a update log or something...