Hello
Just received OTA update to MARSHMALLOW. After downloading I did run the install. Various steps run OK including the 156 ( or more) application optimization. New restart up to the lock screen, but then immediate reboot.
Now the phones is stocked in this bootloop.
By pressing volume down and power together I was able to access Fastboot. I tried to enter Recovery mode but I got the Android with "no command" message.
How to proceed to recover my phone?
Thanks
That is Recovery.. that is what it looks like.
The fact you did not know that yet know how to get into Recovery tells me one thing.
You most likely have already used custom stuff on the phone such as TWRP, Root etc.
Then you installed an OTA for Marshmallow which has a new level of security.
I would have started by providing details on what model of phone you have and
what OS you were running before hand and what version of it and if you were rooted or had TWRP installed etc.
Saying.. "i clicks on teh Marshmallows Installs an it's no works"
Is not going give people here much to go on to TRY and help you.
And did you search this forum help section ?
Because the same questions get asked non stop.
So much that most people don't reply to them anymore..
Each guy that has a problem creates his own new topic
so he can have repeated for him the same thing the last 100 guys were told.
Hello
My model is SM4163AD1E1
The phone has never been rooted.
It was running only official ROM received by OTA from manufacturer.
I try to remember which version it was running before ? Probably 5.1
I tried to search on the forum, but I didn't found anything related to the brand new update to 6.0 leading to bootloop !
Related
I am an android noob and I have been very frustrated because the OS boot setup does not allow me to control which apps will boot-up at start. I’ve tried various startup managers and none of them can keep apps disabled as they seem to auto start themselves so I have to constantly close apps in order to preserve resources.
I Then sought to root phone to gain control by using a collection of root apps; Universal Androot – v1.6.2 beta 5, 6 & 7, z4root & Super One Clickv2.2 all w/o success. I do not know why they failed only that these apps seemed to do no harm to the phone otherwise. The phone is a Samsung Galaxy I5500M through PC Mobile, the carrier being Bell Mobile. The following is the particulars on the phone:
Model number: GT-I5500M
Firmware Version: 2.1-update1
Baseband version: I5500MUGKE3
Kernal version: 2.6.29-perf [email protected]#1
Build number: ECLAIR.UGKE3
When I dial *2767*4387264636#.
Product code: GT-I5500YKMBMC.
When I dial *#1234# I get;
PDA: I5500MUGKE3
CSC: I5500MUGKE3
Phone: I5500MUGKE3
I have an acquaintance that has the same phone from the same source that attempted to install a custom ROM using the method outlined on the madteam website "cyanogenmod-7-installation-guide-for-g5-users"
Unfortunately after rebooting that phone it simply boot looped on the Samsung & Android logos. After many attempts to fix boot loop the phone was put aside, to my knowledge that phone has yet to be repaired.
Anyway, I really want to take control of this phone but am afraid of bricking it. Any help to be able to at the very least root it or even better to install a custom ROM would be very much appreciated. Thanks very much to all those that have contributed to this forum… it is amongst the most informative I’ve come across.
Hello there!
If your phone isn't rooted you won't be able to install a custom rom or anything, so I shall try and help you as much as I can, I'm a noob at this kind of stuff too so I'd wait for somebody to confirm what I say before you try it.
I rooted and installed Superuser on my I5500 using Universal Androot, took a few tries though so it might be worth trying it again.
Basically, can you put your phone into download mode? (Turn off device, hold down power button and the volume buttons and it should boot into Download Mode) If so then you could install Clockworkmod (Don't hold me to this, wait for some confirmation from someone with more knowledge) I'm not sure if your device has to be rooted to flash Clockworkmod v4. Even if it doesn't then surely accessing Download Mode and opening KIES will allow you to reset your device and get out of the boot loop.
Here is how to install a custom rom- I use Cyanogenmod 7.1, I'd recommend that to be honest, plenty of customization and many options to tweak performance.
Root your device (I use Universal Androot, it worked for me)
Flash Clockworkmod v4 via Odin.
Put the 3 Cyanogenmod files onto your SD Card.
Reboot into recovery on your device.
Select install update from zip.
Select the 3 files in the specific order.
Wipe data, cache and dalvik cache then reboot.
Then you're running CM7.1.
You can find the files and a more in-depth guide on the Development section under our phones name.
I hope I have helped a bit.
oh I almost forgot, have you tried hard-reseting your device by holding down certain buttons in a specific order? If so then you can reset your phone like that and maybe sort out the boot issue, should fix it, but again don't hold me to it. Hold down the menu/home key, volume key and power off button whilst your device is turned off and that does a hard reset.
Hi CurtisAndroid5,
Thank you for responding. To give a little history I have tried repeatedly using Universal Androot – v1.6.2 beta 5, 6 & 7, z4root & Super One Clickv2.2 to able to gain Superuser access all w/o success. As far as the custom ROM... that would be the ULTIMATE! But as mentioned on the original post there is someone I know that has possibly bricked one using the exact instructions outlined by the madteam when installing cyanogenmod-7 & spent weeks trying to solve a boot loop... still not fixed. The only reason I have not attempted to do this is I don't want to see the same result.
I have literally booked marked a dozen or more threads, have read hundreds of posts trying to find a solution to rooting this Bell Samsung phone. In my searches I've found on Samsung Open Source website a zipped update; "GT-I5500M_OpenSource_eclair_update2" that I no idea how to use. I honestly think that there are some subtle differences in how Bell sets up their phones that prevents rooting & Superuser access.
I will delve deeper into your suggestion and view posts under the Development section under the phone name. Again your response is deeply appreciated. Thanks!
Ah I see, like I said, I'm not the most experienced person in this kind of stuff so I can't help you any more seen as though my knowledge is limited. I hope you managed to sort your phone out, it will probably be a minor error and will be easily fixed, your G5 will be an amazing little phone once you get it rooted and installed a custom rom!
I had the same problem with my samsung i5500, i just got odin, flashed clockworkmod with it then put in my custom rom, i'm currently on cyanogen mod 1.7.2
CurtisAndroid5 said:
your G5 will be an amazing little phone once you get it rooted and installed a custom rom!
Click to expand...
Click to collapse
I wish mine was -.-
Hi I have Motorola Defy phone, which is rooted and I already update it on Android 4.1 once. But I wanted to make some changes so I made new update with this version: cm-10.2-20130801 and mini GAPPS both from this thread: http://forum.xda-developers.com/show....php?t=1768702. But when I try to start a phone the note: "Setup Wizard has stopped working" shows up and i can't do anything with that.
So I tried to get in recovery mode and install another version, but the yellow exclemation mark with green android (which apparently shows up in phones without root) shows up and then i can get in something like recovery mode in unrooted phone. There are only 4 options.
I'm starting to get really desperate because I really don't know what to do. I'll be very glad if somebody can help me and I'm considering some kind of reward for helping me.
Thank you.
Hey lovely ladies and gents,
So here is the situation: I have an LG Optimus l70 MS323, which until yesterday was with a stock ROM. I banged my head against the wall, trying desperately to follow a guide and root it, along with trying to unlock the bootloader until I watched a video (in Spanish. Thank you high school spanish!) which used flashify to flash a CWM and boot to the custom recovery. I loved it, since that meant that I would be able to finally flash an official Cyanogenmod OS. The first ROM that I flashed was cm-13.0-20160121-NIGHTLY-w5.zip, which worked and made me feel SO HAPPY (I almost yelled Eurika for the sake of historical comedy). I then went ahead and installed an Superuser-SU binary update through the CWM recovery because I wanted to keep on having root. Then I installed a nano gapps package for ARM, Android 6.0 with some minor complications (mostly the "Setup Wizard" crashing every 2 seconds). I rewiped and reinstalled Cyanogenmod through CWM, flashed gapps on the same go, and made a little backup through the recovery menu. I booted up successfully to be met with that buttery-smooth GUI of Marshmallow (ugh, so good.) I decided to go ahead and fetch some apps from the Play Store, such as Messenger and ROM manager. I saw that the Cyanogenmod Update Center had pushed out a notification that the newest nightly snapshot is already downloaded and decided "Meh. What new features have been added? Let's reboot and reinstall." At that point it was 4:40am (keep in mind that I've been trying to get the goddamn phone to cooperate since ~10pm) and I noticed that the boot sequence takes up a lot longer and told myself "It's probably taking a bit longer than usual, it's normal." I put the phone next to my head, hoping that it's going to be ready to use in the morning.
Fast forward to 8:07 am. Bootloader is still going, phone is so hot it can cook an egg.
GNAAAAAAAAAAAAAAAAAAAHHHH. WHY YOU GOTTA DO DIS TO ME PHONE?!??! WHY!?!
SO, the CURRENT situation:
1. Whenever I press the power button, it starts off normally. According to my definition of bootloop, it's stuck in a bootloop.
After hours of staring that goddamn cyanogenmod mascot do you realize that it's going to boot itself into the booting oblivion.
2. I don't have access to CWM. I have tried holding down the power buttons with godknowswhat combinations (I like to call them the Naruto Jutsu of pure despair). Maybe I should hold the buttons for 2 milliseconds longer and it might work. *Sigh*
3. I don't think that I can use fastbood or adb. My computer doesn't see the phone. (GNAAHHAHASDJFLSKDHFSLJHLKJ.)
4. I am totally clueless about what I should do or try. I've basically softbricked my phone and don't know how to unbrick it.
So, now that you see that saying that I'm frustrated is truly an understatement, what do you suggest I do?
In advance, I'd like to thank you SO MUCH for even giving a sh!t about my problem.
Other misc info: I have a 32GB SD card on which I have all the different tools I have used throughout this journey.
I am willing to have it back on stock ROM. My biggest goal is to somehow boot into CWM recovery. From there on, I will be able to deal with it. Until I come back to this forum, begging for mercy.
Have u tried using LG suite or LGUP u need to go to LG 's firmware page I'm not sure about this phone but it worked w my k7 about 100 times also helped unlock it. Check out the LG k7 forum lots of guys on there that use the lgup program and can help
Hi guys!
I own a Samsung Galaxy S Wifi 3.6 (Europe version) since december 2012. I actually want to give it a new life (it was my first Android device) by rooting it and maybe installing a custom ROM. While searching on XDA forums, I discovered that thread, I absolutly wanted to test it, and now I'm blocked at step 5: I can't access recovery mode.
The problem is, when I'm holding buttons to access recovery, it simply starts my device launching Android system. I tried like 50 times to access recovery mode. I'm using ODIN, and I was able after that failed try to recover a stock, working system of my Samsung (I can use it, but it is still the same old 2.3.6 Android version).
I want to point that I'm not a newbie in modifying Android devices: I'm playing everyday with my incredible Nexus 7 2013. And I remember that I accessed recovery mode maybe in July-August 2013, before sending my device to the vendor, who fixed it and sended it back to me (so it's still the same device). And if I start a thread rather than writing a new post in previously quoted thread, it is because I think that my device is the only problem.
If anyone can help me, by suggesting something or completly solving my problem, I will just love him. ^^
Thank you in advance!
Nierven said:
Hi guys!
I own a Samsung Galaxy S Wifi 3.6 (Europe version) since december 2012. I actually want to give it a new life (it was my first Android device) by rooting it and maybe installing a custom ROM. While searching on XDA forums, I discovered that thread, I absolutly wanted to test it, and now I'm blocked at step 5: I can't access recovery mode.
The problem is, when I'm holding buttons to access recovery, it simply starts my device launching Android system. I tried like 50 times to access recovery mode. I'm using ODIN, and I was able after that failed try to recover a stock, working system of my Samsung (I can use it, but it is still the same old 2.3.6 Android version).
I want to point that I'm not a newbie in modifying Android devices: I'm playing everyday with my incredible Nexus 7 2013. And I remember that I accessed recovery mode maybe in July-August 2013, before sending my device to the vendor, who fixed it and sended it back to me (so it's still the same device). And if I start a thread rather than writing a new post in previously quoted thread, it is because I think that my device is the only problem.
If anyone can help me, by suggesting something or completly solving my problem, I will just love him. ^^
Thank you in advance!
Click to expand...
Click to collapse
Did you try: adb reboot recovery?
Hi All,
I have a Huawei Enjoy 7 - Model SLA-LA00 (running Nougat 7.0, EMUI 5.1, Boot is unlocked).
I'd like to root it, but I've tried Kingoroot, King Root, iRoot etc and it repeatedly fails. On checking it seems that my device isn't compatible with those apps. I would like to use the ADB method, but there's no custom recovery image for the SLA-LA00, I've also checked and it seems, there isn't but please correct me if I'm wrong.
Is there a custom recovery available for my model?? Also, I've tried looking but, is there an International firmware for this model??
Any assistance would be appreciated, thanks.
Regards,
marquez010
Hello, was going to create a new thread, but think yours fits what I need to ask aswell.
Same phone here, bought it in Shanghai and now in Brasil, was trying just to make it google able. Salesman at the official Huawei store tricked me to think it would just need access to a open network for it to work. Silly me.
Well, as you, unlocked it with ADB and with no answers from nobody, tried to flash it with a random TWRP. Obviously didn't work. Now the phone wont boot into system, but i still can manage to put it in fastboot mode and it still replies to ADB.
Question is if someone that knows better than me can tell me what to do to at least get back where I was, before I finish killing this damm stupid phone, wich also doesn't seem such bad idea.
lucasresende said:
Hello, was going to create a new thread, but think yours fits what I need to ask aswell.
Same phone here, bought it in Shanghai and now in Brasil, was trying just to make it google able. Salesman at the official Huawei store tricked me to think it would just need access to a open network for it to work. Silly me.
Well, as you, unlocked it with ADB and with no answers from nobody, tried to flash it with a random TWRP. Obviously didn't work. Now the phone wont boot into system, but i still can manage to put it in fastboot mode and it still replies to ADB.
Question is if someone that knows better than me can tell me what to do to at least get back where I was, before I finish killing this damm stupid phone, wich also doesn't seem such bad idea.
Click to expand...
Click to collapse
Hi , all you have here :
https://www.getdroidtips.com/huawei-enjoy-7-b161-nougat/
Hey, thanks a bunch. Found that post before, but it looks like its for an older version of this phone. Mine was running b190 nougat. Don't know if should try to flash this one, but if no other ideas, will try it.
Well, was able to boot it again. Flashed it with yet another twrp that i found for a similar (or so i think) huawei and even tough it didn't work, when I connected the phone to the charger and it responded the power up volume combination and allowed me to reboot normaly.
Guess I'm back to where I started. Think now is better to wait, maybe there wiil be a moe suitable release of a gms core package that it requires for google play to work (have it, but installation fails on rebbot) or twrp updates with a version that works for me and then I can try to install gapps thru it.
Back to my old crappy lg now.