Related
Hello there,
I've just got a Nexus S which has ICS installed. I must say I've used Android before but am no expert, especially when it comes to the whole ROM scene. While I am a very technical user, from my online research I haven't yet been able to figure out how to best go about the downgrade to 2.3.6.
My concern being that this is not stock anymore and I would not want to brick it by treating it as stock and simply following the standard downgrade or ROM flash directions.
I am attaching a screenshot for everyone to see exactly what I've got on the device.
Any help with this would be immensely appreciated!
Cheers.
Since you said you're a technical user I assume you know how to use fastboot and stuffs. To downgrade to GingerBread, you only need to install a custom recovery (ClockWorkMod) for your phone model and flash a full OTA package. I guess that's all
Well if the phone already has ICS installed, I'm pretty sure it also has Clockworkmod Recovery(aka. CWM or CWR).
Try this:
Turn off your phone.
Turn it on by HOLDING DOWN the power button AND the volume up button. After 2-3 sec. you should see a menu. Scroll down 2 clicks with the volume down button, you should land on 'Recovery '. Press the power button to enter CWR. (Clockworkmod Recovery)
If this procedure takes you to another menu, then you have a functioning CWR. And if so, I would recommend trying one or more of the fine roms in this forum under 'Android Development'. Many of these roms have a lot of features and fixes that you would miss once you've had them.
Try it out, and happy flashing.
PS. To flash most roms, download the rom on your mobile. (it's a zip-file) and go to CWR. Choose 'wipe data/factory reset' and then go to 'advanced' and there you should choose 'wipe dalvik cache'. Go back, choose 'install zip from sdcard' and then 'choose zip from sdcard'. Locate the rom you downloaded and choose it. This will flash the rom. Go back and choose 'reboot system now'. The first boot on any rom will allways take longer than usual. Usually about 2min. Enjoy! ;-)
Sent from my Google Nexus S using xda premium
swaipa said:
Well if the phone already has ICS installed, I'm pretty sure it also has Clockworkmod Recovery(aka. CWM or CWR).
Try this:
Turn off your phone.
Turn it on by HOLDING DOWN the power button AND the volume up button. After 2-3 sec. you should see a menu. Scroll down 2 clicks with the volume down button, you should land on 'Recovery '. Press the power button to enter CWR. (Clockworkmod Recovery)
If this procedure takes you to another menu, then you have a functioning CWR. And if so, I would recommend trying one or more of the fine roms in this forum under 'Android Development'. Many of these roms have a lot of features and fixes that you would miss once you've had them.
Try it out, and happy flashing.
PS. To flash most roms, download the rom on your mobile. (it's a zip-file) and go to CWR. Choose 'wipe data/factory reset' and then go to 'advanced' and there you should choose 'wipe dalvik cache'. Go back, choose 'install zip from sdcard' and then 'choose zip from sdcard'. Locate the rom you downloaded and choose it. This will flash the rom. Go back and choose 'reboot system now'. The first boot on any rom will allways take longer than usual. Usually about 2min. Enjoy! ;-)
Sent from my Google Nexus S using xda premium
Click to expand...
Click to collapse
Not necesarilly, CWM not always remains flashed and have to reflash repeatedly. Try what was recommended here, if not, download Rom manager and reflash.
That worked. Turns out I already had everything I needed to install from an archive.
So I downloaded the official 2.3.6 full ROM and got it installed.
The problem I am facing now is that as soon as the phone boots up, I get a sequence of errors, the first one being "The process com.google.process.gapps has stopped unexpectedly. Please try again."
This gives me a "Force close" button, and that's about it. Then there are subsequent errors for android.process.acore, com.android.providers.calendar and then it just sort of loops back and forth between those.
Unfortunately the problem here being that I cannot tap the Android to get started or anything like that. It looks like I am pretty much stuck.
swaipa, I followed your instructions and everything worked seamlessly.
Any clue as to why I am getting all of these issues now?
Edit: nevermind, I just did the same thing again and it seems to be working well!
Kudos my friend, you're on to a life of flashing.. ;-)
Sent from my Nexus S using xda premium
cant go beyond recovery menu using i9023 with ICS any ideas ?
I able to downgrade from 4.0.3 to 2.3.6
Here is what I did...
http://kishanrathod.blogspot.com/2011/12/downgrade-nexus-s-from-403-to-236.html
hey
http://en.miui.com/a-1.html try this steps and it will work.
At "Downloading flashing tools and ROM pack" instead of ther rom, you should download the official OTA for your model from here http://forum.xda-developers.com/showthread.php?t=1063664.
good luck...
i have a i9023 a put first 2.3.3 and i make de update to 2.3.6.
good luck!
just a question please :
What does "install unlocked boot" or "fast boot" mean , Will it unroot the device ? and after that , If I will install a stock 2.3.6 ROM , will I return 100% factory (including the stock recovery) ?
i`ve check my recovery and it is stock like i had before.
after you finish downgrade LOCK the device using UNLOCK start bat and write LOCK instead of UNLOCK.
euskode said:
That worked. Turns out I already had everything I needed to install from an archive.
So I downloaded the official 2.3.6 full ROM and got it installed.
The problem I am facing now is that as soon as the phone boots up, I get a sequence of errors, the first one being "The process com.google.process.gapps has stopped unexpectedly. Please try again."
This gives me a "Force close" button, and that's about it. Then there are subsequent errors for android.process.acore, com.android.providers.calendar and then it just sort of loops back and forth between those.
Unfortunately the problem here being that I cannot tap the Android to get started or anything like that. It looks like I am pretty much stuck.
swaipa, I followed your instructions and everything worked seamlessly.
Any clue as to why I am getting all of these issues now?
Edit: nevermind, I just did the same thing again and it seems to be working well!
Click to expand...
Click to collapse
im also getting this same issue from installing GB via odin.
cant work out how to fix it.
i dont fully understand swipa's instructions there
Hi!
My P500 was originally Gingerbread 2.3.3, than I used CM 7.2 with AmonRa 3.0.6 recovery for a year.
So I tried to flash KitKat (http://forum.xda-developers.com/showthread.php?t=2589303), and got some issues.
I flashed ClockworkMod Recovery 6.0.4.6 (Jan/14), than the ROM (v8), and the installation worked well.
Before the reboot, CWM says:
"root access possibly lost. Fix?
this can not be undone"...
Whatever I choose, I got that black screen with
"fastboot mode started
udc_start()".
Thaaaan, I see this: http://forum.xda-developers.com/showthread.php?t=2439466
and tried to downgrade SU to v1.55. But the CWM got an error, and cannot install (even with AmonRa)...
After all, I can't get KitKat working, and got back to AmonRa recovery and CM 7.2.
To complete the "good vibe", my Android can't get AT ALL connect through USB, so I can't test any ADB command.
I don't know where I'm doing wrong... Any directions??
Thanks!!!!
SOS
This^. Exactly this is what I am suffering from right now and I am amazed how identical the issue is. I hope the OP doesn't mind if I added some more info since I didn't wanna create a new thread when one is already made recently.
Here is some info in brief regarding my issue.
Last OS: CynogenMod 7.2
Last CWM: 5.0.0.X
Target OS: Cynogen KittKat
Target CWM: 6.0.4.6 [January 2014 release]
Downloaded KittKat Rom from here: http://forum.xda-developers.com/showthread.php?t=2589303
Downloaded CWM from here: http://forum.xda-developers.com/showthread.php?t=2564767
Everything went fine when I flashed the CWM first and it entered the new recovery mode without a hitch. But the trouble began after I flashed the KittKatt Rom. Though initially everything installed just fine but in the end just before restart, this came:
"root access possibly lost. Fix?
this can not be undone"...
For safe measure I chose "Yes" and that's where my phone apparently got "soft-bricked" cause it rebooted into fastboot mode with this message
"fastboot mode started
udc_start()".
I looked around and found a "solution" for this kind of issue here: http://forum.xda-developers.com/showthread.php?t=1088046
I followed instructions to the letter but my the LG Mobile support tool refused to identify my phone. Since I figured it might have been a driver issue so I installed PDAnet instead to get stuff working. The only hitch was that PDAnet would hang on "Updating PDAnet to your phone" option. I sat their staring at it for an hour or so and figured something was wrong like my phone wouldn't allow to install anything on itself since my debugging wasn't enabled, though I am not sure about this one.
In any case I checked device manager and my ADB drivers were fine so I ran the three recovery commands in DOS anyway and they all executed without a hitch. I jumped for joy but my happiness was short lived since the phone booted back into recovery mode and now I am basically stuck up the creek without a paddle. I could really use some expert advice here just like the OP cause I really am not sure what went wrong and where. I would really like to fix this rather than flash and start the whole phone up from scratch if possible.
Regards,
LonerPrime
PS: Long time reader but this is my first post here so greetings to the xda community.
LonerPrime said:
This^. Exactly this is what I am suffering from right now and I am amazed how identical the issue is. I hope the OP doesn't mind if I added some more info since I didn't wanna create a new thread when one is already made recently.
Here is some info in brief regarding my issue.
Last OS: CynogenMod 7.2
Last CWM: 5.0.0.X
Target OS: Cynogen KittKat
Target CWM: 6.0.4.6 [January 2014 release]
Downloaded KittKat Rom from here: http://forum.xda-developers.com/showthread.php?t=2589303
Downloaded CWM from here: http://forum.xda-developers.com/showthread.php?t=2564767
Everything went fine when I flashed the CWM first and it entered the new recovery mode without a hitch. But the trouble began after I flashed the KittKatt Rom. Though initially everything installed just fine but in the end just before restart, this came:
"root access possibly lost. Fix?
this can not be undone"...
For safe measure I chose "Yes" and that's where my phone apparently got "soft-bricked" cause it rebooted into fastboot mode with this message
"fastboot mode started
udc_start()".
I looked around and found a "solution" for this kind of issue here: http://forum.xda-developers.com/showthread.php?t=1088046
I followed instructions to the letter but my the LG Mobile support tool refused to identify my phone. Since I figured it might have been a driver issue so I installed PDAnet instead to get stuff working. The only hitch was that PDAnet would hang on "Updating PDAnet to your phone" option. I sat their staring at it for an hour or so and figured something was wrong like my phone wouldn't allow to install anything on itself since my debugging wasn't enabled, though I am not sure about this one.
In any case I checked device manager and my ADB drivers were fine so I ran the three recovery commands in DOS anyway and they all executed without a hitch. I jumped for joy but my happiness was short lived since the phone booted back into recovery mode and now I am basically stuck up the creek without a paddle. I could really use some expert advice here just like the OP cause I really am not sure what went wrong and where. I would really like to fix this rather than flash and start the whole phone up from scratch if possible.
Regards,
LonerPrime
PS: Long time reader but this is my first post here so greetings to the xda community.
Click to expand...
Click to collapse
The way back home without buggy LG Mobile anything: Remove and replace batter, press home, volume-down and power keys simultaneously. Can be a bit tricky but will get you back in recovery. I assume you did that backup before playing. Restore it to get the phone back up.
Two ways to get your Kitkat:
1. Using the Version-8 install, do a clean install and be sure to choose an item in the various menu panes. Should work with this and then you need to reinstall and setup everything.
2. Take the "nightly" and install normally doing the requesite steps in the backup.
Thank you, but– Nvm fixed it.
@Dovidhalevi
Thank you for your amazing advice. I was able to get into recovery and restore from my nandroid backup. *Thank god I did that*
But kittkat ROM is still being a pain. I decided to read the logs of version 8 of the ROM a bit more closely and found this:
Upgrading from CM-10.2 or older / Fresh (First time) Installation: Now DON'T WIPE ANYTHING (Data/Factory reset, Wipe Cache partition, Dalvik Cache, Format System) everything have built in Aroma Installer. Simply flash through sdcard or adb sideload, Follow the Aroma Menu. Finish and Reboot device. Avoid Facebook, Whatsapp, Viber, Hangout apps while selecting apps to be flash, it may gives you fastboot mode. Done!!!
I decided to try my luck once more and disabled all those apps during the installation. But just before rebooting my phone lost root access again and asked if I wanted to fix it or not and then it froze again on LG logo afterwards. Another force restart and it went straight into fastboot mode. Had to do another restore to get my phone working on the older backup.
Now I know it isn't the CWD cause I am running that with my older Cynogen 7.2 OS and its rebooting without a hitch unlike kittkat which mysteriously loses root access...
I really apologize if I am being a bit noobish. Even though hardware/networking/linux[Red Hat] is like playing in my backyard, android itself is a new concept to me, hence I really appreciate all the help I can get on this to work.
MAJOR EDIT: I finally found the root of the problem and got my KitKat munching! The issue was, yep you definitely guessed it, human error... that human being me and if the original OP did everything like I did then I am guessing he made the same mistake.
What I did was, I didn't read the Aroma installer's text thoroughly enough during the installation process. At one point there comes a choice of partitions and the installer asks you to choose one of the following: *Please forgive me this is not the exact quote of the text but roughly along the same lines as memory serves*
A) Install if you are coming from a previous version of the ROM.
B) Install if you are coming from a different ROM all together.
Trust me, the way I put it makes me look like an idiot for not choosing the right choice but the actual text combined with reading carelessly on the fly ended up me botching up my initial attempts to install the new ROM. Point being you have to choose the second option and then install like usual. Following that method I wasn't faced with fastboot mode in the end and after 5 to 10 minutes of loading I was playing with the KittKat ROM. Once again I apologize for bothering you good folks and I am grateful for the guidance to the person above me.
Kind Regards,
LonerPrime
I'll try
LonerPrime said:
@Dovidhalevi
MAJOR EDIT: I finally found the root of the problem and got my KitKat munching! The issue was, yep you definitely guessed it, human error... that human being me and if the original OP did everything like I did then I am guessing he made the same mistake.
What I did was, I didn't read the Aroma installer's text thoroughly enough during the installation process. At one point there comes a choice of partitions and the installer asks you to choose one of the following: *Please forgive me this is not the exact quote of the text but roughly along the same lines as memory serves*
A) Install if you are coming from a previous version of the ROM.
B) Install if you are coming from a different ROM all together.
Trust me, the way I put it makes me look like an idiot for not choosing the right choice but the actual text combined with reading carelessly on the fly ended up me botching up my initial attempts to install the new ROM. Point being you have to choose the second option and then install like usual. Following that method I wasn't faced with fastboot mode in the end and after 5 to 10 minutes of loading I was playing with the KittKat ROM. Once again I apologize for bothering you good folks and I am grateful for the guidance to the person above me.
Kind Regards,
LonerPrime
Click to expand...
Click to collapse
Glad you fixed your phone!! I forgot to say what I did to "fix" it...
Read error... maybe???
I'll try as soon as I get home, with results!! Thanks!!!
I did that... =/
yes.. i was doing right. All the 6 times I tried...
And tried again now, just to be sure, and FASTBOOT again.
=/
jpesci said:
I flashed ClockworkMod Recovery 6.0.4.6 (Jan/14), than the ROM (v8), and the installation worked well.
Before the reboot, CWM says:
"root access possibly lost. Fix?
this can not be undone"...
Click to expand...
Click to collapse
All newer recoveries have this behavior. Because you are running a custom ROM and recovery, you should select "No" when prompted to disable recovery flashing.
Did you try the Key combos suggested by @Dovidhalevi to manually enter in to CWM?
As a worst case scenario, view this post to see how to restore your device to stock.
It's fixed, but no Kitkat...
shinobisoft said:
All newer recoveries have this behavior. Because you are running a custom ROM and recovery, you should select "No" when prompted to disable recovery flashing.
Did you try the Key combos suggested by @Dovidhalevi to manually enter in to CWM?
As a worst case scenario, view this post to see how to restore your device to stock.
Click to expand...
Click to collapse
Oh, sorry. Maybe bad explanation. I did get it fixed. All the "x" times, heheh =)
I just got in recovery by pressing home+vol up+power, and flashed back my older ROM. Now I'm trying CM 10 by Jenkins.
The problem isn't the "fastboot" message itself... but don't get Kitkat working =/
But thanks for the reply anyway!
kitkat by mukulsoni... ui stops with multiple popupd
M stuck.. i have successfully flashed kitkat by mukulsoni.. thanks. BUT UI DOES NOT START... it starts with so many popups... eg. Unfortunately voice dialer has stopped. Unfortunately bluetooth share has stopped. Unfortunately com.google.process.gapps stopped. Unfortunately com.android.systemui has stopped . Unfortunately clock has stopped. Unfortunately kitkat+ launcher stopped....
what to do. Should i get back through backup 4m recovery.. or u can help me wid kitkat .. feeling so sad..
amit2411 said:
M stuck.. i have successfully flashed kitkat by mukulsoni.. thanks. BUT UI DOES NOT START... it starts with so many popups... eg. Unfortunately voice dialer has stopped. Unfortunately bluetooth share has stopped. Unfortunately com.google.process.gapps stopped. Unfortunately com.android.systemui has stopped . Unfortunately clock has stopped. Unfortunately kitkat+ launcher stopped....
what to do. Should i get back through backup 4m recovery.. or u can help me wid kitkat .. feeling so sad..
Click to expand...
Click to collapse
Boot in to your recovery and try wiping your cache and dalvik cache.
still no working
I wish I could get these popups.
Is there something else to do??? I tried everything, everyway... Always get "fastboot mode started / udc_start()".
jpesci said:
I wish I could get these popups.
Is there something else to do??? I tried everything, everyway... Always get "fastboot mode started / udc_start()".
Click to expand...
Click to collapse
Maybe I can help... Are you flashing the same download every time? It's possible that your download managed to get corrupted. Try redownloading the ROM. I'd suggest redownloading the newest recovery also.
Now I'm going to list my ROM installation method for comparison. I personally have NEVER had an issue installing a ROM on any Optimus One variant. And I have 3 of them...
Boot device to your current recovery. CWM 6.0.45+ is compatible with CM10 - CM11 only. If you are currently running an older recovery, make a backup of your ROM with your current recovery first. Now if running an older recovery, Select "Install from zip" and install CWM 6.0.4.5+ or equivalent. Then go to "Advanced" and select "Reboot Recovery". We should now be in your new recovery. 1) Select "Wipe data/factory reset". This will wipe cache, data, .android_secure, and sd-ext.
2) Select "Advanced" then "Wipe Dalvik Cache". When done, return to recovery main menu.
3) Select "Mounts and storage". Choose "Format /system" and then confirm the action. Go back to main menu.
4) Select "Install from zip". Now we can install KitKat. Browse to and select your KitKat ROM and confirm installation.
5) If your device was old baseband ( originally running Android 2.2.2 or older ) then you will also need to flash the old baseband patch found here.
6) If you wish to flash a GApps package, that should be done now, or optionally after booting the device and letting it boot in to the ROM for the first time.
7) Go back to the main menu and select "Reboot device". If prompted to disable recovery flashing, select "NO". First boot will take 3 - 5 minutes.
shinobisoft said:
Maybe I can help... Are you flashing the same download every time? It's possible that your download managed to get corrupted. Try redownloading the ROM. I'd suggest redownloading the newest recovery also.
Now I'm going to list my ROM installation method for comparison. I personally have NEVER had an issue installing a ROM on any Optimus One variant. And I have 3 of them...
Boot device to your current recovery. CWM 6.0.45+ is compatible with CM10 - CM11 only. If you are currently running an older recovery, make a backup of your ROM with your current recovery first. Now if running an older recovery, Select "Install from zip" and install CWM 6.0.4.5+ or equivalent. Then go to "Advanced" and select "Reboot Recovery". We should now be in your new recovery. 1) Select "Wipe data/factory reset". This will wipe cache, data, .android_secure, and sd-ext.
2) Select "Advanced" then "Wipe Dalvik Cache". When done, return to recovery main menu.
3) Select "Mounts and storage". Choose "Format /system" and then confirm the action. Go back to main menu.
4) Select "Install from zip". Now we can install KitKat. Browse to and select your KitKat ROM and confirm installation.
5) If your device was old baseband ( originally running Android 2.2.2 or older ) then you will also need to flash the old baseband patch found here.
6) If you wish to flash a GApps package, that should be done now, or optionally after booting the device and letting it boot in to the ROM for the first time.
7) Go back to the main menu and select "Reboot device". If prompted to disable recovery flashing, select "NO". First boot will take 3 - 5 minutes.
Click to expand...
Click to collapse
Thanks for explanation!! But... still nothing.
I did EVERY SINGLE STEP like you said. Except for baseband, cause my phone was originally 2.3.3. But all new downloads...
After flashing, try to reboot... DAMN! "root access possibly lost..." YES/NO, gives me same problem. I read another thread about this erros, people said about SU. Can it be? I tried to flash another SU version, but CWM return an error too =/
jpesci said:
I wish I could get these popups.
Is there something else to do??? I tried everything, everyway... Always get "fastboot mode started / udc_start()".
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2559363 try this.
voltaire23 said:
http://forum.xda-developers.com/showthread.php?t=2559363 try this.
Click to expand...
Click to collapse
Ah, thanks man! But my problem isn't the "brick" itself, but the frustration of can't get kitkat working, hehe.
By the way, I think KDZ method dangerous, by many reports that you can find all through the web. In all 217897254179 times I tried Kitkat without success, I just rebooted in recovery mode (hold HOME+VOL UP+POWER button), and recovered the last CWM backup.
But thanks to the effort =)
jpesci said:
Ah, thanks man! But my problem isn't the "brick" itself, but the frustration of can't get kitkat working, hehe.
By the way, I think KDZ method dangerous, by many reports that you can find all through the web. In all 217897254179 times I tried Kitkat without success, I just rebooted in recovery mode (hold HOME+VOL UP+POWER button), and recovered the last CWM backup.
But thanks to the effort =)
Click to expand...
Click to collapse
I am considering the jenkins build from here: http://download.androidarmv6.org/_builds/
can anyone help with finding the smallest gapps that will fit?
Edit:No need
Hello all,
Sorry for my bad english.
I try to install new rom (fixed rom) on thl t11.
After i go in recovery mode i go in button "wipe all data" and after " yes - wipe data for all users"
Now when i turn on my mobile (power button) i get only black screen,nothing alse.
Please help me,is possible to fix this ?
Thanks a lot
Edit:
My phone is not rooted.also now i can't acces to my recovery .
did you fix that and if did how ?
By wiping your data you deleted the android system and data on your internal storage. But all your user data should still be there. However, since no operating system is installed, nothing can boot. That's why the screen stays black.
You will have to flash a ROM now. It must be suitable to your phone. You can either install the stock ROM oder a Custom ROM (which I would do since usually you have more options there). Download the zip-file to your sd-card and then flash it via the recovery, which you normally can enter by pressing certain buttons.
Which phone do you have? There a different ROMS out for most of the phones available. CyanogenMod for example is available for almost every phone. I would recommend getting that or the original firmware that was coming with your phone when you bought it.
boka003 said:
Hello all,
Sorry for my bad english.
I try to install new rom (fixed rom) on thl t11.
After i go in recovery mode i go in button "wipe all data" and after " yes - wipe data for all users"
Now when i turn on my mobile (power button) i get only black screen,nothing alse.
Please help me,is possible to fix this ?
Thanks a lot
Edit:
My phone is not rooted.also now i can't acces to my recovery .
Click to expand...
Click to collapse
You can take a look at this, though this is not for your phone you can try along the lines of the tutorial http://forum.xda-developers.com/showthread.php?t=2341320
If you cant even go to qpst download then i think you should hurry to your nearest service station
HIT THNX IF I HELPED
I (assumed) bricked my Moto G LTE today and just ordered another one. How it happened was that I factory reset my phone, but the setup stopped working after I finished it so I had no launcher. I naturally panicked and booted into recovery using ClockworkMod, but it didn't work. Eventually it got to the point where it was stuck at the Motorola "M" logo, so I continued to factory reset with ClockworkMod and installed a zip hoping a stock would fix it. It did not, since I misunderstood and now my phone is currently stuck at the warning bootloader screen (replaced by "Motorola powered by Android").
So I gave up and ordered the "Motorola Moto G - Universal 4G LTE - GSM Unlocked - 8GB (Black)" from Amazon.
To prevent something like that happening again what are some things I need to do to ensure I'll always have a safe recovery? I'm also overwhelmed by how many ways there are to root a Moto G LTE and could use some direction. I'm also confused on how I can find the appropriate stock ROM of 4.4.4 for my new XT1045.
Blkdrgn415 said:
I (assumed) bricked my Moto G LTE today and just ordered another one. How it happened was that I factory reset my phone, but the setup stopped working after I finished it so I had no launcher. I naturally panicked and booted into recovery using ClockworkMod, but it didn't work. Eventually it got to the point where it was stuck at the Motorola "M" logo, so I continued to factory reset with ClockworkMod and installed a zip hoping a stock would fix it. It did not, since I misunderstood and now my phone is currently stuck at the warning bootloader screen (replaced by "Motorola powered by Android").
So I gave up and ordered the "Motorola Moto G - Universal 4G LTE - GSM Unlocked - 8GB (Black)" from Amazon.
To prevent something like that happening again what are some things I need to do to ensure I'll always have a safe recovery? I'm also overwhelmed by how many ways there are to root a Moto G LTE and could use some direction. I'm also confused on how I can find the appropriate stock ROM of 4.4.4 for my new XT1045.
Click to expand...
Click to collapse
I am in no way an expert but here is my few cents :
0) make sure your bootloader is unlocked, see motorola website
1) Install TeamWin recovery latest version. For that just use adb to connect to your phone in debug mode and flash it, read up on that. Its easy process once you know it.
2) Hold vol down and power for a bit then release power, that goes into fastboot/bootloader, in which you press down then up to get into recovery.
3) erase everything from recovery, this should destroy your OS, to start at a clean slate.
4) make sure all your drivers are install on pc, for all modes that the phone can be in, so in the recovery now you should even see ur phone using adb devices
5) do a side load using adb of the rom your want to load, should take seconds
6) restart phone, rom should work, check it all out
7, if there is no root, then go back into recovery and install Super SU zip file, you can find.
Look at this guide: http://www.swedroid.se/forum/thread...nlock-recovery-root-guide-for-windows.106595/ it has all the tools you should need.
Oh, and don't panic, its very hard to really brick your phone.
Thanks for the help. Is it OK to use the guide even though it's intended for 4.4.2? What's the difference between CWM and TWRP, which one is better? In the scenario where I need to load the stock ROM because of corrupted recovery like before, how would I do that?
Blkdrgn415 said:
Thanks for the help. Is it OK to use the guide even though it's intended for 4.4.2? What's the difference between CWM and TWRP, which one is better? In the scenario where I need to load the stock ROM because of corrupted recovery like before, how would I do that?
Click to expand...
Click to collapse
For the Moto G hands down twrp
You can even flash IMG files after 2.8( if you even need to heh)
I just got my new phone today from Amazon. Apparently it's a XT1039 rather than my old XT1045. Is there a difference? I'm in the U.S. if that matters.
Edit: While following the guide @MuhammadA linked, I can't flash any recovery for some reason. When I try to flash them, my phone says "Mismatched partition size (recovery)" and when I try to launch "Recovery" it says "Boot up failed"
Edit: Found the problem. I don't know what it was, but I used a different version of CWM called "Unofficial CWM - 6.0.5.0 - peregrine" by Shabbypenguin and the OUDHS.
Edit again: The first thing I decided to do when I installed CWM was to backup my system, the first backup to my phone which went well and finished in a minute or so. When I started another one to my external SD card, it's stuck on "Generating MD5 checksums..." for about 20 minutes. Is it safe to force restart it via the power button?
Good day.
Thanks fore reading my post.
I had root on my phone like for 3 or 4 months. everything was great and all. I did not dwell in any ROM installing or playing with the firmware.
But I am not sure what I did that this happened.
When I restarted my phone, I experienced everything until the Logo faded to the rotating circle(loading). And it stays there. Always.
I did check on many sites and it seems to be a bootloop. I tried going into recovery, used every button combination possible(I have only 3 and also tried and for my phone and for others to work) and I can't.
It just continues normally and to the position I explained before.
I have a Vodafone Smart 4 Max and even though I want the fix for my phone, I know there are other users that also experience/experienced this problem on different phones.
Might there be a way to fix this?
Thank you for your time
EDIT:: I managed to enter in recovery mode and tried a hard reset of the android. The situation is still the same, the bootloop remaining
Go to bootloader and flash factory firmware with fastboot
I wish I could. I have no idea how to access the bootloader(as I see no function like that).
I only have 4 options:
1).Reboot system now
2). Wipe Data
3)Wipe Cache
4). Recovery from back-up on SD (which I am stupid and don't have)
andreinit said:
I wish I could. I have no idea how to access the bootloader(as I see no function like that).
I only have 4 options:
1).Reboot system now
2). Wipe Data
3)Wipe Cache
4). Recovery from back-up on SD (which I am stupid and don't have)
Click to expand...
Click to collapse
How did you get to recovery? Wasn't it through bootloader? I found the information you get into bootloader like this: (power off) press and hold "end call"+"power on"+"volume up". If it doesn't work try the same but with "volume down". I guess you tried it, but you never know (plus I've got a feeling you can flash new rom with option 4 you've got there)
minimale_ldz said:
How did you get to recovery? Wasn't it through bootloader? I found the information you get into bootloader like this: (power off) press and hold "end call"+"power on"+"volume up". If it doesn't work try the same but with "volume down". I guess you tried it, but you never know (plus I've got a feeling you can flash new rom with option 4 you've got there)
Click to expand...
Click to collapse
Hm, I know what you are saying. For me to enter in recovery mode though, I needed to do the following.
1). Fully shutdown the phone for like 30 seconds
2). Volume UP + power button until the first logo with android appears
3). Let the buttons go and I enter
The problem is that adb and fastboot don't see my device at all. I have been tweaking with the drivers for so long, thinking that may be the cause, but I have no results.
And I can use the backup thing to flash a new rom? It requests an update file though, not an image(a zip file)
I think this is about your phone, maybe it will point you in the right direction:
https://www.youtube.com/watch?v=bKHEZbj4NHo
They are figuring out firmware installation on a similair model here: http://forum.xda-developers.com/android/help/stock-rom-vodafone-888-t3002958