i flashed deodexed gb last night and wanted to go back to the odexed rom today. it aborted the install when i flashed the original and now i cant flash either and it is stuck in a bootloop....ive tried wiping data a dozen times...i downloaded the rsdlite and the 2.3.2 but rsd is not recognizing my device. HELP!!!!
Nevermind . I didn't have my 64 bit drivers installed. Highly stressful
you should access the recovery menu : power button + x(keypad) hit the magniflying glass key or if it doesnt work hit both volume rockers.
and then choose wipe data/factory reset and cache too.
Then reboot
I have the same issue as you except that no matter how many times i wipe cache/data in stock recovery i'm still stuck in a bootloop.
I did install gb prerooted and everything went smooth whereas when i installed the deodexed over it i'm now stuck forever in bootloop despite how many times i access and clear cache/ data in stock recovery. Any ideas?
Related
Hello.
Just yesterday, I installed CM 7.1 on my Defy, which was on stock froyo. It started up normally, and was working perfectly, until I had to reboot it, in order to get the google apps, when it went into boot loop.
I've tried going into stock recovery and wiping the data/ factory reset and wiping the cache, but even then it's stuck on boot loop on the CM 7 logo. What should I do?
Ps. It's the Indian Defy, which is without Blur, if that makes any difference.
EDIT: Just got it to work, I flashed the stock Froyo SBF using RSD lite. I think my mistake was installing Clockworkmod on it, because it has it's own custom recovery. Can anyone tell me how to get into it?
Ya installing CWM on top of CM7 will screw up the pre-installed Custom recovery. While the phone is just starting to boot watch for a blue LED to flash at the top of the phone. Right when it flashes blue, press volume down. From here use your volume rocker to select recovery, use the power button to make your selection. Next choose custom recovery.
Thanks mate
Though sadly, after rebooting it, it keeps on showing the message - process com.android.phone has stopped working, and I get no network. What do I do?
Wipe data and install the zip again...
Sent from my MB525 using xda premium
after the new root method i had it rooted and then flashed a rom that didnt work. i sbfed back to the stock rom and now my phone is bootlooping. i have reinstalled the drivers multiple times and sbfed multiple times. i can not figure out what is wrong
Have you gone to recovery and wiped data?
I think that will likely be necessary. To get to stock recovery, hold down X while booting, and when the android logo and triangle come up, I think you hit both volume buttons at once to enter recovery.
use volume buttons to move, power to select.
Hope this helps
Yeah, as noted you need to wipe data/cache. SBFing only restores system files.
Wiping the data should do the trick
i ended up getting it to work. and it was the fact that i had to wipe the data.
I attempted to flash a Liquid Smooth rom yesterday. I rebooted into the bootloader, and chose recovery mode. I wiped all cache, then installed the zip. I followed this by installing the gapps zip immediately, which I think I shouldn't have done.
When I rebooted it, it was stuck on the liquid smooth screen for a while, I know this is normal, but when it sat there for an hour and fifteen minutes I knew something was wrong. If I hold down both volume keys and the power button I can reboot into the bootloader again, but when I now choose recovery mode, it gets stuck on the google load screen.
Can anybody help me out?
danlk2 said:
I attempted to flash a Liquid Smooth rom yesterday. I rebooted into the bootloader, and chose recovery mode. I wiped all cache, then installed the zip. I followed this by installing the gapps zip immediately, which I think I shouldn't have done.
When I rebooted it, it was stuck on the liquid smooth screen for a while, I know this is normal, but when it sat there for an hour and fifteen minutes I knew something was wrong. If I hold down both volume keys and the power button I can reboot into the bootloader again, but when I now choose recovery mode, it gets stuck on the google load screen.
Can anybody help me out?
Click to expand...
Click to collapse
Plug the N7 into your PC before you boot into the bootloader.
You were correct to flash gapps immediately after flashing the ROM. Maybe the ROM didn't flash correctly because you only wiped caches. If you are coming from a different ROM you will need to do a factory reset. If you didn't back up your apps and don't have a nandroid, then you might want to wipe caches, format system, and reflash the previous ROM and try to boot in and backup your apps. Might not work but worth a shot if you got stuck where you are now with no app backups.
irishrally said:
Plug the N7 into your PC before you boot into the bootloader.
You were correct to flash gapps immediately after flashing the ROM. Maybe the ROM didn't flash correctly because you only wiped caches. If you are coming from a different ROM you will need to do a factory reset. If you didn't back up your apps and don't have a nandroid, then you might want to wipe caches, format system, and reflash the previous ROM and try to boot in and backup your apps. Might not work but worth a shot if you got stuck where you are now with no app backups.
Click to expand...
Click to collapse
Wow, that didn't even cross my mind, I did this and I've got the rom up and running now. Thanks a lot.
This is another of those bricked defy thread.
Everything was fine. I was on 4.3 (a couple of nightlies earlier version) and just downloaded the latest one from Quarx.
I went to TWRP and wiped cache, dalvik, system and data.
Now, what was strange is that I got a prompt that you do not have root, do you want to have root or something. I swiped for that.
The next thing I remember is that the phone rebooted and stuck on the red M (with honey bee) and showing version 7.1-11 (which has always been the boot up screen for me for last two years).
So, I removed the battery, pressed volume down and then Power button. I was in the green android bot screen. Pressed volume up and down and got into some recovery screen.
There are options to wipe cache, wipe data/ factory reset, install update.zip and reboot. I have tried all of these. Unfortunately none of those help me in getting back to normal.
I have an SD card, where I can copy the latest 4.3 ROM from my computer and rename it to update.zip. Will that help?
s_u_n said:
This is another of those bricked defy thread.
Everything was fine. I was on 4.3 (a couple of nightlies earlier version) and just downloaded the latest one from Quarx.
I went to TWRP and wiped cache, dalvik, system and data.
Now, what was strange is that I got a prompt that you do not have root, do you want to have root or something. I swiped for that.
The next thing I remember is that the phone rebooted and stuck on the red M (with honey bee) and showing version 7.1-11 (which has always been the boot up screen for me for last two years).
So, I removed the battery, pressed volume down and then Power button. I was in the green android bot screen. Pressed volume up and down and got into some recovery screen.
There are options to wipe cache, wipe data/ factory reset, install update.zip and reboot. I have tried all of these. Unfortunately none of those help me in getting back to normal.
I have an SD card, where I can copy the latest 4.3 ROM from my computer and rename it to update.zip. Will that help?
Click to expand...
Click to collapse
You softbricked your phone by allowing it to reboot with an empty system partition. Flash SBF, root and you should be fine.
Sent from my MB526 using Tapatalk
hotdog125 said:
You softbricked your phone by allowing it to reboot with an empty system partition. Flash SBF, root and you should be fine.
Sent from my MB526 using Tapatalk
Click to expand...
Click to collapse
So, I assume I should not have deleted the system partition.
Anyway I flashed full sbf (JRDNEM_U3_3.4.3-36-1.7_CHINESE_SIGN_SIGNED_UCAJRDNEMARAB1B50AA03A.0R_PDS03C_USAJRDNFRYORTINT15_P002_A014_HWp3_Service1FF.sbf)
RSD lite was the main problem - did not detect the phone. I was pressing the volume down key to enter the boot loader menu, but I should have pressed the volume up key.
Finally realized my mistake and then corrected it.
Now I am on 4.1.2 (again, downloaded the wrong file) and hopefully the 4.3 (30 Oct) file won't take much time to download.
So, all is well.
I downloaded Imperium ROM from a thread on xda and installed it. I wiped data, wiped cache and dalvik and installed zip. Then I rebooted and it showed a downloading screen, after a little bit of research it's called download mode or ODIN mode. Now what's happening is whenever I try to reboot, it shows the S4 i9505 screen (i think it's called a splash screen, thats what someone called it) and freezes. After about 10-15 seconds, reboots into recovery. I've got CWM installed and I've ran out of ideas. The volume buttons are not being touched and for some reason recovery and download mode are always being booted into, never the OS.
I'm also new so anything I've done wrong, I'd love to know.
CWM recovery is outdated and should not be used anymore. Instead only use TWRP. Flash it trough Odin in the same way you flashed CWM.
You say that you only wiped data, cache and dalvik. You also HAVE to wipe /system. Otherwise the rom will probably not boot.
Lennyz1988 said:
CWM recovery is outdated and should not be used anymore. Instead only use TWRP. Flash it trough Odin in the same way you flashed CWM.
You say that you only wiped data, cache and dalvik. You also HAVE to wipe /system. Otherwise the rom will probably not boot.
Click to expand...
Click to collapse
Update I tried to install albe95's s6 port. I've noticed something and it's that both ended up with Statuc 7 or some word that started with "S" and had the number 7. Googled that and turns out it's bad. I formatted /System and installed the ROM, it worked!
I guess there was just no OS to boot into. Going to try installing Imperium now.
Status 7 errors can occur if the recovery is outdated. What recovery is on the phone?