Related
Hey guys,
I unlocked the bootloader for my NS4G, installed CWM 5.8.0.2, and wiped cache, dalvik, battery stats, and boot, and then proceeded to install the v7 JB ROM by hp420... the problem is when I tried to install it, I get a status 7 and an abort. When I try to reboot my phone, it obviously stays in fastboot, because I don't have boot or a ROM, yet I can go back to recovery... can anyone tell me how to revert to a stock ROM or how to install the v7 ROM or another ROM so I can actually use my phone? Thank you! :good:
Edit: Mounted Storage to computer, tried to install a CM9 ROM to the phone, same problem.. seems like CWM is the problem, how would I fix this?
Here's a link to download the 4.0.4 factory image for your phone:
https://dl.google.com/dl/android/aosp/sojus-imm76d-factory-10660f4c.tgz
open it with 7Zip and flash the boot.img and system.img in there with fastboot.
You need to format system when you flash a custom ROM over a stock ROM. Well basically anytime you go from one different ROM to another like aokp - petes- miui and so on.
Its called a full wipe
RE: fastboot cmd line
albundy2010 said:
You need to format system when you flash a custom ROM over a stock ROM. Well basically anytime you go from one different ROM to another like aokp - petes- miui and so on.
Its called a full wipe
Click to expand...
Click to collapse
Okay, thanks guys, I have a problem. When I use fastboot command line, I type fastboot flash system (systempath) and when I hit enter a whole list of options pop up. what should I actually type after? I don't know what to do with the options.
Edit: after an hour of trying, it finally just gave in and it worked! Thank you guys so much!
Hey All,
I just got my One XL and I was so excited by the root on 2.20 that I decided to try and flash the custom rom of AOKP on onto it.
After rooting the phone, I did the following:
Flashed TWRP 2.3.1.0 - success
Then I went and saw the thread about the AOKP rom and followed instructions. On that thread, it states that you must flash the boot.img before doing this through fastboot if you are coming forom 2.20 firmware, so I did that. Then I saw that it said on the thread "do not complain about bootlooping if you flashed a custom KERNEL or did not manually flash the stock KERNEL via fastboot" As this was the first custom rom I had attemped with this phone I assumed that I had the stock KERNEL already installed, so I did not flash any kind of kernel.
As soon as I flashed the boot.img from AOKP, I saw that there was red writing on the bootloader about this being for development use only and I noticed that the phone would get past the bootloader to a black screen and then would reboot (boot loop).
I thought that the issue here was that I did not flash the kernel so I went and downloaded the rohan.kernel and flashed that. HOWEVER, I did not realize that I was meant to use recovery to do that and I pushed the boot.img from within the kernel via fastboot instead of using recovery to flash the new kernel (not sure if that matters all that much, but I think that from now on all rom work will be done in the day time after sleeping a little more).
After doing that I see no change in the performance of the phone (it is still boot looping). I am unsure of what to do now. I managed to push the KERNEL zip file and the ROM zip file to the phone via adb but when I try and install them via TWRP I am getting an error because the phone reports that it is unable to mount /sdcard/.
Can one of the far more knowlegable gurus here point me in the right direction? I have wiped the cache and davlik cache numerous times but that has not helped. Should I use TWRP to wipe the system? How can I get the phone back to a place where I can install the new rom?
Thanks!!
ackerchez said:
Hey All,
I just got my One XL and I was so excited by the root on 2.20 that I decided to try and flash the custom rom of AOKP on onto it.
After rooting the phone, I did the following:
Flashed TWRP 2.3.1.0 - success
Then I went and saw the thread about the AOKP rom and followed instructions. On that thread, it states that you must flash the boot.img before doing this through fastboot if you are coming forom 2.20 firmware, so I did that. Then I saw that it said on the thread "do not complain about bootlooping if you flashed a custom KERNEL or did not manually flash the stock KERNEL via fastboot" As this was the first custom rom I had attemped with this phone I assumed that I had the stock KERNEL already installed, so I did not flash any kind of kernel.
As soon as I flashed the boot.img from AOKP, I saw that there was red writing on the bootloader about this being for development use only and I noticed that the phone would get past the bootloader to a black screen and then would reboot (boot loop).
I thought that the issue here was that I did not flash the kernel so I went and downloaded the rohan.kernel and flashed that. HOWEVER, I did not realize that I was meant to use recovery to do that and I pushed the boot.img from within the kernel via fastboot instead of using recovery to flash the new kernel (not sure if that matters all that much, but I think that from now on all rom work will be done in the day time after sleeping a little more).
After doing that I see no change in the performance of the phone (it is still boot looping). I am unsure of what to do now. I managed to push the KERNEL zip file and the ROM zip file to the phone via adb but when I try and install them via TWRP I am getting an error because the phone reports that it is unable to mount /sdcard/.
Can one of the far more knowlegable gurus here point me in the right direction? I have wiped the cache and davlik cache numerous times but that has not helped. Should I use TWRP to wipe the system? How can I get the phone back to a place where I can install the new rom?
Thanks!!
Click to expand...
Click to collapse
First of all I think if you're on 2.2 fw I don't think you can flash kernels through TWRP - I think it has to be through fastboot, I don't know first hand as I'm still on an earlier fw version.
Secondly if you can get into recovery you can flash another rom.
Go to Mount > Mount USB Storage with your phone connected via USB, it should mount as a drive otherwise windows asks you to format format the drive if this happens chances are may have wiped it in bootloader with factory reset or clear storage in either case just format the drive.
You can then drag and drop another rom onto the phone and flash that - remember to extract the boot.img from the rom and flash via fastboot so it will boot.
Goodluck
thejosh86 said:
First of all I think if you're on 2.2 fw I don't think you can flash kernels through TWRP - I think it has to be through fastboot, I don't know first hand as I'm still on an earlier fw version.
Secondly if you can get into recovery you can flash another rom.
Go to Mount > Mount USB Storage with your phone connected via USB, it should mount as a drive otherwise windows asks you to format format the drive if this happens chances are may have wiped it in bootloader with factory reset or clear storage in either case just format the drive.
You can then drag and drop another rom onto the phone and flash that - remember to extract the boot.img from the rom and flash via fastboot so it will boot.
Goodluck
Click to expand...
Click to collapse
Hey!
Thanks a ton for your reply! I managed to get the phone to install a new ROM (AOKP V5) and it seems to boot up. Now when I get into that rom, I see all kinds of things crashing on me. The "Settings" app crashes, the keyboard crashes..any idea?
Did you wipe system, factory reset, davlik and cache from within TWRP before flashing?
Try that otherwise if you're still running into issues post in the thread.
You flashed the 11/10 JB gapps?
Sent from my Nexus 7 using xda premium
ok, i got the phone back up now and have been able to flash stuff properly.
I am working on an issue where after flashing a new rom (AOKP v4) and then a new kernel right after (rohan.kernel V2) the rom seems to hang on the loading splash screen. Has anyone else had this happen? Know how to solve it?
ackerchez said:
ok, i got the phone back up now and have been able to flash stuff properly.
I am working on an issue where after flashing a new rom (AOKP v4) and then a new kernel right after (rohan.kernel V2) the rom seems to hang on the loading splash screen. Has anyone else had this happen? Know how to solve it?
Click to expand...
Click to collapse
Did u wipe everything? (davlik, cache)
Sent from my HTC One XL using xda premium
hi peeps, i really have a problem right now with my one s, i upgraded my supersu to supersu pro, after that i restarted my phone and now my one s keeps booting into clockworkmod, even i select reboot system now still boot in to clockworkmod. help please dont know what to do...
anybody please help me...
guys,i reallyneed help, my phone dont turn off anymore when i press power button it keeps turning backon to CWM. i try to restore it with my backup viperones but same results still booting into CWM.:crying:
Relax. You aint getting help faster just because you constantly bump the thread. Usually it has quite the opposite effect.
Use twrp recovery instead of cwm, its much better than cwm. Try full wipe, or reinstall OS (system).
yfcpunishment said:
hi peeps, i really have a problem right now with my one s, i upgraded my supersu to supersu pro, after that i restarted my phone and now my one s keeps booting into clockworkmod, even i select reboot system now still boot in to clockworkmod. help please dont know what to do...
Click to expand...
Click to collapse
The phone bootlooping into CWM normally means your ROM is messed up. Also the One S isn't supported by CWM so you should really stop using it since it has bugs that haven't been and never will be fixed. Switch to TWRP.
If your lucky you can boot into CWM and wipe cache and the davlik cache and that will let you back into the rom.
If you're not lucky you need to flash the ROM again and fastboot flash the boot.img for the rom.
dc211 said:
The phone bootlooping into CWM normally means your ROM is messed up. Also the One S isn't supported by CWM so you should really stop using it since it has bugs that haven't been and never will be fixed. Switch to TWRP.
If your lucky you can boot into CWM and wipe cache and the davlik cache and that will let you back into the rom.
If you're not lucky you need to flash the ROM again and fastboot flash the boot.img for the rom.
Click to expand...
Click to collapse
thanks guys, i manage to get back to stock rom, relock bootloader.
thanks all
yfcpunishment said:
thanks guys, i manage to get back to stock rom, relock bootloader.
thanks all
Click to expand...
Click to collapse
Now stop using CWM as our phone isn't supported and it has lots of bugs.
Hi,
I was attempting to install a Lolipop ROM on my HTC Pico and in the process had to install TWRP(previously had CWM). Something happened, and now my exisiting KitKat ROM is in bootloops(CM) and the Recovery refuses to open and is simply stuck at the TWRP welcome image. Is there a way in which I can flash a recovery onto it without using the phone directly but by connecting it to the Laptop somehow? Or should I leave it for dead?(Note: it is not my daily driver)
Thanks and Cheers.
If i understand you flash TWRP recovery from lollipop thread right?
Bro that TWRP like aw3som3 recovery which change your partition table ,perhabs that makes your phone stuck.
Dont worry , reboot phone to fastboot mode and flash A normal TWRP recovery from our forum
And Next time you want to flash aw3som3 or lollipop recovery Remember to wipe system, cache, data,dalvik cache before flash
TANdev said:
Hi,
I was attempting to install a Lolipop ROM on my HTC Pico and in the process had to install TWRP(previously had CWM). Something happened, and now my exisiting KitKat ROM is in bootloops(CM) and the Recovery refuses to open and is simply stuck at the TWRP welcome image. Is there a way in which I can flash a recovery onto it without using the phone directly but by connecting it to the Laptop somehow? Or should I leave it for dead?(Note: it is not my daily driver)
Thanks and Cheers.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=3228623
Story of my life with the recovery issues. Check my above thread and you won't have to bury the Pico.
Sent from a Cool Phone stuck with crappy KingUser
My Moto G (XT1033) 1st Gen with stock lollipop has stuck in a boot loop.
I am still able to go in to recovery mode. Have tried clearing cache, but that didn't seem to work.
I don't have CWM installed it's pure android as stock have installed updates only through OTAs.
Have googled about it and many are stating that a factory reset will solve the issue. But I don't want to lose data in the phone.
Main reason for the boot loop could be App as I use beta versions of Facebook, Whatsapp and Nova launcher from apkmirror.
What can be done to recover data or just get this boot loop fixed?
P.S: My device is not rooted and does not have any CWM or TWRP recovery.
I have got exactly the same issue yesterday itself. It was working fine, even received a call after which it was placed on a table. Picked up a few moments later & it was switched off. After that, whenever i'm trying to turn it on, its stuck on the M Logo - Powered by Android i.e Bootloop.
My phone was full stock and totally untouched as well. There weren't any apps installed from sources apart from Play Store. I'm able to access the stock recovery and tried clearing the cache but no respite. Whenever i try to factory format that, it gives an error of e:/could't mount /cache/recovery/xxxxxxxx errors.
I had read the forums for similar issues and got to know from this thread : http://forum.xda-developers.com/moto-g/help/moto-g-bootup-problem-recovery-mode-t3122492. The issue is cent percent same apart from the fact that i can access stock recovery.
Maybe @ravibhat & @lost101 can help us in this. I'm not worried about getting the data but bringing the phone back to life is more important for me !! Please help.
BBThumbHealer said:
I have got exactly the same issue yesterday itself. It was working fine, even received a call after which it was placed on a table. Picked up a few moments later & it was switched off. After that, whenever i'm trying to turn it on, its stuck on the M Logo - Powered by Android i.e Bootloop.
My phone was full stock and totally untouched as well. There weren't any apps installed from sources apart from Play Store. I'm able to access the stock recovery and tried clearing the cache but no respite. Whenever i try to factory format that, it gives an error of e:/could't mount /cache/recovery/xxxxxxxx errors.
I had read the forums for similar issues and got to know from this thread : http://forum.xda-developers.com/moto-g/help/moto-g-bootup-problem-recovery-mode-t3122492. The issue is cent percent same apart from the fact that i can access stock recovery.
Maybe @ravibhat & @lost101 can help us in this. I'm not worried about getting the data but bringing the phone back to life is more important for me !! Please help.
Click to expand...
Click to collapse
oh okay mate. I have been googling for such issue but the mostly suggested method is reset that I haven't done (not to lose data). Will wait for a day if I get any solution otherwise will reset it.
Let me know what happened to your phone. Hope it gets fixed soon
okay so here's the update. Was successful to take backup as per http://forum.xda-developers.com/showthread.php?t=2426426
And made factory reset after that but now it is still getting stuck on bootloop with M logo and powered by android screen. :crying:
I gave my phone to the service center guys today for reflashing the firmware. They were unable to do and suggested a motherboard replacement for which i obviously refused as they asked for ~INR 8000 as charges. So will start experimenting with it now and hope so i'm able to bring back to life.
What i'm planning is:
1. Flash Custom Recovery.
2. Wipe entire phone.
3. Flash stock ROM.
Will keep updating if i'm able to manage anything
EDIT : Did everything mentioned above but the phone is having same fate as before @krunalshah68. It gets stuck on the M Logo :crying: The internal memory although is being shown as 5xxx MB in TWRP unlike 0 Mb earlier.
Unlock Bootloader (if not already done) and flash twrp - mfastboot flash recovery twrp.img
Alternatively you can boot into twrp without flashing: mfastboot boot twrp.img
Download twrp: http://forum.xda-developers.com/moto-g/development/recovery-twrp-2-8-2-0-touch-recovery-t2980621
Then via PC, do the following wipe: (requires working ADB setup - google it)
http://forum.xda-developers.com/showpost.php?p=65431978&postcount=22
BBThumbHealer said:
I gave my phone to the service center guys today for reflashing the firmware. They were unable to do and suggested a motherboard replacement for which i obviously refused as they asked for ~INR 8000 as charges. So will start experimenting with it now and hope so i'm able to bring back to life.
What i'm planning is:
1. Flash Custom Recovery.
2. Wipe entire phone.
3. Flash stock ROM.
Will keep updating if i'm able to manage anything
EDIT : Did everything mentioned above but the phone is having same fate as before @krunalshah68. It gets stuck on the M Logo :crying: The internal memory although is being shown as 5xxx MB in TWRP unlike 0 Mb earlier.
Click to expand...
Click to collapse
Damn mate ! I am going to follow same steps.
1) Unlock bootloader
2) Flash custom recovery if needed
3) Flash Custom rom
btw did you had unlocked the bootloader? @BBThumbHealer
lost101 said:
Unlock Bootloader (if not already done) and flash twrp - mfastboot flash recovery twrp.img
Alternatively you can boot into twrp without flashing: mfastboot boot twrp.img
Download twrp: http://forum.xda-developers.com/moto-g/development/recovery-twrp-2-8-2-0-touch-recovery-t2980621
Then via PC, do the following wipe: (requires working ADB setup - google it)
http://forum.xda-developers.com/showpost.php?p=65431978&postcount=22
Click to expand...
Click to collapse
Thank you for you reply mate. :good:
I have somehow managed to backup data by script. but the problem is now even after resetting it is still stuck into bootloop.
But I am a bit confused here in steps.
1) Unlock bootloader
2) Flash custom recovery like TWRP and clear dalvik cache
3) and then flash any custom rom
correct me if I am wrong. I am going to follow these steps. @lost101
Phone started! yeeey!
So heres the update bro @BBThumbHealer.
Unlocked bootloader.
Flashed TWRP.
Cleared cache/dalvik cache/data.
Flashed http://forum.xda-developers.com/moto-g/development/nx-nexus-experience-rom-10-0-3-ambient-t3268555/
And device is working smooth as silk now and that too with Marshmallow !:fingers-crossed:
Let me know your status bro. Hope I could help you in some way
@krunalshah68 : Great to know bro that ur phone is as good as new now .. Many congratulations
As far as mine is concerned, did the following :
1. Unlocked bootloader
2. Flashed TWRP Recovery v3.0.2
3. Using mfastboot, flashed stock 5.0.2 and the phone booted up successfully finally !!
But now here's the catch, the phone once flashed up with a rom boots up fine for a single time only. Within that time frame, every damn thing works fine. Able to browse the net, configure apps & settings , blah blah etc etc ... every single thing. But as soon as i restart the phone, the rom fails to startup. It gets stuck on the boot loop.
Initially i thought the rom might have been corrupt, but then i tried the following roms:
1. Stock 5.1 Optimized as posted by @lost101
2. crDroid CM 13 6.0.1
And again the same fate was met.
And yes, i've been installing the above roms by flashing the zips in twrp. After every flash, cleared dalvik, cache & data.
Maybe the fellow members @lost101 @ravibhat can give some insight what's happening ! :crying :
Hello guys, My phone is stuck on bootloop
I have already rooted device and now it is stuck on bootloop even the Recovery isn't opening. I know I would have to reset the phone with mfastboot but I want my internal storage to be backed up before doing all this Is there anyway to do so? Anyone here can help me out?
@sahil_arora05 : if you are able to access the bootloader mode, with the help of mfastboot, flash the latest version of twrp for moto g (mfastboot flash recovery recoveryfilename.img). After that, connect an otg disk to ur handset, boot into twrp and you'll be able to see all your files in the internal storage using the inbuilt file explorer for twrp. With that you can copy all ur data from the handset to the otg drive.
BBThumbHealer said:
@sahil_arora05 : if you are able to access the bootloader mode, with the help of mfastboot, flash the latest version of twrp for moto g (mfastboot flash recovery recoveryfilename.img). After that, connect an otg disk to ur handset, boot into twrp and you'll be able to see all your files in the internal storage using the inbuilt file explorer for twrp. With that you can copy all ur data from the handset to the otg drive.
Click to expand...
Click to collapse
I tried to do this stuff with fastboot but nothing happened. Phone is stuck at TWRP logo only.
by the way mfastboot or fastboot is same or not?
sahil_arora05 said:
I tried to do this stuff with fastboot but nothing happened. Phone is stuck at TWRP logo only.
by the way mfastboot or fastboot is same or not?
Click to expand...
Click to collapse
@sahil_arora05 Use mfastboot. It's been specifically designed for Moto devices as the regular fastboot is reportedly having some issues with Moto mobiles (read this on some XDA post itself)
@krunalshah68 : waiting for your suggestions to get my device up & running like urs
BBThumbHealer said:
@sahil_arora05 Use mfastboot. It's been specifically designed for Moto devices as the regular fastboot is reportedly having some issues with Moto mobiles (read this on some XDA post itself)
@krunalshah68 : waiting for your suggestions to get my device up & running like urs
Click to expand...
Click to collapse
Ok going to try that. Is there anyone who can provide me a link to download STOCK recovery for moto G xt1033. Can't find that.
@sahil_arora05 : http://forum.xda-developers.com/showthread.php?t=2649763 : Select XT1033 and from there u can choose the stock recovery for Asian model.
BBThumbHealer said:
@sahil_arora05 : http://forum.xda-developers.com/showthread.php?t=2649763 : Select XT1033 and from there u can choose the stock recovery for Asian model.
Click to expand...
Click to collapse
tThanks again buddy.
BBThumbHealer said:
Maybe the fellow members @lost101 @ravibhat can give some insight what's happening ! :crying :
Click to expand...
Click to collapse
I already gave you the solution in post #6. Stop ignoring what I say and do it.
BBThumbHealer said:
@krunalshah68 : Great to know bro that ur phone is as good as new now .. Many congratulations
As far as mine is concerned, did the following :
1. Unlocked bootloader
2. Flashed TWRP Recovery v3.0.2
3. Using mfastboot, flashed stock 5.0.2 and the phone booted up successfully finally !!
But now here's the catch, the phone once flashed up with a rom boots up fine for a single time only. Within that time frame, every damn thing works fine. Able to browse the net, configure apps & settings , blah blah etc etc ... every single thing. But as soon as i restart the phone, the rom fails to startup. It gets stuck on the boot loop.
Initially i thought the rom might have been corrupt, but then i tried the following roms:
1. Stock 5.1 Optimized as posted by @lost101
2. crDroid CM 13 6.0.1
And again the same fate was met.
And yes, i've been installing the above roms by flashing the zips in twrp. After every flash, cleared dalvik, cache & data.
Maybe the fellow members @lost101 @ravibhat can give some insight what's happening ! :crying :
Click to expand...
Click to collapse
Thank you @BBThumbHealer.
Damn man that's the basic steps that you are following and that too pretty neat and right. Even though it is causing issues then there might be some other hardware bug may be ! Hope your phone gets started soon!
Hi Guys,
phone : Moto G (XT1033), Falcon
- stuck in bootloop
- able to go to recovery
- unable to flash custom recovery such as twrp or cwm
- as suggested,
1. Unlocked the bootloader successfully, can see code status = 3 in recovery mode
mfastboot oem unlock <CODE>2. Unable to flash twrp. It writes successfully but shows stock recovery only
mfastboot flash recovery twrp-3.0.2-0-falcon.img3. so tried booting twrp using with success
mfastboot boot twrp-3.0.2-0-falcon.img4. cleaned cache, dalvik etc.
5 using twrp, used ADB which enables MTP which let me transfer Android6.0.1_NX_R10.3.3_MotoG2013.zip to internal memory
6 Using twrp to flash ROM - Android6.0.1_NX_R10.3.3_MotoG2013.zip
It seems it started installing but its been more than one hour and it seems its still doing something.
It has stuck at - "Patching system image unconditionally..."
is this normal? Did I miss anything?
Appreciate help in advance. thank you for your time...
Best Regards,
Jignesh