Related
I've tried all types of flashing and so, yet I get same black screen after rebooting my phone
not sure if any of my files are wrong, yet I don't think so
I've tried all I can think of, all custom roms and stuff, but no result
I can get to root my phone, install bootstraper then bootmenu, wiped all data and cache but while installing the mod, it loads the installation and after last reboot I get a blank screen with no options to get back in bootmenu or recovery
it's rather my fault or not, but I can't install it, not even with your fast help from post above
any tips left?
cosmy032 said:
I've tried all types of flashing and so, yet I get same black screen after rebooting my phone
not sure if any of my files are wrong, yet I don't think so
I've tried all I can think of, all custom roms and stuff, but no result
I can get to root my phone, install bootstraper then bootmenu, wiped all data and cache but while installing the mod, it loads the installation and after last reboot I get a blank screen with no options to get back in bootmenu or recovery
it's rather my fault or not, but I can't install it, not even with your fast help from post above
any tips left?
Click to expand...
Click to collapse
Revert to stock and start over. dont panic.
I'm to stock now...but I can instal custom rom..
cosmy032 said:
I'm to stock now...but I can instal custom rom..
Click to expand...
Click to collapse
What stock do you have? froyo or gingerbread one? and what rom do you want install?
Because if you have Gingerbread base you cannot install miui or cm for froyo kernel..
but you have a Cm gb kernel based..
sorry for my English
I have Gingerbread (2.3.4) and I want to instal CM7 (http://temp.anonymouz.eu/cm72-111215.1631-NIGHTLY-Milestone2-GB-v1.3.zip) or else...but I cannot instal anything..the screen remains black after apply update.zip.. and to startup phone again only after I flash SBF...
Sorry for my English..but i really need help
you have to downgrade your kernel.
just folow instructions in this topic:
http://forum.xda-developers.com/showthread.php?t=1497263
try this!
cosmy032 said:
I have Gingerbread (2.3.4) and I want to instal cm72-111215.1631-NIGHTLY-Milestone2-GB-v1.3.zip or else...but I cannot instal anything..the screen remains black after apply update.zip.. and to startup phone again only after I flash SBF...
Click to expand...
Click to collapse
There's a sbf-fix for that issue on the CM7 thread, for GB kernel you need to apply update.zip, wipe data/cache/dalvik, reboot and you get a blank screen, then you flash the sbf-fix via RSDLite and now you can boot
You can also try CM9 which is based on European GB
wow it works, thank you all for all :X
Hi all
I use to run cm-7.2 Jordan without any issues. Decided however to upgrade and test cm10 but since I didn't find it stable enough I decided to downgrade back to 7.2. The flash succeed without issues but when I reboot I get stuck with the Google logo and the os never boot up.
I tried to go through cm.7.1 but no luck there, same issue.
Any clue how i can resolve this?
llavsor said:
Hi all
I use to run cm-7.2 Jordan without any issues. Decided however to upgrade and test cm10 but since I didn't find it stable enough I decided to downgrade back to 7.2. The flash succeed without issues but when I reboot I get stuck with the Google logo and the os never boot up.
I tried to go through cm.7.1 but no luck there, same issue.
Any clue how i can resolve this?
Click to expand...
Click to collapse
Try to wipe all from stock recovery ----> Power+Vol dwn
Kayant said:
Try to wipe all from stock recovery ----> Power+Vol dwn
Click to expand...
Click to collapse
Thanks for quick reply. I tried that and the phone loaded a android character with a triangle and a exclamation mark. I don't have a good feeling about that
llavsor said:
Thanks for quick reply. I tried that and the phone loaded a android character with a triangle and a exclamation mark. I don't have a good feeling about that
Click to expand...
Click to collapse
That's good sorry forget to say you need to hold VOL dwn& Vol Up at the same time then wipe all...
Good luck
Exactly the same problem here, cannot downgrade to CM7.
Any good news?
Flash official froyo (I used ver 2.2.2)sbf via rsdlite. Root it using superoneclick and install 2init bootmenu 2.0. In custom recovery do full factory wipe follow with restore your nandroid 7.2 if you have them. If it booting hang at start screen, flash any froyo fixed sbf that contain the froyo kernel(optional). This way all your previous user data will still be intact.
Sent from my awesome rooted Defy: 2.3.6 XDA premium
So the recovery won't work and will have to start with SBF. Will wait until I have the computer environment to do so.
Thanks!
Kayant said:
Try to wipe all from stock recovery ----> Power+Vol dwn
Click to expand...
Click to collapse
farsight73 said:
Flash official froyo (I used ver 2.2.2)sbf via rsdlite. Root it using superoneclick and install 2init bootmenu 2.0. In custom recovery do full factory wipe follow with restore your nandroid 7.2 if you have them. If it booting hang at start screen, flash any froyo fixed sbf that contain the froyo kernel(optional). This way all your previous user data will still be intact.
Sent from my awesome rooted Defy: 2.3.6 XDA premium
Click to expand...
Click to collapse
Okey I have now flashed 2.2.2 sbf with RSDlite and after flash the phone still hangs during boot, now with the ugly Motoroly M instead of the Google logo from CM. So I guess I am back to square one, any idean anyone
llavsor said:
Okey I have now flashed 2.2.2 sbf with RSDlite and after flash the phone still hangs during boot, now with the ugly Motoroly M instead of the Google logo from CM. So I guess I am back to square one, any idean anyone
Click to expand...
Click to collapse
Wipe all from stock recovery that's you needed to do btw before installing cm7.... Sbf is not needed.
Go to stock recovery and wipe all your ROM should boot...
Let's Go ^_^
llavsor said:
Okey I have now flashed 2.2.2 sbf with RSDlite and after flash the phone still hangs during boot, now with the ugly Motoroly M instead of the Google logo from CM. So I guess I am back to square one, any idean anyone
Click to expand...
Click to collapse
Factory reset from stock bootmenu again. If it still hangs, flash sbf again with another factory reset afterwards just to be safe. BTW, I've had times where 3+ sbf flashes with factory resets were needed to get the phone to boot again.
One problem you might be having is if you formatted /data and /cache to ext4. Maybe it was just me, but I had to reinstall CM10, change back to ext3, flash sbf, then install CM7. Changing to ext3 and flashing CM7 didn't work -- same problem you're having. I wasn't sure if ext4 was the problem so I made sure I changed back to ext3 before sbf flashing. I'm not sure if the sbf reformats the partitions or just wipes them like a factory reset. If you've already flashed the sbf, then you can't install a CM10 rom to change back to ext3... Worse come to worse, you maybe able to install one of the custom sbf's with CM10 custom kernel preinstalled, change to ext3, flash official sbf, factory reset, then install CM7. I haven't looked into them because I make my own custom sbf's .
Bravo users are having this exact problem and my solution is to ensure that /data and /cache are ext3, flash the sbf and start from scratch -- the only guaranteed way I know of to fix this problem. Another Bravo user had the same problem and managed to fix it by changing some /data permissions over adb -- the user didn't specify the exact things done so I'm waiting on a reply with more details.
skeevy420 said:
Factory reset from stock bootmenu again. If it still hangs, flash sbf again with another factory reset afterwards just to be safe. BTW, I've had times where 3+ sbf flashes with factory resets were needed to get the phone to boot again.
One problem you might be having is if you formatted /data and /cache to ext4. Maybe it was just me, but I had to reinstall CM10, change back to ext3, flash sbf, then install CM7. Changing to ext3 and flashing CM7 didn't work -- same problem you're having. I wasn't sure if ext4 was the problem so I made sure I changed back to ext3 before sbf flashing. I'm not sure if the sbf reformats the partitions or just wipes them like a factory reset. If you've already flashed the sbf, then you can't install a CM10 rom to change back to ext3... Worse come to worse, you maybe able to install one of the custom sbf's with CM10 custom kernel preinstalled, change to ext3, flash official sbf, factory reset, then install CM7. I haven't looked into them because I make my own custom sbf's .
Bravo users are having this exact problem and my solution is to ensure that /data and /cache are ext3, flash the sbf and start from scratch -- the only guaranteed way I know of to fix this problem. Another Bravo user had the same problem and managed to fix it by changing some /data permissions over adb -- the user didn't specify the exact things done so I'm waiting on a reply with more details.
Click to expand...
Click to collapse
Okey good advice.
Here is where I am at now. I have flashed a number of different SFBs and I end up with the same situation every time. RSDLIte finish the process nicely but the phone get stuck with the flashing M. When I reboot manually I get passed the M and to the Android text/logo and there I get stuck.
I get advice to do a factory reset but how do I do that. The CW bootloader is gone and I can't get to the original boot loader either. I hit volume down and power, get to the triangle screen where I am supposed to hit the right bottom corner but nothing happens.
So I cant boot the phone to get into a menu where I can change to ext3 if this is a problem.
Please help, how can I get further?
Since I have no luck restoring stock rom I now have the following plan.
Install ClockWorkMod recovery with ADB.
Using recovery to do a factory reset and clear cache.
Flash a CM10 ROM (or any rom that will successfully boot up my phone).
From that start over to downgrade to CM9 to find a stable ROM.
The question I have now is if I will be able to use ADB with the USB connection mode I get from the bootloader (volume up+pwr button)? Or does ADB actually require that I can boot my phone and go into some other USB mode such as UMS or MTP.
Second question. Playing with restoring stock ROM i run out of battery and now my defy wont charge (only see a big question mark when loading). Seems like I get no power when USB is connected so is there a way for me to charge the battery or do I need to find another happy camper in town with a working defy that can power up my battery?
llavsor said:
Okey good advice.
Here is where I am at now. I have flashed a number of different SFBs and I end up with the same situation every time. RSDLIte finish the process nicely but the phone get stuck with the flashing M. When I reboot manually I get passed the M and to the Android text/logo and there I get stuck.
I get advice to do a factory reset but how do I do that. The CW bootloader is gone and I can't get to the original boot loader either. I hit volume down and power, get to the triangle screen where I am supposed to hit the right bottom corner but nothing happens.
So I cant boot the phone to get into a menu where I can change to ext3 if this is a problem.
Please help, how can I get further?
Click to expand...
Click to collapse
In froyo, you should hit vol up/down together to enter stock recovery.
If you have your cm7 nandroid or your gingerbread nandroid 2.3.6. In,custom recovery cm10, restore them. Your phone would not boot but you have your cm7 or gingerbread cwm by then, that you could format cache and total wipe back to ext.3 in the recovery menu, format/wipe follow with another nandroid restore and flash fix sbf from rsdlite.
But then the best way is go back totally clean by flashing stock froyo and root, install 2init with bootmenu 2.0. Then total wipe in recovery follow with restore your cm7 or gingerbread nandroids and flash the corresponding fix sbf via rsdlite.
Charging dead rom defy would need the MacGyver trick then. But some say if you leave it connected overnight in pc usb would charged it somehow but slow..
On 2nd thought.. you need to tell us yoyr defy model...green lense, red lense or the defy plus?? These models has their own characteristics in term of play around in cwm and way of flashing..
Sent from my awesome rooted Defy: 2.3.6 XDA premium
farsight73 said:
In froyo, you should hit vol up/down together to enter stock recovery.
If you have your cm7 nandroid or your gingerbread nandroid 2.3.6. In,custom recovery cm10, restore them. Your phone would not boot but you have your cm7 or gingerbread cwm by then, that you could format cache and total wipe back to ext.3 in the recovery menu, format/wipe follow with another nandroid restore and flash fix sbf from rsdlite.
But then the best way is go back totally clean by flashing stock froyo and root, install 2init with bootmenu 2.0. Then total wipe in recovery follow with restore your cm7 or gingerbread nandroids and flash the corresponding fix sbf via rsdlite.
Charging dead rom defy would need the MacGyver trick then. But some say if you leave it connected overnight in pc usb would charged it somehow but slow..
On 2nd thought.. you need to tell us yoyr defy model...green lense, red lense or the defy plus?? These models has their own characteristics in term of play around in cwm and way of flashing..
Sent from my awesome rooted Defy: 2.3.6 XDA premium
Click to expand...
Click to collapse
Thanks for very informative reply. I have a Defy 525 with red lens.
It's working.
I found a friend blessed with a defy and used that to charge the battery, tried to charge it over night with USB but it didn't work.
I then followed the steps from the last post and managed to flash a stock rom and then from there I rooted the phone with SuperOneClick, installed 2ndInit with ADB (guess you could use an apk installer from the phone as well ). I booted into recovery and flashed 7.2.0 Jordan from CM and now I am where I started a few weeks back.
Thank you all for your help.
That was the low battery problem.......
Since i had this i allways look for a full battery
If you think your defy is dead , a look for a empty battery won't be mad
Could anybody took a reminder info into beginners guide
MB525 red lense
in teamwin official website i couldn't find twrp recovery support for motorola bravo, however motorola defy was in the list to get twrp recovery.
does TWRP for defy work on bravo? or we need a different for bravo? i love that recovery ...can some body help me install that on my bravo???
hiandro said:
in teamwin official website i couldn't find twrp recovery support for motorola bravo, however motorola defy was in the list to get twrp recovery.
does TWRP for defy work on bravo? or we need a different for bravo? i love that recovery ...can some body help me install that on my bravo???
Click to expand...
Click to collapse
The Defy TWRP works on the Bravo, but its only up to version 2.1 and can't install large Aroma roms (WR, Pikachu, etc). Your better off reading the thread over at Defy Development. Its neat and works, but our custom CWM 5 is the best for us in terms of reliability and stability.
skeevy420 said:
The Defy TWRP works on the Bravo, but its only up to version 2.1 and can't install large Aroma roms (WR, Pikachu, etc). Your better off reading the thread over at Defy Development. Its neat and works, but our custom CWM 5 is the best for us in terms of reliability and stability.
Click to expand...
Click to collapse
can u give me link to download latest CWM please.
hiandro said:
can u give me link to download latest CWM please.
Click to expand...
Click to collapse
Its installed be default with CM10 or PA. The newer the rom, the newer the recovery.
You can copy the zip/system/bootmenu/.... to other roms to get the touch ui in the bootmenu, just don't overwrite your current roms init scripts....and use a PRE 2nd Kernel zip when porting the bootmenu to non custom kernel roms. This isn't something I'd advise doing cause if you don't know what your fully doing you can easily put yourself in a position to flash the sbf. I sbf'd 3 times adding the JB Touch bootmenu to CM7.
skeevy420 said:
Its installed be default with CM10 or PA. The newer the rom, the newer the recovery.
You can copy the zip/system/bootmenu/.... to other roms to get the touch ui in the bootmenu, just don't overwrite your current roms init scripts....and use a PRE 2nd Kernel zip when porting the bootmenu to non custom kernel roms. This isn't something I'd advise doing cause if you don't know what your fully doing you can easily put yourself in a position to flash the sbf. I sbf'd 3 times adding the JB Touch bootmenu to CM7.
Click to expand...
Click to collapse
I installed cm10 then after I went to stable recovery and I wipe data/factory reset and then wipe cache and again wipe dalvik cache,and then I went to install zip from SD card and then choose mokee and flashed the zip.and when I reboot the phone it got stuck at Motorola red logo. again i boot into recovery (it was different, which mokee installed maybe)and when i wipe data and cache it said something like this:can't mount E/cache/recovery/log .and then i went to backup and restore and restored my cm10 backup and it only restored system(no data) why did this happen did I did something wrong?? or is there problem in recovery?? please tell me about this.
hiandro said:
I installed cm10 then after I went to stable recovery and I wipe data/factory reset and then wipe cache and again wipe dalvik cache,and then I went to install zip from SD card and then choose mokee and flashed the zip.and when I reboot the phone it got stuck at Motorola red logo. again i boot into recovery (it was different, which mokee installed maybe)and when i wipe data and cache it said something like this:can't mount E/cache/recovery/log .and then i went to backup and restore and restored my cm10 backup and it only restored system(no data) why did this happen did I did something wrong?? or is there problem in recovery?? please tell me about this.
Click to expand...
Click to collapse
I have a couple of ideas, but I'd be guessing with all of them. Probably just an error from CM10 using a newer recovery than Mokee. Since CM10's /system was restored, so was its bootmenu\recovery -- try doing a full restore now that you're using the same recovery that backed it up .
Crap like this is why we need an unlocked bootloader, or even just a place to hide a custom recovery -- with every rom you flash, your recovery changes and bad things can\have happened. While its nowhere as bad as it once was, problems like yours still occur from time to time. Its the same reason that there's so many posts with people having problems from using BandroidX Recovery -- its a very old CWM based recovery that uses different formats than whats used now (can't even install newer roms with it). Old and new don't usually play nicely with us .
skeevy420 said:
I have a couple of ideas, but I'd be guessing with all of them. Probably just an error from CM10 using a newer recovery than Mokee. Since CM10's /system was restored, so was its bootmenu\recovery -- try doing a full restore now that you're using the same recovery that backed it up .
Crap like this is why we need an unlocked bootloader, or even just a place to hide a custom recovery -- with every rom you flash, your recovery changes and bad things can\have happened. While its nowhere as bad as it once was, problems like yours still occur from time to time. Its the same reason that there's so many posts with people having problems from using BandroidX Recovery -- its a very old CWM based recovery that uses different formats than whats used now (can't even install newer roms with it). Old and new don't usually play nicely with us .
Click to expand...
Click to collapse
Yeah, i tried to restore backup using cm10 recovery and although it said cant restore .android.secure something like that(iam not quite sure) it restored system as well as data.
The thing is i like mokee os .its speed, clean and clear... ecetra but it is not jelly bean.can't we have a cm10 tweaked and modified for bravo.of course I love your PA jelly bean there are lots of tablet tweaks can you also add some other functions like in pimp my rom.
And thanks man for answering my queries
I updated my phone to latest liquidsmooth rom two days ago and the phone freezes and restarts/reboots randomly like sometimes when im on phone/ playing a game/ using browser/ connected to charger. Yesterday I changed rom to latest carbon rom. Did install (3 wipes) as told in the thread but im still having the reboots.
Im using TWRP recovery and had used Utility 1.10 to go back to stock from Energy rom with safestrap recovery.
Can tell me whats the prob? Is it the kernel problem?
Have you tried upgrading or reflashing TWRP and then doing a clean install of Carbon? Its probably worth doing a fresh download of each first just to make sure you cover all your bases. These reboots were happening to me a few months ago and it drove me mad. following these steps fixed it for me.
jcxmej said:
I updated my phone to latest liquidsmooth rom two days ago and the phone freezes and restarts/reboots randomly like sometimes when im on phone/ playing a game/ using browser/ connected to charger. Yesterday I changed rom to latest carbon rom. Did install (3 wipes) as told in the thread but im still having the reboots.
Im using TWRP recovery and had used Utility 1.10 to go back to stock from Energy rom with safestrap recovery.
Can tell me whats the prob? Is it the kernel problem?
Click to expand...
Click to collapse
Honestly, if you're using SafeStrap, that might be your problem. Remove SS and flash the ROM in TWRP. If your bootloader is unlocked, you don't really want to use SS. Also, make a stock backup in TWRP, prior to flashing. This way, it will be easier for you to recover in the future, and you won't need to go through the painful process of fastboot.
RikRong said:
Honestly, if you're using SafeStrap, that might be your problem. Remove SS and flash the ROM in TWRP. If your bootloader is unlocked, you don't really want to use SS. Also, make a stock backup in TWRP, prior to flashing. This way, it will be easier for you to recover in the future, and you won't need to go through the painful process of fastboot.
Click to expand...
Click to collapse
Like I said on first post Im using TWRP now. Previously I was using safestrap. I removed it and installed TRWP. Anyways thanks.
PantherVT said:
Have you tried upgrading or reflashing TWRP and then doing a clean install of Carbon? Its probably worth doing a fresh download of each first just to make sure you cover all your bases. These reboots were happening to me a few months ago and it drove me mad. following these steps fixed it for me.
Click to expand...
Click to collapse
Thanks man. I will upgrade TWRP or reinstall it first. Thanks for that tip. Will post again if it doesnt work.
Still having those restarts. Really irritating. Froze and rebooted 4 5 times today morning while I was on call and trying to message. I reflashed reinstalled everything. I used both Utility 1.10 and 1.20. Im getting reboots even the stock ROM after using the Utility. I am confused which Utility I should be using. I had no issue of rebooting before flashing using Utility. Can someone give me exact procedure to reflash so that i know i am not missing out anything.
jcxmej said:
Still having those restarts. Really irritating. Froze and rebooted 4 5 times today morning while I was on call and trying to message. I reflashed reinstalled everything. I used both Utility 1.10 and 1.20. Im getting reboots even the stock ROM after using the Utility. I am confused which Utility I should be using. I had no issue of rebooting before flashing using Utility. Can someone give me exact procedure to reflash so that i know i am not missing out anything.
Click to expand...
Click to collapse
you might need to do a clean install.
- what version of TWRP are you using (anything other than 2.4 should be fine)?
- to perform the clean install, mount system, then try wiping everything (system, factory reset, & internal storage) - DO NOT WIPE external SD (I presume this is where you store the ROM files
- after wiping, reboot recovery, then install whichever 4.2.2 ROM you want follow by the GApps (use the 3/2013 version)
jco23 said:
you might need to do a clean install.
- what version of TWRP are you using (anything other than 2.4 should be fine)?
- to perform the clean install, mount system, then try wiping everything (system, factory reset, & internal storage) - DO NOT WIPE external SD (I presume this is where you store the ROM files
- after wiping, reboot recovery, then install whichever 4.2.2 ROM you want follow by the GApps (use the 3/2013 version)
Click to expand...
Click to collapse
Since TWRP wasnt working for me, I tried flashing with CWM recovery by hashcode. Still had reboots. I was using TWRP 2.3.2.3
When you say wipe everything, does it include 'modem' and 'pds'? Saw these two options also inside Mount/Format menu of CWM recovery.
Also there was an option 'Mount sdcard' (internal I suppose) but when i click it nothing happens it remains as Mount sdcard. Rest of it changes from Mount to Unmount. Is there some problem with that?
Do I have to just Mount system only? Also after rebooting recovery do I have to mount system again?
I try again as you said meanwhile.
jcxmej said:
Since TWRP wasnt working for me, I tried flashing with CWM recovery by hashcode. Still had reboots. I was using TWRP 2.3.2.3
When you say wipe everything, does it include 'modem' and 'pds'? Saw these two options also inside Mount/Format menu of CWM recovery.
Also there was an option 'Mount sdcard' (internal I suppose) but when i click it nothing happens it remains as Mount sdcard. Rest of it changes from Mount to Unmount. Is there some problem with that?
Do I have to just Mount system only? Also after rebooting recovery do I have to mount system again?
I try again as you said meanwhile.
Click to expand...
Click to collapse
nope, just system/factory reset/internal storage.
yes, make sure everything is mounted (checked) so that they read "unmount"
jco23 said:
nope, just system/factory reset/internal storage.
yes, make sure everything is mounted (checked) so that they read "unmount"
Click to expand...
Click to collapse
Did exactly like said. Got into CWM recovery. Mounted system. Formatted system, data, cache, sdcard. Did factory reset and wiped the caches. Then rebooted recovery. Then installed the ROM, 3/13 gapps, gsm fix. Reboot system. Still no use. I got 2 reboots in 5 mins in the ROM. I checked the md5 of the files and its ok. Dont know what else to try?
jcxmej said:
Did exactly like said. Got into CWM recovery. Mounted system. Formatted system, data, cache, sdcard. Did factory reset and wiped the caches. Then rebooted recovery. Then installed the ROM, 3/13 gapps, gsm fix. Reboot system. Still no use. I got 2 reboots in 5 mins in the ROM. I checked the md5 of the files and its ok. Dont know what else to try?
Click to expand...
Click to collapse
which ROM are you trying to install?
jco23 said:
which ROM are you trying to install?
Click to expand...
Click to collapse
LiquidSmooth v2.9 by DHacker29
http://forum.xda-developers.com/showthread.php?t=2373703
I have also tried Carbon ROM but was having reboots with that too. I liked liquidsmooth better so trying to make this work.
jcxmej said:
LiquidSmooth v2.9 by DHacker29
http://forum.xda-developers.com/showthread.php?t=2373703
I have also tried Carbon ROM but was having reboots with that too. I liked liquidsmooth better so trying to make this work.
Click to expand...
Click to collapse
are you flashing a kernel at the same time?
I would recommend trying a basic 4.2.2 ROM right now - like unoffical AOKP.
another problem could be the GApps or GSM fix. try installing just the ROM without the GApps perhaps?
carbon was very solid too. unfortunately, I can't help you with the GSM fix, as I am CDMA.
jco23 said:
are you flashing a kernel at the same time?
I would recommend trying a basic 4.2.2 ROM right now - like unoffical AOKP.
another problem could be the GApps or GSM fix. try installing just the ROM without the GApps perhaps?
carbon was very solid too. unfortunately, I can't help you with the GSM fix, as I am CDMA.
Click to expand...
Click to collapse
Okay i will try but had this reboot issue even with the stock ROM after flashing with Utility 1.20.
jcxmej said:
Okay i will try but had this reboot issue even with the stock ROM after flashing with Utility 1.20.
Click to expand...
Click to collapse
hmm.... not really sure then. perhaps you lost root? try re-installing SuperSU - I'm just grasping at straws here.
someone mentioned a similar issue:
http://forum.xda-developers.com/showthread.php?p=44317692#post44317692
jco23 said:
hmm.... not really sure then. perhaps you lost root? try re-installing SuperSU - I'm just grasping at straws here.
someone mentioned a similar issue:
http://forum.xda-developers.com/showthread.php?p=44317692#post44317692
Click to expand...
Click to collapse
I think I have root access I had no issue with it. Okay maybe I will check the thread you gave. Anyways I tried Eclipse ROM which is based AOKP. Still had reboots. So I switched back to liquid. Anyways Im gonna keep trying the basics. If anyone has any suggestions I could try its welcome.
PS. Should I flash another kernel with the ROM just in case ? I have been only installing ROM and gapps only till now.
jcxmej said:
I think I have root access I had no issue with it. Okay maybe I will check the thread you gave. Anyways I tried Eclipse ROM which is based AOKP. Still had reboots. So I switched back to liquid. Anyways Im gonna keep trying the basics. If anyone has any suggestions I could try its welcome.
PS. Should I flash another kernel with the ROM just in case ? I have been only installing ROM and gapps only till now.
Click to expand...
Click to collapse
I don't think changing the kernel will do it.... I suspect the issue is with your recoveries - will respond in other thread....
Hey all,
I RSD'd the other day and then re-rooted and re-unlocked the bootloader (yes, I now know it stays unlocked) and flashed CWM v6.0.1.4 recovery.
Now none of the custom ROMs will boot, though they install correctly in recovery. From CyanogenMod to Carbon to AOSP, it just sits on the boot animation... I've let it sit for up to half an hour.
I'm wiping data and cache, though CWM says E:Can't mount /cache/recovery/pretty-much every subfolder, but that doesn't seem like a big deal...
So what am I doing wrong, here, any ideas? It doesn't matter if I install the ROMs and GAPPS from external SD, right?
I RSD'd to 96.15.66, the one where I can unlock the bootloader, and the only ROM I can get to boot is Clean Rom (basically stock with tweaks of course).
jimmyco2008 said:
Hey all,
I RSD'd the other day and then re-rooted and re-unlocked the bootloader (yes, I now know it stays unlocked) and flashed CWM v6.0.1.4 recovery.
Now none of the custom ROMs will boot, though they install correctly in recovery. From CyanogenMod to Carbon to AOSP, it just sits on the boot animation... I've let it sit for up to half an hour.
I'm wiping data and cache, though CWM says E:Can't mount /cache/recovery/pretty-much every subfolder, but that doesn't seem like a big deal...
So what am I doing wrong, here, any ideas? It doesn't matter if I install the ROMs and GAPPS from external SD, right?
I RSD'd to 96.15.66, the one where I can unlock the bootloader, and the only ROM I can get to boot is Clean Rom (basically stock with tweaks of course).
Click to expand...
Click to collapse
are you mounting system first? never used CWM on this device, but in TWRP, they install just fine. I believe that most devs use TWRP (although, it should not make a difference).
Thanks for the reply, actually I have two cwm recovery images, and after the RSD I flashed the "wrong" one... After flashing the other, I was able to flash and boot just fine.
jimmyco2008 said:
Thanks for the reply, actually I have two cwm recovery images, and after the RSD I flashed the "wrong" one... After flashing the other, I was able to flash and boot just fine.
Click to expand...
Click to collapse
Hi Im not sure if Im having this exact issue but I have been having problem since I used Utility 1.20 and re-rooted and re-unlocked my phone. Every ROM I have tried has random reboot issue. Can you tell me exactly how you did it correctly?
Also I didnt understand the two recovery image concept. I was having safe strap before and had issue with stock partition and was using slot1 partition as daily rom. And I couldnt flash any other ROM. So I had to go back to stock with Utility 1.2 and start over. Right now Im having liquidsmooth ROM with CWM recovery. Still having those reboots.
jcxmej said:
Hi Im not sure if Im having this exact issue but I have been having problem since I used Utility 1.20 and re-rooted and re-unlocked my phone. Every ROM I have tried has random reboot issue. Can you tell me exactly how you did it correctly?
Also I didnt understand the two recovery image concept. I was having safe strap before and had issue with stock partition and was using slot1 partition as daily rom. And I couldnt flash any other ROM. So I had to go back to stock with Utility 1.2 and start over. Right now Im having liquidsmooth ROM with CWM recovery. Still having those reboots.
Click to expand...
Click to collapse
are you sure you uninstalled SS via the app (and not via the android system)?
jco23 said:
are you sure you uninstalled SS via the app (and not via the android system)?
Click to expand...
Click to collapse
I dont think I have uninstalled safestrap with an app. I followed the instruction in this thread.
http://forum.xda-developers.com/showthread.php?t=2238341
This thread was started by me when I had problem with flashing ROMs in the stock slot using safestrap. Rikrong suggested I use Utility so that I go back to stock and start all over again. So I did. I guess thats how it should have been done?
jcxmej said:
I dont think I have uninstalled safestrap with an app. I followed the instruction in this thread.
http://forum.xda-developers.com/showthread.php?t=2238341
This thread was started by me when I had problem with flashing ROMs in the stock slot using safestrap. Rikrong suggested I use Utility so that I go back to stock and start all over again. So I did. I guess thats how it should have been done?
Click to expand...
Click to collapse
what I would suggest doing is going into SS via the app (not via recovery once the phone boots up) and click the uninstall button.
then, return to stock as rik suggested.... then root, then install TWRP, then you'll be able to slap on whatever ROM you like.
jco23 said:
what I would suggest doing is going into SS via the app (not via recovery once the phone boots up) and click the uninstall button.
then, return to stock as rik suggested.... then root, then install TWRP, then you'll be able to slap on whatever ROM you like.
Click to expand...
Click to collapse
Actually I did all that already just not by uninstalling SS. Now Im on CWM recovery. I was on SS one week back and then i followed the instructions by rik. I m having reboots ever since.
jcxmej said:
Actually I did all that already just not by uninstalling SS. Now Im on CWM recovery. I was on SS one week back and then i followed the instructions by rik. I m having reboots ever since.
Click to expand...
Click to collapse
I'm thinking the combination of SS and CWM could be the issue.... try to get a clean fresh start would be best....
jco23 said:
I'm thinking the combination of SS and CWM could be the issue.... try to get a clean fresh start would be best....
Click to expand...
Click to collapse
Thats interesting. I dont see safe strap or the rom i was using with SS (energy rom). So then how can i erase SS and get a fresh start? I was assuming Matts Utility already did that for me and I was on a fresh start.
jcxmej said:
Thats interesting. I dont see safe strap or the rom i was using with SS (energy rom). So then how can i erase SS and get a fresh start? I was assuming Matts Utility already did that for me and I was on a fresh start.
Click to expand...
Click to collapse
safestrap could still be there if uninstalled incorrectly. trying re-installing it, then uninstall it within its own app. this worked for me.
jco23 said:
safestrap could still be there if uninstalled incorrectly. trying re-installing it, then uninstall it within its own app. this worked for me.
Click to expand...
Click to collapse
Just installed SS and unnistalled it thru the app. I ll wait for any reboots before I reflash the ROM. Hope this works. (finger crossed)