Any way I can get it to boot without wiping? The problem occurred when I accidently did the 3 key method to get into cwm... forgetting you're not supposed to.. and then flashed glitch's new kernel.
Plug into computer, turn on, open command prompt, type adb shell, type reboot recovery. Next flash the kernel in the proper recovery.
good day.
chopper the dog said:
Plug into computer, turn on, open command prompt, type adb shell, type reboot recovery. Next flash the kernel in the proper recovery.
good day.
Click to expand...
Click to collapse
adb shell on the computer or phone? I can't even boot the phone.
On the computer to enter into recovery then flash kernel.
quedi12 said:
On the computer to enter into recovery then flash kernel.
Click to expand...
Click to collapse
doesn't it only work though if the phone is in usb debugging mode?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I don't know what to do. I've tried flashing cwm via odin again.. tried wiping... tried reinstalling kernel / rom. nothing but a bootloop everytime now.
There have been some problems with the Glitch Kernel and the newest Cyanogen nightlies causing it to Bootloop. The Glitch developer is aware and working on it. I had to revert back to stock and start over. For now im staying at CM7 nightly 35 and using Glitch.
DakotaS96 said:
There have been some problems with the Glitch Kernel and the newest Cyanogen nightlies causing it to Bootloop. The Glitch developer is aware and working on it. I had to revert back to stock and start over. For now im staying at CM7 nightly 35 and using Glitch.
Click to expand...
Click to collapse
X2
Had to atlas pit and repartition, then back to build 35 was the only way I could get rid of the boot loop when trying to go to the newest nightly build.
Sent from my SCH-I500 using XDA App
to fix the adb problem I had to install the drivers.. which I DID but the instructions on the wiki were wrong... so it took awhile to find where they got installed to. I finally got the newest cwm + glitch v12 kernel to work though. Took all day!!!
I had to same problem, just had to restore the CWM backup
Related
No matter which FroYo Release I try, "Fix-permissions" doesnt seem to work properly. Regardless of what i try, it only fixes permissions for the CWM app itself. So its shows two lines of text for CWM, and its done. Any one know why this is happening?
Ps- I've tried completely un installing CWM and deleting its folders and everything associated with it but to no avail. I'm out of ideas...
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I take it that everyones ClockWork's "Fix-Permissions" works perfectly fine? Any input would be nice. THanks
You need to get into the actual clockwork recovery and fix perm there. So, open ROM manager, select reboot into recovery, select re-install packages, clockwork recovery should boot up, then goto advance options at the bottom of the list and select, then you should see the fix perm option about half way down the list, select it and your done.
I have the same problem. I'm thinking it's to do with CWM needing to be updated for the vibrant. Since there is no current 2.2 official/supported release it will not be updated as of yet. I haven't contacted koush(dev), but I'm sure he knows.
Even if you do go directly into CWR you can select it, but it doesn't seem to scroll the script...
I am using the stock Froyo eugene posted and I am not having any problems with ROM manager or CWR. I have done two backups with ROM man and wiped cache, dalvik cache, and fix permissions in CWR and it worked. I even got the fix permissions log on my SD card.
This must be it, because same thing happens if i try from the recovery. Is there anyone that can get fix-permissions to actually run the entire script? Would be nice to know if its a select few, everyone, or just us two
All~G1 said:
I have the same problem. I'm thinking it's to do with CWM needing to be updated for the vibrant. Since there is no current 2.2 official/supported release it will not be updated as of yet. I haven't contacted koush(dev), but I'm sure he knows.
Even if you do go directly into CWR you can select it, but it doesn't seem to scroll the script...
Click to expand...
Click to collapse
Im also experiencing this. Im running AOSPish froyo.
I am currently running cyanogenMod 7.1 fxp 044 in my X10i, and have problems to upgrade to fxp 047. This is what I have done:
I downloaded the fxp 047 package and put the update-cm-7.2.0-RC0-es209ra-KANG-signed.zip in sdcard.
then I booted the phone into xrecovery mode, select install custom zip form sdcard
and I got error messege saying that installation aborted with a long string of code ended with "error in...zip (status 7)".
I though the problem may be the locked bootloader, so I followed the post by 9Lukas5, but I got stuck already at step 2! After I downgraded the kernel, I plugged in the phone to the computer, but the flashtool kept saying the phone didnt turn on the usb debugging mode, although the debugging is ON already...
any idea? Any Help is appreciated!
The phone info is listed below:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
First, I dont know if you need a unlocked bootloader..
2nd, you have to flash the rom with cwm recovery
http://forum.xda-developers.com/showpost.php?p=17998666&postcount=12446
Sent from my X10 using xda premium
LzVebz said:
First, I dont know if you need a unlocked bootloader..
2nd, you have to flash the rom with cwm recovery
Click to expand...
Click to collapse
thank you for your answer
but why cwm recovery? is Xrecovery not compatible with cyanogenMod rom?
I think all the new cyanogenmod developments are happening under CWM recovery only. Not sure about the xrecovery rom though. But I guess CWM offer better options. As we can directly reboot to recovery!
huntish said:
I think all the new cyanogenmod developments are happening under CWM recovery only. Not sure about the xrecovery rom though. But I guess CWM offer better options. As we can directly reboot to recovery!
Click to expand...
Click to collapse
I actually installed my previous cyanogenmod rom 7.1 using Xrecovery, but gonna try CWM recovery and hope it works!
So, last night i was using my tablet and it started acting weird. youtube videos not loading, apps locking up, etc. So I decided to reboot my tab to resolve it. But now it wont boot. The boot animation stops part way through, and after a while it turns itself off.
My next thought was to go to recovery, but that doesnt work either. When I try to enter recovery it hangs at the twrp splash screen. At this point I dont know what to do
Any ideas?
What ROM were you on?
Sent from my Infamous Tab.
slim bean
Bigandrewgold said:
slim bean
Click to expand...
Click to collapse
It sounds like a bad flash. Perhaps try using Odin to reflash a working recovery again? Then do a complete wipe and restore a backup to get working again.
If that doesn't work it sounds like its stock firmware time...
Sent from my Infamous Tab.
djmatt604 said:
It sounds like a bad flash. Perhaps try using Odin to reflash a working recovery again? Then do a complete wipe and restore a backup to get working again.
If that doesn't work it sounds like its stock firmware time...
Sent from my Infamous Tab.
Click to expand...
Click to collapse
I just flashed cwm and it loads, but when trying to wipe data it stalls and eventually crashes, guess ill try stock firmware
ugh, flashed stock in odin and it is stuck at this screen, not moving, and its been there for a good 5 minutes
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Damn. If you have flashed stock firmware you will have stock android recovery...however using it is rather scary because of the potential for the emmc brick bug. If you weren't able to wipe the device before flashing the stock firmware you're probably locking up on a bad driver or lib or something.
Do you have adb access to the device? Are you able to pull a Logcat?
Sent from my Infamous Tab.
ok, I got it working. I rebooted from that screen, did a factory reset in stock recovery, flashed cwm, and rebooted a few more times and I finally was able to get it booted up.
Bigandrewgold said:
ok, I got it working. I rebooted from that screen, did a factory reset in stock recovery, flashed cwm, and rebooted a few more times and I finally was able to get it booted up.
Click to expand...
Click to collapse
Phew!!!
Yeah man, factory resets in stock recovery are really scary. Good job getting back on a custom recovery. Make sure it is a newer recovery (CWM 6+) so you are safe when you run a FR.
Get re-rooted and back into a ROM with a safe kernel too and you're golden congrats!
Sent from my Infamous Tab.
hi i managed to update my tab to the latest firmware 4.0.4 . Previously it was already rooted and TWRP installed. I was thinking of rooting and backing up this build so from romtoolbox i boot into recovery mode (thinking that i will be seeing TWRP) But when boot i was shown the folllowing picture
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
since all of my buttons are not working (hence the reason installing TWRP ) i was ok fine lets reboot it via adb. therefore i run adb reboot and yet it still boots back to the same screen . Thinking i need to reverting all of the changes via odin i tried reboot download also does not work. reboot-bootloader also does not work. apprently i am stuck at this screen.
Right now i only have access to adb and is there any way i can recover from this?
many thanks again
I'm assuming you were running some kind of custom rom with TWRP as your recovery before going to stock ICS. Essentially, flashing stock ICS overwrote the old TWRP.
To fix it, flash in TWRP again (its somewhere in the development section) via Odin.
EDIT: If you can't access download mode... Try push the TWRP .tar file via ADB
Sent from my GT-P7510
Soryuu said:
I'm assuming you were running some kind of custom rom with TWRP as your recovery before going to stock ICS. Essentially, flashing stock ICS overwrote the old TWRP.
To fix it, flash in TWRP again (its somewhere in the development section) via Odin.
EDIT: If you can't access download mode... Try push the TWRP .tar file via ADB
Sent from my GT-P7510
Click to expand...
Click to collapse
the thing is i only root and installed twrp for the sake of backing up since my daughter loves to install application. I've read about pushing / Installing application but that would requires root right? this is my command console like
Right now is there a way to force it to boot into download because thats the only way i see i can fix it (without using physical buttons)
Again many thanks for replying.
Day before yesterday i was trying to flash rom to update (mi pad 1 )4.4 to lollipop version and I’ve did everything exactly same like tutorial first rooted with update.zip to activate twrp then flash custom rom but it got error in middle due to this when I rebooted the device it stuck on logo . I’ve flashed recovery firmware by mi flashing tool it goes 100% in bootloader mode but still stuck on logo. Any method to back to normal?
Did you flash shied blob based rom?
SquirreL_64 said:
Did you flash shied blob based rom?
Click to expand...
Click to collapse
Nope I’ve just flashed different normal fastboot roms . Only can access fastboot mode and recovery mode even restarting stuck on mi logo don’t know when it gonna be fixed
Gagan36 said:
Nope I’ve just flashed different normal fastboot roms . Only can access fastboot mode and recovery mode even restarting stuck on mi logo don’t know when it gonna be fixed
Click to expand...
Click to collapse
Did u do something like tos or boot?
BTW which rom did you flash cuz miui never released fastboot rom for lolipop
SquirreL_64 said:
Did you flash shied blob based rom?
Click to expand...
Click to collapse
i have the same problem... stuck in bootlop, and before that i used to have a shied blob based rom... what should i do now?
thank you.
EDIT:fastboot ROMs? Never know that it existed for mi pad.
1. Download Mi PC suite and connect it in fastboot mode.
If everything go normal then it will automatically detect the respective ROM.
Check the screenshot below.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
2. Just click on Flash device.
Now if all the things are normal it will reboot normally.