So i accidentally wiped the system using twrp. But i got it to work by using a usb flash drive n flashing a custom rom from there (paranoif android) And now ive been getting random reboots and crashes. I also flashed franco kernel. Also some system apps will not work properly, such as the calendar app. And i was thinking maybe thats because i wiped the system. Now i want to revert back to stock kikat without losing my root and unlocked bootloader. Im quite new to flashing roms and i find it easy using twrp. So how do i go about reverting back to stock, to see if those random crashes and reboots will go away?
xfranchize said:
So i accidentally wiped the system using twrp. But i got it to work by using a usb flash drive n flashing a custom rom from there (paranoif android) And now ive been getting random reboots and crashes. I also flashed franco kernel. Also some system apps will not work properly, such as the calendar app. And i was thinking maybe thats because i wiped the system. Now i want to revert back to stock kikat without losing my root and unlocked bootloader. Im quite new to flashing roms and i find it easy using twrp. So how do i go about reverting back to stock, to see if those random crashes and reboots will go away?
Click to expand...
Click to collapse
Try re-flashing another rom, as PA is a beta ROM, and thats where you may be having your crashed apps
xfranchize said:
So i accidentally wiped the system using twrp. But i got it to work by using a usb flash drive n flashing a custom rom from there (paranoif android) And now ive been getting random reboots and crashes. I also flashed franco kernel. Also some system apps will not work properly, such as the calendar app. And i was thinking maybe thats because i wiped the system. Now i want to revert back to stock kikat without losing my root and unlocked bootloader. Im quite new to flashing roms and i find it easy using twrp. So how do i go about reverting back to stock, to see if those random crashes and reboots will go away?
Click to expand...
Click to collapse
You can always flash the factory images here: http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701
You can flash any ROM and that should fix your issue
You will not lose your unlocked bootloader unless you flash the stock one which is in the factory images
Your bootloader will not relock unless you lock it yourself using fastboot. Flashing roms or factory images won't lock it by themselves.
And even if it somehow did, one fastboot command and you're unlocked again.
And as far as root goes....it takes 5 minutes to reroot.
So just flash whatever factory image you need and then custom recovery, and you're done. Maybe need to download superSU from play store after.
Sent from my N5, N7, Moto X, G Tab 3 or S2.....
justinisloco said:
Try re-flashing another rom, as PA is a beta ROM, and thats where you may be having your crashed apps
Click to expand...
Click to collapse
So i just flashed purity rom, and im still having the same issues, but the crashes and reboots are less yet their still there. Maybe reverting back to stock rom will do the trick?
xfranchize said:
So i just flashed purity rom, and im still having the same issues, but the crashes and reboots are less yet their still there. Maybe reverting back to stock rom will do the trick?
Click to expand...
Click to collapse
The crashes and reboots are because you didn't wipe data/factory reset and also didn't wipe dalvic/cache...
If you're keen on using a custom rom follow these steps:
1. Head over to recovery and wipe data/factory reset and wipe dalvic/cache
2. Flash rom.zip and gapps.zip
3. Reboot!
Initial boot can take upto 10 minutes sometimes so be patient...
If you want to go fully stock then follow this thread:
http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701
vin4yak said:
The crashes and reboots are because you didn't wipe data/factory reset and also didn't wipe dalvic/cache...
If you're keen on using a custom rom follow these steps:
1. Head over to recovery and wipe data/factory reset and wipe dalvic/cache
2. Flash rom.zip and gapps.zip
3. Reboot!
Initial boot can take upto 10 minutes sometimes so be patient...
If you want to go fully stock then follow this thread:
http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701
Click to expand...
Click to collapse
Sorry if i did not include this on the op, but everytime i were to flash a rom or gapps i would wipe data/factory and dalvic/cache, since i had those issues i even wipe internal memory just to see if the problems were there.
xfranchize said:
Sorry if i did not include this on the op, but everytime i were to flash a rom or gapps i would wipe data/factory and dalvic/cache, since i had those issues i even wipe internal memory just to see if the problems were there.
Click to expand...
Click to collapse
Maybe your flashing a bad version of GApps since the force closes are on google Calander?
Are you using a 4.4.2 GApps?
Im on cataclysm now, and i believe no gapps needed since their included in the zip. Have had about 3 reboots, i believe their because of playstore downloading an update or something, and one caused by either bluetooth or hello messaging app. But who knows. Just one more thing, by me accidentally wiping the system shouldnt be the cause of my random crashes and reboots?
Sent from my Nexus 5 using Tapatalk
xfranchize said:
Im on cataclysm now, and i believe no gapps needed since their included in the zip. Have had about 3 reboots, i believe their because of playstore downloading an update or something, and one caused by either bluetooth or hello messaging app. But who knows. Just one more thing, by me accidentally wiping the system shouldnt be the cause of my random crashes and reboots?
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Why don`t you backup your user apps and data with TB and start fresh by flashing the stock image, reroot and reflash a custom rom in recovery. This will eliminate all errors and reboots.
gee2012 said:
Why don`t you backup your user apps and data with TB and start fresh by flashing the stock image, reroot and reflash a custom rom in recovery. This will eliminate all errors and reboots.
Click to expand...
Click to collapse
Sorry but how do i do that? Im really new to this, i had someone else root and unlock my bootloader for me. How do i flash the stock image then root?
xfranchize said:
Sorry but how do i do that? Im really new to this, i had someone else root and unlock my bootloader for me. How do i flash the stock image then root?
Click to expand...
Click to collapse
Read this thread http://forum.xda-developers.com/goo...ide-nexus-5-how-to-unlock-bootloader-t2507905 well and all should be pretty easy.
gee2012 said:
Read this thread http://forum.xda-developers.com/goo...ide-nexus-5-how-to-unlock-bootloader-t2507905 well and all should be pretty easy.
Click to expand...
Click to collapse
Okay cool, do i just skip the bootloader part right?
Sent from my Nexus 5 using Tapatalk
xfranchize said:
Okay cool, do i just skip the bootloader part right?
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Yes, just flash the factory image (flash-all.batt) in fastboot, reboot and setup the phone. Flash a custom recovery and flash the superSU.zip (1.94 is the latest).
gee2012 said:
Yes, just flash the factory image (flash-all.batt) in fastboot, reboot and setup the phone. Flash a custom recovery and flash the superSU.zip (1.94 is the latest).
Click to expand...
Click to collapse
Okay ill give it a shot, thanks alot. Ill update here if im successful.
Sent from my Nexus 5 using Tapatalk
Related
I upgraded to CM10 from the original OS and I am using the latest version to root my phone, I am using TWRP. Anyway, Everything worked fine, I rooted the phone, I upgraded to CM10. I want to go back to the original OS. I downloaded [ROM][8/3] - Stock Rooted AT&T 2.20.502.7 - Android 4.0.4 - Odex or De-Odex, I got the ODEX version, I flashed it to my phone but its just hangs at the HTC One X Splash screen with the red lettering. What am I missing here? I can get back into recovery and I backed up my old ROM just in case.
How long are you letting it hang for? Try 2 more power downs and power ons. The first few times it took about 5 min to load.
mgutierrez87 said:
How long are you letting it hang for? Try 2 more power downs and power ons. The first few times it took about 5 min to load.
Click to expand...
Click to collapse
It just shuts off and turns back on again, it basically loops. Did I download the wrong file maybe? Is there a specific ROM I need other than the one I mentioned earlier?
Boot into recovery and wipe your cache and dalvik cache again
mgutierrez87 said:
Boot into recovery and wipe your cache and dalvik cache again
Click to expand...
Click to collapse
Factory reset, wipe system, flash ROM, wipe cache and delvik.
Any time you go from non sense to sense or vise versa you have to wipe the system and factory reset.
Sent from my One X using xda app-developers app
This was the ROM that worked when i did it.
http://forum.xda-developers.com/showthread.php?t=1872842
---------- Post added at 04:53 AM ---------- Previous post was at 04:46 AM ----------
Myrder said:
Factory reset, wipe system, flash ROM, wipe cache and delvik.
Any time you go from non sense to sense or vise versa you have to wipe the system and factory reset.
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
He mentioned in another thread that he did those steps. The only other thing I would try is to flash the boot.IMG from the ROM you want to use
I still want to keep my phone rooted. This wont kill the root right?
No the ROM posted above is stock rooted
But if you made a backup as you said in the first post why are you not just restoring the backup?
Sent from my Nocturnalized One XL using Forum Runner
Basically where I am right now. I downloaded the original OS, by following instructions, I have managed to delete my backed up rom of CM10 that i backed up earlier. I was able to FLASH the OS I wanted, I flashed the boot.img file using fastboot. I restarted the phone and now its just stuck on the HTC Quietly Brilliant screen with the red lettering at the bottom. It doesn't restart or anything, it just hangs there. What am I missing here guys? ):
I'm going to install cm10 right now them go back to stock rooted and see what's up with this
There's no issues going back and forth. You probably flashed a bad ROM
yea, your most likely just doing it wrong. you need to do a full wipe and flash boot.img
answer: oh yea cant flash the stock rom using twrp 2.3.1.0 you will need to flash twrp 2.2.2.0 then flash stock rom. that is actually most likely your problem.
What hboot are you on? If you separately flashed boot.img from CM10 via fastboot, you might need to again separately flash the boot.img from the stock ROM. Also remember that the procedure employed to root 2.20 is substantially different from the root procedure to root the previous build of stock. Not sure what software you rooted, or whether this would pose a problem, but it's a consideration.
Another option is to just restore to stock via RUU and re-unlock, re-root, if nothing else works. Getting stuck on HTC splash screen sounds like a boot.img issue. Good luck.
DvineLord said:
answer: oh yea cant flash the stock rom using twrp 2.3.1.0 you will need to flash twrp 2.2.2.0 then flash stock rom. that is actually most likely your problem.
Click to expand...
Click to collapse
Really? Why is that?
Just curious, I haven't heard this before. Is this a known issue with flashing the 2.20 stock ROM? I haven't seen any cases of ROMs (stock rooted or otherwise) being sensitive to version of TWRP. At least not the case of having to use an older version (keeping TWRP updated is usually the recommendation).
Of course, just because I haven't heard of it, doesn't mean it didn't happen!
Did you fastboot flash boot boot.img?
Sent from my HOX running Cyanogenmod 10
redpoint73 said:
Really? Why is that?
Just curious, I haven't heard this before. Is this a known issue with flashing the 2.20 stock ROM? I haven't seen any cases of ROMs (stock rooted or otherwise) being sensitive to version of TWRP. At least not the case of having to use an older version (keeping TWRP updated is usually the recommendation).
Of course, just because I haven't heard of it, doesn't mean it didn't happen!
Click to expand...
Click to collapse
im assuming the age of the stock rooted would have conflicts with the new twrp. i have had problems with roms not flashing with newest twrp. it is also a known problem since twrp 2.3.1.0 release.
Looking for some input on clean ROM on the TF300T,
This is my second time trying to install it and both times it was successful, however as soon as the boot image loads up it stays stuck loading... I did download the file again thinking it may have been corrupted.
It has been sitting there loading for 20 minutes now.
I am using cwm the latest version and I did not install a kernel still running stock
Any ideas on what could cause this?
chibra said:
Looking for some input on clean ROM on the TF300T,
This is my second time trying to install it and both times it was successful, however as soon as the boot image loads up it stays stuck loading... I did download the file again thinking it may have been corrupted.
It has been sitting there loading for 20 minutes now.
I am using cwm the latest version and I did not install a kernel still running stock
Any ideas on what could cause this?
Click to expand...
Click to collapse
CWM has issues on this unit. Many, many complaints. I use twrp. If you decide to use twrp be sure to choose JB and tf300t version.
Clean ROM is freaking amazing! Seriously just do it I love the mods I can make for it too! Can't wait till I get my volume long press seek mod done! Love this device!
Sent from my SGH-T999
"So I put my phone into airplane mode and threw it... worst transformer ever. -.-" -My friend
tobdaryl said:
CWM has issues on this unit. Many, many complaints. I use twrp. If you decide to use twrp be sure to choose JB and tf300t version.
Click to expand...
Click to collapse
I initially when i first rooted intalled Twrp however i was not able to flash anything at all with it, it would give me errors.... that is the only reason i went to cwm.... I was able to make backups and restores with but ROMs flashing would just fail
chibra said:
I initially when i first rooted intalled Twrp however i was not able to flash anything at all with it, it would give me errors.... that is the only reason i went to cwm.... I was able to make backups and restores with but ROMs flashing would just fail
Click to expand...
Click to collapse
OK. It was just a suggestion since the problem you are experiencing is usually cleared by using twrp.
oryhight sullivan
tobdaryl said:
OK. It was just a suggestion since the problem you are experiencing is usually cleared by using twrp.
Click to expand...
Click to collapse
i m going to give twrp another shot...
i installed http://tinyw.in/5foT
JB version for the TF300T
This is the Rom i m trying to install
http://forum.xda-developers.com/showthread.php?t=2049322
Kernel is still stock and i ve left it that way through the aroma installer
Everytime i flash and reboot i get a boot loop
chibra said:
i installed http://tinyw.in/5foT
JB version for the TF300T
This is the Rom i m trying to install
http://forum.xda-developers.com/showthread.php?t=2049322
Kernel is still stock and i ve left it that way through the aroma installer
Everytime i flash and reboot i get a boot loop
Click to expand...
Click to collapse
I'm sorry it is hard to tell since you have chosen an older twrp to install. The current is five versions later and was updated as the kernels were updated to account for changes. The rom you are flashing is based on 10.4.4.25.
chibra said:
i installed http://tinyw.in/5foT
JB version for the TF300T
This is the Rom i m trying to install
http://forum.xda-developers.com/showthread.php?t=2049322
Kernel is still stock and i ve left it that way through the aroma installer
Everytime i flash and reboot i get a boot loop
Click to expand...
Click to collapse
Use TWRP 2.4.1.0
You are using a very old version of TWRP that has bugs with AROMA installer. So that is most likely where your issues are.
What ROM are you ccoming from? What boot loader are you on.
Sounds to me like you need to upgrade your boot loader and possibly do a full wipe - make sure you are on latest TWRP first otherwise you could brick if you use an older recovery!
sbdags said:
What ROM are you ccoming from? What boot loader are you on.
Sounds to me like you need to upgrade your boot loader and possibly do a full wipe - make sure you are on latest TWRP first otherwise you could brick if you use an older recovery!
Click to expand...
Click to collapse
Wise words. Nobody likes to listen to me so im glad someone else suggested it!
elesbb said:
Use TWRP 2.4.1.0
You are using a very old version of TWRP that has bugs with AROMA installer. So that is most likely where your issues are.
Click to expand...
Click to collapse
Updated the TWRP to the version you mentioned still stuck in boot loop.
sbdags said:
What ROM are you ccoming from? What boot loader are you on.
Sounds to me like you need to upgrade your boot loader and possibly do a full wipe - make sure you are on latest TWRP first otherwise you could brick if you use an older recovery!
Click to expand...
Click to collapse
The only ROM i was able to flash that was fully functioning is cm10.1,
i have also flashed PA 2.9 but had some bugs i couldn't stand (screen rotation not working, extended desktop with no pie)
as for boot loader it says 1.00e by "US _Epad-10.4.2.20-20121228" A03
I just updated the TWRP as recommended on the other post (v2.4.1.0)
on every flash i wipe dalvik / Cache / Factory reset.
Before attempting to boot into Clean Rom i also followed the steps on screen saying to wipe cache and dalvik.
I m hoping PA releases a 3.0 for this device and/or i m able to get Clean rom running
chibra said:
The only ROM i was able to flash that was fully functioning is cm10.1,
i have also flashed PA 2.9 but had some bugs i couldn't stand (screen rotation not working, extended desktop with no pie)
as for boot loader it says 1.00e by "US _Epad-10.4.2.20-20121228" A03
I just updated the TWRP as recommended on the other post (v2.4.1.0)
on every flash i wipe dalvik / Cache / Factory reset.
Before attempting to boot into Clean Rom i also followed the steps on screen saying to wipe cache and dalvik.
I m hoping PA releases a 3.0 for this device and/or i m able to get Clean rom running
Click to expand...
Click to collapse
If you are coming from cm10.1 you will definitely need to do a full wipe as it is non stock. It does say this in the first post. You only do a dalvik and cache wipe when upgrading from the same ROM or in CROMI's case from stock.
Do a data wipe in recovery, make sure you have a titanium backup or equivalent if you want to restore apps.
Success!!!
It worked perfectly fine after i install the back up i did before i flashed my 1st costume rom,
I rooted made a back up at stock/rooted... It just would not install from a full wipe,
it install fine once i flashed that specific backup and dirty flashed then wiped dalvik and cache before booting.
So I'm trying to install custom ROM on my friend Nexus 5, should be a 2 minute job turns into 2 hours..
CWM is giving me a list of can't mount anything basically.
I tried fe-flashing the entire phone back to stock via fastboot, that went fine, flashed recovery again to CWM.. and can't mount anything again..
I need to be able to mount in order to install zip...
anybody can help??
now i got it to boot with purity ROM, telling me on startup with no google sign in... "
System UIDs Inconsistent. UIDs on the system are inconsistent, you need to wipe your data partition or your device will be unstable."
THE_KINGDOM said:
now i got it to boot with purity ROM, telling me on startup with no google sign in... "
System UIDs Inconsistent. UIDs on the system are inconsistent, you need to wipe your data partition or your device will be unstable."
Click to expand...
Click to collapse
yup, you will need to wipe and reflash.
still can't mount sdcard in recovery..
so i can't do anything.. I had to sideload the ROM..
so i've done a bat flash all, restore to stock..
I don't get why everytime i flash CWM custom recovery I can't load anything.. how the hell do I install purity from stock if I can't install CWM ?!
THE_KINGDOM said:
so i've done a bat flash all, restore to stock..
I don't get why everytime i flash CWM custom recovery I can't load anything.. how the hell do I install purity from stock if I can't install CWM ?!
Click to expand...
Click to collapse
try twrp recovery
but i've been using CWM forever on every nexus device without problems..
I though process is simple.
1. Unlock bootloader
2. Fastboot flash recovery recovery.img (cwm)
3. wipe & install custom ROM (Purity)
4. gapps
5. start phone..
what am I missing???
so I tried installing the previous version of CWM 6.0.4.4 and CWM problems seems to be resolved.. clearly they must have issued with the latest version.
Now im able to read /sdcard and hopfully install purity ROM, gapps etc.
but I'm still getting the system UID's inconsistent issue...
what a colossal waste of time...
ok phone back to stock at again with a batch restore all file.. factory files...
how the ****ing hell do I install a custom ROM?!?!?!? Like iv'e done this a million times before.. what am I missing??????
anybody?????
THE_KINGDOM said:
ok phone back to stock at again with a batch restore all file.. factory files...
how the ****ing hell do I install a custom ROM?!?!?!? Like iv'e done this a million times before.. what am I missing??????
Click to expand...
Click to collapse
Put a custom ROM.zip and gapps package on storage, flash in recovery, flash SuperSU if necessary?
THE_KINGDOM said:
anybody?????
Click to expand...
Click to collapse
No bumping within 24 hours is the forum rule. I also believe they should set a punctuation limit. Chill out
Sent from my Nexus 5 using Tapatalk
Lethargy said:
Put a custom ROM.zip and gapps package on storage, flash in recovery, flash SuperSU if necessary?
Click to expand...
Click to collapse
this is what ive been doing.. when phone boots it doesn't ask for google login credentials and goes straight to android is upgrading as if I did a dirty flash and then tell me i have a UID mismatch, and to wipe data partition..
i've now reinstalled this phone close to 6 times.. I cannot figure this out
THE_KINGDOM said:
what am I missing??????
Click to expand...
Click to collapse
cwm recovery SUCKS. but if you are unwilling to try other recoveries, oh well..
THE_KINGDOM said:
this is what ive been doing.. when phone boots it doesn't ask for google login credentials and goes straight to android is upgrading as if I did a dirty flash and then tell me i have a UID mismatch, and to wipe data partition..
i've now reinstalled this phone close to 6 times.. I cannot figure this out
Click to expand...
Click to collapse
Well somewhere you're not wiping properly. Flash the factory images again using the flash-all.bat included in the compressed file as it'll wipe everything, then go from there.
Stock CWM always has issues. It's based on an outdated version of Android so it doesn't always play well with KitKat. I would recommend either TWRP or Philz Touch CWM.
Lethargy said:
Well somewhere you're not wiping properly. Flash the factory images again using the flash-all.bat included in the compressed file as it'll wipe everything, then go from there.
Click to expand...
Click to collapse
flashed factory img aroudn 6 times now.. every single time i got back to put on CWM and then flash the rom i get a UID mismatch, bunch of force closes etc..
BirchBarlow said:
Stock CWM always has issues. It's based on an outdated version of Android so it doesn't always play well with KitKat. I would recommend either TWRP or Philz Touch CWM.
Click to expand...
Click to collapse
CWM is built from CM11 4.4.3 source code.. But yeah it has issues., lacks functionality and also is antiquated
Sent from my Nexus 5 using Tapatalk
THE_KINGDOM said:
flashed factory img aroudn 6 times now.. every single time i got back to put on CWM and then flash the rom i get a UID mismatch, bunch of force closes etc..
Click to expand...
Click to collapse
Don't know what to tell you, just try TWRP. I've had issues with CWM on every single device I've put a custom ROM onto (Xperia Arc S, HTC One M7, Galaxy S4, HTC One M8, Galaxy Note 3, Xperia Z, Nexus 5), and never had a single issue with TWRP on any.
gonna try Philz Touch CWM and if that doesn't work then TWRP
Hi ,guys .
So my problem is the first boot (on my p3110 )takes an eternity , whatever I'm trying to flash it wouldn't succesfully have the first boot .
I've tried omni,slimkat and CM but nothing works .
Dumb I was ,in my blind tries, I've deleted my backups and now the only place i can flash is my microSD card.
Help please , I'm really stuck . :crying:
TheHelplessGuy said:
Hi ,guys .
So my problem is the first boot (on my p3110 )takes an eternity , whatever I'm trying to flash it wouldn't succesfully have the first boot .
I've tried omni,slimkat and CM but nothing works .
Dumb I was ,in my blind tries, I've deleted my backups and now the only place i can flash is my microSD card.
Help please , I'm really stuck . :crying:
Click to expand...
Click to collapse
The first boot always takes longer as it is setting up, but no longer than ~5 minutes.
Anyway... If you've waited and it is boot looping, try these steps:
Make sure your recovery is up to date.
Wipe system, data, cache, and dalvik cache.
Flash ROM, gapps, and any addons
Wipe cache and dalvik
Reboot. After first reboot is complete and on setup screen, wait 5 minutes and reboot into recovery.
Wipe cache and dalvik again. Reboot
This reboot could also take ~5 minutes, but the others shouldn't as long as you don't wipe cache and dalvik.
You should see an "Android is Upgrading" screen. After this is done, complete setup and you should be good to go.
Sent from my SGH-T989
The same
jrc2 said:
The first boot always takes longer as it is setting up, but no longer than ~5 minutes.
Anyway... If you've waited and it is boot looping, try these steps:
Make sure your recovery is up to date.
Wipe system, data, cache, and dalvik cache.
Flash ROM, gapps, and any addons
Wipe cache and dalvik
Reboot. After first reboot is complete and on setup screen, wait 5 minutes and reboot into recovery.
Wipe cache and dalvik again. Reboot
This reboot could also take ~5 minutes, but the others shouldn't as long as you don't wipe cache and dalvik.
You should see an "Android is Upgrading" screen. After this is done, complete setup and you should be good to go.
Sent from my SGH-T989
Click to expand...
Click to collapse
The same loading image .(You know ,when you first boot something it appears the custom flash's logo) . what can i do ?
TheHelplessGuy said:
The same loading image .(You know ,when you first boot something it appears the custom flash's logo) . what can i do ?
Click to expand...
Click to collapse
How long have you tried waiting? Which room door you flash on which device?
Sent from my SGH-T989
jrc2 said:
How long have you tried waiting? Which room door you flash on which device?
Sent from my SGH-T989
Click to expand...
Click to collapse
I've waited more than usual 5-10 mins ,even 6 hours ,but nothing, ,I'm curently trying to flash slimkat 4.4.4 but i've tried omni ,CM all kitkat .
What is your advice ?
TheHelplessGuy said:
I've waited more than usual 5-10 mins ,even 6 hours ,but nothing, ,I'm curently trying to flash slimkat 4.4.4 but i've tried omni ,CM all kitkat .
What is your advice ?
Click to expand...
Click to collapse
What version of unroofed TouchWiz were you running before rooting and flashing?
Sent from my SGH-T989
jrc2 said:
What version of unroofed TouchWiz were you running before rooting and flashing?
Sent from my SGH-T989
Click to expand...
Click to collapse
The one with Android 4.1 my guess is Nature UX
TheHelplessGuy said:
The one with Android 4.1 my guess is Nature UX
Click to expand...
Click to collapse
Then idk what the problem is. You were on jelly bean already so that isn't a problem.
Sent from my SGH-T989
jrc2 said:
Then idk what the problem is. You were on jelly bean already so that isn't a problem.
Sent from my SGH-T989
Click to expand...
Click to collapse
What do you suggest ?
TheHelplessGuy said:
What do you suggest ?
Click to expand...
Click to collapse
I don't know, sadly. Maybe someone else will know and we'll both learn something.
Sent from my SGH-T989
Back to stock rom for now, prepare (charge until full).
Re-root, then reboot to recovery to try again flashing the rom.
Always format /system, /cache, /data/media first when installing different roms. Good luck
150208 said:
Back to stock rom for now, prepare (charge until full).
Re-root, then reboot to recovery to try again flashing the rom.
Always format /system, /cache, /data/media first when installing different roms. Good luck
Click to expand...
Click to collapse
I did exactly as you said but nothing happened .
1. It's a problem that i install zips from my external storage ?
2.Do you know where i can find a nandroid backup to download ?
3.What do you suggest for my issue ?
TheHelplessGuy said:
I did exactly as you said but nothing happened .
1. It's a problem that i install zips from my external storage ?
2.Do you know where i can find a nandroid backup to download ?
3.What do you suggest for my issue ?
Click to expand...
Click to collapse
Stock rom is working fine? Is root working on stock?
Did you get any errors while flashing costom roms?
I remember a folk here got a same problem as you, and i think it's not resolved yet..
Maybe you and him have a "special" devices.
Don't worry, it's not a problem with your ext-sd because i use it all the time. and if it was ext-sd problem, you'll get an error while flashing.
I suggest messages devs in developement section, maybe they can figure out what is wrong.
And of course i think it's not safe to restore others nandroid backup, so don't mind find it.
God speed, wish I can help you more :angel:
150208 said:
Stock rom is working fine? Is root working on stock?
Did you get any errors while flashing costom roms?
I remember a folk here got a same problem as you, and i think it's not resolved yet..
Maybe you and him have a "special" devices.
Don't worry, it's not a problem with your ext-sd because i use it all the time. and if it was ext-sd problem, you'll get an error while flashing.
I suggest messages devs in developement section, maybe they can figure out what is wrong.
And of course i think it's not safe to restore others nandroid backup, so don't mind find it.
God speed, wish I can help you more :angel:
Click to expand...
Click to collapse
Sadly my stock rom is gone.
So yesterday when I've rerooted whit your link I've received two errors :
- SOKP and when I've flash it something like poped up : E:Cannot write to sd card clockworkmod recovery etc.
- CM 11 :
Root Access Possibly Lost Fix?
THIS CANNOT BE UNDONE
1. YES fix root (/system/xbin/su)
2. NO do not fix
TheHelplessGuy said:
Sadly my stock rom is gone.
So yesterday when I've rerooted whit your link I've received two errors :
- SOKP and when I've flash it something like poped up : E:Cannot write to sd card clockworkmod recovery etc.
- CM 11 :
Root Access Possibly Lost Fix?
THIS CANNOT BE UNDONE
1. YES fix root (/system/xbin/su)
2. NO do not fix
Click to expand...
Click to collapse
Like I said earlier, you should have flashing stock rom first to remove root via odin/hemidall.. you can find it at sammobile,com
then re-root with link i gave earlier again via odin/hemidall, and format in recovery like i said earlier. no wonder you still fail..
you should have philz touch recovery instead cwm if you succeed.
150208 said:
Like I said earlier, you should have flashing stock rom first to remove root via odin/hemidall.. you can find it at sammobile,com
then re-root with link i gave earlier again via odin/hemidall, and format in recovery like i said earlier. no wonder you still fail..
you should have philz touch recovery instead cwm if you succeed.
Click to expand...
Click to collapse
re-rooted as you said still the same loading screen , you can give me a link to the part of the forum where I can speak with developers as you said few comments ago
Hi guys, can somebody help me? I received the stagefright update this morning and after downloading it and rebooting, the phone stopped working. It shows the logo animation for a few seconds then the screen goes black. It's a rooted and unlocked phone so i don't know if thats the cause. Also, i can access the recovery mode pressing power and down. Other than that nothing.
If you were rooted and updated ya..the rooting may be the reason
So as you can access the bootloader just flash the stock rom back and you will be done with it..
Jaydeep123 said:
So as you can access the bootloader just flash the stock rom back and you will be done with it..
Click to expand...
Click to collapse
I always forget how peacefull people with knowledge can be. Thanks mate, will do that.
But, just for curiosity: rooted phones tends to have problems after updates?
Yes It may get error or Somthing Else Thats Why I prefer if a update is avaiable flash back to stock and then proceed
Just a quick update. Flashed stock, worked fine. Thanks all.
Also, sorry for posting under general, i was so worried that i forgot to put this under HELP TROUBLESHOOTING.
Also, if I went there before i would find this thread here with the same problem and solution
http://forum.xda-developers.com/2015-moto-g/help/ota-caused-boot-loop-t3202322/
Thanks all again.
reinaldojr said:
Just a quick update. Flashed stock, worked fine. Thanks all.
Also, sorry for posting under general, i was so worried that i forgot to put this under HELP TROUBLESHOOTING.
Also, if I went there before i would find this thread here with the same problem and solution
http://forum.xda-developers.com/2015-moto-g/help/ota-caused-boot-loop-t3202322/
Thanks all again.
Click to expand...
Click to collapse
Mod will move or merge.
Sent from my MotoG3 using XDA Free mobile app
Technically, it should not install at all if it's been rooted. It's interesting that Moto has let this slip by.
In the future, if you have made a single change in the system partition...root, build.prop edit....anything...even custom recovery or kernel...you should reflash your current factory image, reboot, then flash your updated factory image. It's VERY IMPORTANT you reboot between flashing one factory image and the next, though. You may have more issues if you don't.
hp420 said:
Technically, it should not install at all if it's been rooted. It's interesting that Moto has let this slip by.
In the future, if you have made a single change in the system partition...root, build.prop edit....anything...even custom recovery or kernel...you should reflash your current factory image, reboot, then flash your updated factory image. It's VERY IMPORTANT you reboot between flashing one factory image and the next, though. You may have more issues if you don't.
Click to expand...
Click to collapse
Hello HP429; reflashin full factory image would effectively wipe phone
sunandoghosh said:
Hello HP429; reflashin full factory image would effectively wipe phone
Click to expand...
Click to collapse
Not if you only flash the system, boot and recovery image files
Recover the factory
I did the update and as mentioned previously on the thread stales after the logo. (bootloader is unlocked)
I can not find my oem backup. I tried twrp on recovery and was able to backup other stuff. Is there a way to generate the OEM so that i can flash or any other roms that are compatible with Moto G 3rd generation?
Try wiping cache, dalvik cache and data with TWRP. Don't use stock recovery for the data wipe or you will lose all the files stored on your internal partition, as well.