OK so I just installed CM10 and I have it "working" but It is not something I want permanently. Every time I go to put my original system.img any where near the root filesystem it freezes then goes to the boot animation. I cant get my my img on the device , I think its a trap to keep me on CM10 :laugh: (Im JK). But can someone PLEASE help me.
Everything is a fresh install of CM10, nothing touched
Thanks
how are you trying to flash back to stock? u need to do it in fastboot. stock boot, system, userdata. if the stock rom doesn't see everything else stock it won't boot.
Sent from my Nexus 7 using xda premium
Related
Hello guys,
I wonder if somebody can help me. I bought a new Nexus 7 few days ago. As usual like with any other new device, I unlocked and rooted the device with the nexus root toolkit. After that I flashed via recovery a custom ROM. Everything worked fine, but after few hours, I wanted to try another rom, so I rebooted into recovery and the mistake I made was, that i wiped the inernal storage instead of cache. I was not able to get the custom ROM to the internal storage and the ROM was deleted, so the only option to bring the tablet to work was flashing original ROM via the toolkit or fastboot. Now I'm running on the original ROM, because when I try to flash any custom ROM, the insallation finishes fine, the tablet restarts and it gets stuck on the bootanimation.
I already tried 3 different ROMs, but the problem still persists and I have always to flash back the original ROM to get the tablet working.
Does anybody know, how to solve this problem? I really want to have a custom ROM running.
I appriciate your help!
Thanks for any ideas!
Sent from my Nexus 7 using xda app-developers app
Re download the rom of your choice to the tablet. Goo manager is my preferred method Keeps from adb push to the device...
Then Boot into recovery.. TWRP is what i use..
Wipe dalvik cache and system...
you can also in twrp .. copy your rom to usb/sd media boot into twrp with a connected usb media.. do full wipe and flash the rom from usb storage.. Great for those who have issues with internal storage. This way you can wipe it as well...
Good Luck....
Hello Erica, of course iI didit this way. As I wrote, I tried 3 different ROMs and the problem is always the same. I stucks on bootanimation.
First time I flashed custom ROM without any problems, but after flashing original ROM via the root toolkit, I am not able to get any custom ROM running.
Sent from my Nexus 7 using xda app-developers app
Wipe caches and if it gets s stuck at the boot screen sometimes you just have to turn it off for a bit and try turning it on in a couple minutes
sunman277 said:
Wipe caches and if it gets s stuck at the boot screen sometimes you just have to turn it off for a bit and try turning it on in a couple minutes
Click to expand...
Click to collapse
did you flash a custom kernel? you are not suppose to before the first boot
Sunmann, I will try.
billchen, In the custom ROMs I tried was always a custom kernel. So it flashed kernel as well.
Sent from my Nexus 7 using xda app-developers app
Hello guys, I'm back again. It still doesn't work flashing any of the custom ROMs. Does anyone, please, have any other idea, what could cause the problem?
Thanks a lot!
Hello i downloaded the stock recovery for my nexus 10 because i wanted to go back to stock for the sooon to come 4.3 android update. I tried using the command to flash but it didnt work so i downloaded flashify and used that to flash. It said it completeded and told me to either flash more stuff or reboot. I rebooted and it went to a dead android with a warning in the chest area :crying: I tried holding power to shut off tablet for 30 seconds but it turns right back on into dead android image. I can get into fastboot if i hold volume up while it turns on but now the only choice is start and it says downloading do not turn off target. If you know whats wrong please help me. Is there anyway to fix this without flashing stock?
abdel12345 said:
Hello i downloaded the stock recovery for my nexus 10 because i wanted to go back to stock for the sooon to come 4.3 android update. I tried using the command to flash but it didnt work so i downloaded flashify and used that to flash. It said it completeded and told me to either flash more stuff or reboot. I rebooted and it went to a dead android with a warning in the chest area :crying: I tried holding power to shut off tablet for 30 seconds but it turns right back on into dead android image. I can get into fastboot if i hold volume up while it turns on but now the only choice is start and it says downloading do not turn off target. If you know whats wrong please help me. Is there anyway to fix this without flashing stock?
Click to expand...
Click to collapse
There might be. Using onboard flashing tools is not a good idea since it doesn't seem like you know what you're doing (no offense) with the low-level tools. You should be able to dirty flash your ROM from stock (although you do realize that the stock recovery will be useless to you if you're trying to update to 4.3 over a custom ROM, right? Or if you're on a stock rooted ROM that flashing will unroot you?) to leave your /data partition intact.
When you said "the command to flash", I assume you're referring to "fastboot flash recovery <path-to-recovery.img>". You will need to rerun that, probably flashing a custom recovery. If your system boots correctly after this, then you can go ahead and reflash your stock recovery (and the problem would likely have been a messed up partition). If not, then you can try to boot into the custom recovery to do a dirty flash of your ROM (i.e. a flash without using factory wipe). If that doesn't work either, you can open up a .zip of your ROM and use "fastboot flash system <path-to-system.img>", pointing to the system image in your ROM. That should generally get you at least bootable again.
Rirere said:
There might be. Using onboard flashing tools is not a good idea since it doesn't seem like you know what you're doing (no offense) with the low-level tools. You should be able to dirty flash your ROM from stock (although you do realize that the stock recovery will be useless to you if you're trying to update to 4.3 over a custom ROM, right? Or if you're on a stock rooted ROM that flashing will unroot you?) to leave your /data partition intact.
When you said "the command to flash", I assume you're referring to "fastboot flash recovery <path-to-recovery.img>". You will need to rerun that, probably flashing a custom recovery. If your system boots correctly after this, then you can go ahead and reflash your stock recovery (and the problem would likely have been a messed up partition). If not, then you can try to boot into the custom recovery to do a dirty flash of your ROM (i.e. a flash without using factory wipe). If that doesn't work either, you can open up a .zip of your ROM and use "fastboot flash system <path-to-system.img>", pointing to the system image in your ROM. That should generally get you at least bootable again.
Click to expand...
Click to collapse
Yes I don't really know what I'm doing. I'm on stock. Anyways I'll try what you said about flashing custom recovery again and thanks for the reply. I just really don't want to lose all my data or else I wouldve flashed stock by now
Sent from my Xperia Play (r800x)
abdel12345 said:
Yes I don't really know what I'm doing. I'm on stock. Anyways I'll try what you said about flashing custom recovery again and thanks for the reply. I just really don't want to lose all my data or else I wouldve flashed stock by now
Sent from my Xperia Play (r800x)
Click to expand...
Click to collapse
Not a problem. These tools are really useful when they work, but it's definitely better to know how to do it when things go wrong (and they almost always will at least once). Just keep a level head about it and don't panic. Fastest way to lose data, that.
ok thanks. Well i got it booting and i decided im just going to back up everything with titanium backup and reflash stock with wugs toolkit
OK I'm a big idiot I did all this for no reason. I flashed back to stock with wugsroot kit and apparently it wiped all SD data so I lost all my titanium backups as well as pictures and apps and everything. Damn I'm stupid. Well I guess now that I lost all my data I might as well flash a custom ROM :banghead::banghead:
Sent from my Xperia Play (r800x)
This isn't my very first time with flashing/rooting/etc. but I'm not that adept with it.
Got my S4 2 days ago but managed to get time today to work on it. I rooted successfully and everything was running perfect. I flashed over the newest Beanstalk ROM w/ gapps and it ran fine the first time it ran.
I can't get passed the Samsung Galaxy S4 boot logo every time I try to reboot the phone though...
If I wipe the cache/dalvik and reflash it still doesn't boot passed logo.
If I wipe the cache/dalvik and then wipe data (including the internal SD card, completely wiping it clean), flashing the ROM will work the first time it runs; once I reboot or just power it off then power it back on, stuck at Galaxy S4 logo... I let the ROM run first time through, input only what is needed to get to the home screen (google account/wifi setup/phone name/etc.), then I've tried rebooting it, shutting it down and powering it back up, letting everything update and waiting half an hour and restarting it... all have the same result, stuck at boot logo
I'm using TWRP, I have a recovery for stock but I don't want to use stock.
If anyone can help me out I'd appreciate it.
Try flashing a different compatible kernel.
ObrienDave said:
Try flashing a different compatible kernel.
Click to expand...
Click to collapse
This is EXACTLY what I was about to try... I'm literally reflashing the ROM fresh right now, going to put the kernel on the SD card, then reboot into recovery and wiping cache then flashing the kernel.
Will using a recovery that was made on a different kernel have any effect if I decide to use the recovery? I've heard bad things about flashing the wrong kernel (even though I know the one I'm about to use is the correct one) and really screwing stuff up if not done properly. I just want to make sure I don't screw anything up permanently.
Thanks.
Spazzzin said:
This is EXACTLY what I was about to try... I'm literally reflashing the ROM fresh right now, going to put the kernel on the SD card, then reboot into recovery and wiping cache then flashing the kernel.
Will using a recovery that was made on a different kernel have any effect if I decide to use the recovery? I've heard bad things about flashing the wrong kernel (even though I know the one I'm about to use is the correct one) and really screwing stuff up if not done properly. I just want to make sure I don't screw anything up permanently.
Thanks.
Click to expand...
Click to collapse
Use twrp 2.5.0.2 because if your using 2.6 its bringing problems. Also report this to their thread for better help
Sent from my SPH-L720 using xda app-developers app
Since there are no recovery categories according to this page,
http://forum.xda-developers.com/showthread.php?t=2303917
I don't see where it would matter. No guarantees though.
I do know it is ESSENTIAL to match the type (TW or AOSP) ROM and kernel to avoid major problems.
I also recommend TWRP 2.5.0.2
D/L TWRP from here:
http://techerrata.com/browse/twrp2/jfltespr
ObrienDave said:
Since there are no recovery categories according to this page,
http://forum.xda-developers.com/showthread.php?t=2303917
I don't see where it would matter. No guarantees though.
I do know it is ESSENTIAL to match the type (TW or AOSP) ROM and kernel to avoid major problems.
I also recommend TWRP 2.5.0.2
D/L TWRP from here:
http://techerrata.com/browse/twrp2/jfltespr
Click to expand...
Click to collapse
How do you go about installing TWRP? I used Goomanager and installed it from there when I was following the rooting guide
Spazzzin said:
How do you go about installing TWRP? I used Goomanager and installed it from there when I was following the rooting guide
Click to expand...
Click to collapse
Flashing a different kernel didn't do anything, I still keep getting stuck at the boot logo :/
Spazzzin said:
How do you go about installing TWRP? I used Goomanager and installed it from there when I was following the rooting guide
Click to expand...
Click to collapse
Just flash it by odin by the link provided above. Make sure to use the tar file v 2.5.0.2
Sent from my SPH-L720 using xda app-developers app
---------- Post added at 09:22 PM ---------- Previous post was at 09:19 PM ----------
Spazzzin said:
Flashing a different kernel didn't do anything, I still keep getting stuck at the boot logo :/
Click to expand...
Click to collapse
By the way can you provide the steps and which files you flashing. Also redownload everything could be a bad download. Make sure to download them in computer and transfer them to your sd card
Sent from my SPH-L720 using xda app-developers app
I did a fresh install of the LiquidSmooth ROM and it's not hanging at boot logo whenever I reboot, and everything is working well. I suppose I'll stick with this for a while.
For my steps trying Beanstalk:
Boot into recovery (TWRP 2.6.0.0)
Factory reset;wipe cache/dalvik
Format Data
Factory reset;wipe cache/dalvik
Install ROM + Gapps
Wipe cache/dalvik
Reboot
I then tried doing that exact process, after letting it boot once I rebooted into recovery and flashed KT Kernel and wiped then rebooted and it hung at boot logo.
I did it again but I installed ROM + Gapps + Kernel then wiped then rebooted and it still hung at boot logo.
I'll download and prepare a new install of Beanstalk and give it another try tomorrow. I'll make sure to backup Liquid in case I want to switch back.
Thanks again for the help!
Glad it's working out for you.
If I may ask here; how do I know if a certain kernel is compatible with a ROM? I know to match the version (4.2, 4.3. etc,) and base (AOSP/ TW) but is there anything else specific that I need to watch out for that could cause problems with flashing a kernel on a ROM?
Spazzzin said:
If I may ask here; how do I know if a certain kernel is compatible with a ROM? I know to match the version (4.2, 4.3. etc,) and base (AOSP/ TW) but is there anything else specific that I need to watch out for that could cause problems with flashing a kernel on a ROM?
Click to expand...
Click to collapse
Not really unless the rom dev for some reason doesn't recommend using a certain one. Kernels will act differently for everyone even on the same device with the same rom. Just need to flash them and find out which one works the best for you (battery life, overheating, smoothness, etc).
Always have a backup handy just in case something doesn't work right.
I've been successfully using the new 4.3 ROM on my a500. After flashing the latest, it worked beautifully until I shut it down. Upon rebooting, it stays in a boot loop. I am able to get into TWRP 2.4.4, but cannot restore my backup or flash any ROM.
It looks like I accidentally deleted the flexrom folder from the tablet. I have not previously been successful flashing via USB. How can I recover my tablet?
Any ideas would be appreciated.
LPMatt said:
I've been successfully using the new 4.3 ROM on my a500. After flashing the latest, it worked beautifully until I shut it down. Upon rebooting, it stays in a boot loop. I am able to get into TWRP 2.4.4, but cannot restore my backup or flash any ROM.
It looks like I accidentally deleted the flexrom folder from the tablet. I have not previously been successful flashing via USB. How can I recover my tablet?
Any ideas would be appreciated.
Click to expand...
Click to collapse
seems a bit strange u cannot do anything from recovery...what happens when u do?
Do u still have Skrilax_CZ bootloader?
Think I'd reflash the v8 bootloader/recovery pkge and go from there
Sent from my GT-I9300 using Tapatalk 4 Beta
Managed to get apx working and flashed bootloader v9. Got to twrp 2.4.4 but could not flash a rom. Flashed an apx bundle with b/l v8 and Thors 1.7 cwm. Flashed a rom with aroma and it looked successful, but would not boot past the wifi screen. Says process failed.
The flexrom issue seems to be solved, but I had to repartition. Could that be it? Don't know what the proper partition sizes should be.
Sent From Here
LPMatt said:
... but I had to repartition. Could that be it? Don't know what the proper partition sizes should be.
Sent From Here
Click to expand...
Click to collapse
U dont need to know the partition sizes??
Just run babsector. rar it does it for u and will flash bootloader/recovery as well...its in the root guide in my sig
Which rom are u flashing?
Make sure u do a full wipe.
Sent from my GT-I9300 using Tapatalk 4
That did it! I'm back on 4.3 with the latest cwm for the a500. Wish I could use TWRP 2.6.1, but I still can't get that one to load. What I have is working great, though. Thanks for your help!
Sent From Here
That's awesome m8, sorry cant help with TWRP but glad you got yaself fixed up!!
Sent from my GT-I9300 using Tapatalk 4
Hi guys, need some help here. I'm sure this has been asked before but i just couldn't find any
Installed slimkat 20140406-0134 rom (cm11) last night and it's basically working. But I'm still not feeling comfortable using it as there's still bugs around. So thought of going back to cm7.2 for now. But for the life of me couldn't figure out how to get to the tool section so I can re-partition it back to ext3!!!
All I could get in to is twrp recovery and that's it. how do I even get into the bootmenu section where I can choose recovery, cpu settings, tools, etc? There's no red Moto logo with blue LED at boot up anymore
Is there any uninstall instruction somewhere, or perhaps someone should write one?
44 viewers but no reply
any idea if i can install some sort of apps to achieve the same end? like a wipe app to re-partition it to ext3, and then an older recovery to install cm7 rom, or restore my cm7 backup?
don't really want to just try and see what will happens. also trying to avoid flashing sbf and start from scratch.....
edit: will aromawiper work? reboot to twrp recovery 2.6.3.0, aromawipe to ext3 and then flash cm7.2 rom straight after? expert opinion and advice please.
edit 2: oh well, tried it and didn't work. might be because i didn't install an older, compatible recovery before i rebooted. stuck at red moto logo and had to flash sbf and start all over again......
case closed...........
jh20 said:
44 viewers but no reply
any idea if i can install some sort of apps to achieve the same end? like a wipe app to re-partition it to ext3, and then an older recovery to install cm7 rom, or restore my cm7 backup?
don't really want to just try and see what will happens. also trying to avoid flashing sbf and start from scratch.....
edit: will aromawiper work? reboot to twrp recovery 2.6.3.0, aromawipe to ext3 and then flash cm7.2 rom straight after? expert opinion and advice please.
edit 2: oh well, tried it and didn't work. might be because i didn't install an older, compatible recovery before i rebooted. stuck at red moto logo and had to flash sbf and start all over again......
case closed...........
Click to expand...
Click to collapse
you can flash cm10 to get the boot menu to format to ext3 then flash to cm7.2.
Thats what i did when i tested cm11.
Or use Aroma wiper to format to ext3 and flash CM7.2.
Sent from my Nexus 7 using Tapatalk
aperture said:
you can flash cm10 to get the boot menu to format to ext3 then flash to cm7.2.
Thats what i did when i tested cm11.
Click to expand...
Click to collapse
thanks. i'll remember that next time. don't know why i didn't think of that. panic striken maybe
hotdog125 said:
Or use Aroma wiper to format to ext3 and flash CM7.2.
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
that's exactly what i did but didn't work. aromawiper seems to have worked properly but twrp 2.6.3.0 keep saying "no os installed" after i installed the gb rom and tried to reboot. tried maniac's cm7.2 and an older wiui gingerbread rom. i thought it might be a hickup and rebooted anyway and that was it.
don't know what went wrong there. has anyone actually tried this method before and got it to work?
edit: imho twrp is not worth it. it rebooted 8-10 times on me after installing cm11 and tried to get back into recovery to flash gapps. also other problems like blank backup files and my failures to install rom problem. they should have stuck to cwm until the problems are fixed.
edit 2: and i think removing bootmenu is not a good idea. more steps to take if you want to go back to cm7.2.