Been having a lot of trouble flashing new roms. Curently running tazz froyo v1.0. Have been able to root, flash many different types of roms (2.1, froyo etc)
But lately been wanting to try out Nonsensikal v4.6 but for some reason cannot get it to load. It'll either get stuck onthe white screen or if it does make it past the boot freezes during the boot animation and will remain stuck for a long time. Have let it go for 30-40 minutes. Batt pull, both wipes reflash and same thing.
So it has to be corrupted downloads. Tried on different computers, same results. Reformatted my card (was already no partitions, fat32 for froyo).
I would like to figure this out as i really want to try nonsensikal ( ran v 3.4 and loved it)
Any ideas? Battery is always fully charged when flashing. Sd card is good.
Maybe it's a computer issue?
Appreciate any responses.
Thannks
Stephen,
Thanks for the input. No setcpu for me anymore. Its only phone but never activated. I can flash other roms. It's just certain ones won't finish booting.
I'll have to verify the md5s and focus on the corrupted download issue.
Thanks again.
ppbb = Jp50 ?
I would try wiping and flashing the ROM, and then booting it for the first time without your SD card being present. (Note this is not the same thing as attempting to boot a ROM without an SD card, where it has already been through several failed bootloops and battery pulls).
It is not possible to flash a corrupted ROM - unless the definition of "corrupted" is that the dev screwed the pooch.
If you reply back, let me know if you have ADB and the USB drivers working on your PC (and if you are familiar with using the command line).
bftb0
You did wipe. My mistake.
bftb0 said:
ppbb = Jp50 ?
I would try wiping and flashing the ROM, and then booting it for the first time without your SD card being present. (Note this is not the same thing as attempting to boot a ROM without an SD card, where it has already been through several failed bootloops and battery pulls).
It is not possible to flash a corrupted ROM - unless the definition of "corrupted" is that the dev screwed the pooch.
If you reply back, let me know if you have ADB and the USB drivers working on your PC (and if you are familiar with using the command line).
bftb0
Click to expand...
Click to collapse
yes that is me. I do have adb and usb drivers. I can get around and do some very basic stuff thru command prompt sdk. Would love to get this up and running.
Thank you so much. I look forward to hearing from you.
Jp50 said:
yes that is me. I do have adb and usb drivers. I can get around and do some very basic stuff thru command prompt sdk. Would love to get this up and running.
Thank you so much. I look forward to hearing from you.
Click to expand...
Click to collapse
Let me know if you have tried booting it without the SD card in the phone (the first time you try booting it). If you already said you did that and I missed it, then my apologies.
Some dev ROMs (not all of them) have "USB debugging" enabled in their boot scripts (some don't), so you can sometimes detect what the problem is using logcat. Maybe you do the "wipe-flash-boot without SD card" experiment and at the same time do this:
- Turn phone off
- Plug it in to the PC and bring up a command window
- in the PC, enter the command
Code:
adb wait-for-device logcat > logcat_boot.txt
The command prompt will not return - it will just sit there, waiting for the phone to start up. So, then:
- boot the phone.
Let the phone sit, even if you think it is going in to a boot loop. The "adb" command will also just sit there until you interrupt it. Wait for 10 minutes if necessary.
Hit Ctrl-C in the PC Command window. You should see the command prompt return.
If the phone booted successfully, then you can just delete the "logcat_boot.txt" file.
If the "logcat_boot.txt" file is zero length, that means that the dev did not enable the "adbd" service on bootup, so this particular technique is of no value.
If the phone went into a bootloop and you have a big "logcat_boot.txt" file, I will probably suggest you post it up to a pastebin somewhere (e.g. http://pastebin.com/ ) so we can look at it.
bftb0
ran the logcat test and it returned nothing. phone still won't boot nonsensikal. just freezes on the white screen. battery pull, reboot now its in boot loop city.
i think i've wasted enough time on this rom. I'm running cyanogen Tazz v2.0 and I was able to flash it over v 1.0 with no issues (other than the camera).
I guess nonsensikal rom doesn't like my phone. the dev was a lot of help, but i think the issue is my phone is just ****ed. I can't overclock anything over 604 without it freezing.
Time to move on and get back to having a real life and not obsessing over a phones interface. tazz's rom is more than good enough and I just have to move on. The amount of time I wasted on this is just silly. This phone took over my life and I have to lick my wounds and admit defeat.
thanks for all your help everyone. not all phones are created equal.
Guys i really need your feedback and advice on this situation. Okay I was trying to install the Rom CNA. 3.5.0 (JB). But my battery was low (stupid me) and i install the ROM with no problem, but when the phone rebooted it went to the Motorola logo and i was stuck. I tried the volume down button which is the NV recovery but my phone turned off due the low battery i guess. And it seems my option could be fast boot but i don't know how to operate it. My question is that can i get out of this situation with a pre-charged battery, or a software from the internet. I really need your advice on this one?
swaggerdagger said:
Guys i really need your feedback and advice on this situation. Okay I was trying to install the Rom CNA. 3.5.0 (JB). But my battery was low (stupid me) and i install the ROM with no problem, but when the phone rebooted it went to the Motorola logo and i was stuck. I tried the volume down button which is the NV recovery but my phone turned off due the low battery i guess. And it seems my option could be fast boot but i don't know how to operate it. My question is that can i get out of this situation with a pre-charged battery, or a software from the internet. I really need your advice on this one?
Click to expand...
Click to collapse
Yes, you'll need a charged battery.
After you get one, enter the recovery and do all the necessary wipes (cache, dalvik, data, etc.) and reboot your phone
If it doesn't work, you may reapply the rom via recovery, avoid applying SBFs, as they may brick your phone.
Can't you just charge the battery while the phone is off?
I know I can on mine, but I'm not sure what's needed for that (like, do you need a bootable system?).
ravilov said:
Can't you just charge the battery while the phone is off?
I know I can on mine, but I'm not sure what's needed for that (like, do you need a bootable system?).
Click to expand...
Click to collapse
Or charge the battery by using EBC...
Sent from my MB860 using XDA Premium HD app
bimasakti85 said:
Or charge the battery by using EBC...
Sent from my MB860 using XDA Premium HD app
Click to expand...
Click to collapse
What is EBC? and how do i use it ?
just hook up the phone in fastboot and issue this command "fastboot -w" then reboot and you should be good
swaggerdagger said:
What is EBC? and how do i use it ?
Click to expand...
Click to collapse
External Battery Charger.
android-DEP said:
just hook up the phone in fastboot and issue this command "fastboot -w" then reboot and you should be good
Click to expand...
Click to collapse
Any steps or guidelines you can give me to get fastboot to reboot my phone to normal ?
which rom did you flash last on your phone? Was it gingerbread or CM7 based or CM9 based?
Depending on your answer to that question, you can try a few things to restore your phone using fastboot.
If it was let's say some CM7 based rom, you can locate a stock CM7 kernel and download it. Extract the zip file to pull out the "boot.img" file and put it inside the same folder you're running fastboot.exe from.
Once that's done, reboot your phone into fastboot mode, and connect it to your PC via usb cable and real quick just type "fastboot devices", that command just shows you which devices it's currently connected to via the fastboot interface and you should see your phone listed with it's serial number showing which tells you that you can continue the procedure..
then do a wipe of any data which might interfere with the new kernel by typing "fastboot -w", don't worry, you won't lose any personal files like pictures or contacts..
after thats done then type out "fastboot flash boot boot.img" which will flash the new kernel onto your phone.. phone's not booting past the initial Dual-Core screen can sometimes be attributed to a bad flash of a rom, kernel not properly being written to the device in cases where the updater script couldn't mount a partition to extract the boot.img to before writing the raw data to your device. The updater-script which is just like a batch file, it just goes down line by line running commands and does not halt on errors to let the user know that something failed. So if something failed during the flash process and you didn't successfully flash some parts of the rom normally, it could still finish the installation and all you'll get it Installation Completed type message where you think it's all good but in reality some parts of the installation didn't complete.
Perhaps the rom didn't properly perform the necessary prep work of wiping cache and dalvik cache. Not exactly always an issue as it depends on the circumstances of what you're installing and what you had installed prior.
I've had a few roms here and there that put me in your shoes, the solutions I've always found to work was to first try something basic like wiping the cache of the device and reboot. If that didn't work, then this is where you could try flashing a new kernel.
Since you did the proper wipe of data, you can make sure the kernel gets installed properly as you isolate the installation from the entire process.
It takes 3-5 seconds anyway for fastboot to flash files anyway so theres no harm done anyway so long as you get the proper compatible files for your setup. Reboot the phone afterwards and give that a shot.
Unless you tried to flash a PDroid patch on your phone, which requires you to have a working rom installation to begin with from which you pull files to patch so you can flash them over the current installation, you should be able to boot.
If you still cannot boot, then reboot into recovery and open up the ADB interface in command prompt and run this command
Code:
adb logcat > "c:\logcat_dump.txt"
and just kick back for a few minutes while it dumps the entire log into the root of your drive in a text file named logcat_dump.txt... press the Windows symbal key(its between the CTRL & ALT buttons on the left side of the keyboard), while holding that press the letter R to bring up a run window box where you type in "%SystemDrive%\logcat_dump.txt" and hit enter... post the log here and you can get more feedback on where the issue is
android-DEP said:
which rom did you flash last on your phone? Was it gingerbread or CM7 based or CM9 based?
Depending on your answer to that question, you can try a few things to restore your phone using fastboot.
If it was let's say some CM7 based rom, you can locate a stock CM7 kernel and download it. Extract the zip file to pull out the "boot.img" file and put it inside the same folder you're running fastboot.exe from.
Once that's done, reboot your phone into fastboot mode, and connect it to your PC via usb cable and real quick just type "fastboot devices", that command just shows you which devices it's currently connected to via the fastboot interface and you should see your phone listed with it's serial number showing which tells you that you can continue the procedure..
then do a wipe of any data which might interfere with the new kernel by typing "fastboot -w", don't worry, you won't lose any personal files like pictures or contacts..
after thats done then type out "fastboot flash boot boot.img" which will flash the new kernel onto your phone.. phone's not booting past the initial Dual-Core screen can sometimes be attributed to a bad flash of a rom, kernel not properly being written to the device in cases where the updater script couldn't mount a partition to extract the boot.img to before writing the raw data to your device. The updater-script which is just like a batch file, it just goes down line by line running commands and does not halt on errors to let the user know that something failed. So if something failed during the flash process and you didn't successfully flash some parts of the rom normally, it could still finish the installation and all you'll get it Installation Completed type message where you think it's all good but in reality some parts of the installation didn't complete.
Perhaps the rom didn't properly perform the necessary prep work of wiping cache and dalvik cache. Not exactly always an issue as it depends on the circumstances of what you're installing and what you had installed prior.
I've had a few roms here and there that put me in your shoes, the solutions I've always found to work was to first try something basic like wiping the cache of the device and reboot. If that didn't work, then this is where you could try flashing a new kernel.
Since you did the proper wipe of data, you can make sure the kernel gets installed properly as you isolate the installation from the entire process.
It takes 3-5 seconds anyway for fastboot to flash files anyway so theres no harm done anyway so long as you get the proper compatible files for your setup. Reboot the phone afterwards and give that a shot.
Unless you tried to flash a PDroid patch on your phone, which requires you to have a working rom installation to begin with from which you pull files to patch so you can flash them over the current installation, you should be able to boot.
If you still cannot boot, then reboot into recovery and open up the ADB interface in command prompt and run this command
Code:
adb logcat > "c:\logcat_dump.txt"
and just kick back for a few minutes while it dumps the entire log into the root of your drive in a text file named logcat_dump.txt... press the Windows symbal key(its between the CTRL & ALT buttons on the left side of the keyboard), while holding that press the letter R to bring up a run window box where you type in "%SystemDrive%\logcat_dump.txt" and hit enter... post the log here and you can get more feedback on where the issue is
Click to expand...
Click to collapse
My phone keeps turning off, it doesn't even reach the logo and it wouldn't even hold a charge...... .Its best i order a extended battery with an external charger?
No, no need to order a battery, there's nothing wrong with your current battery.
This was exactly the same way I first soft-bricked my first atrix long long ago. The battery would not charge no matter what I did and I could not flash anything onto the phone because the charge was too low and kept getting lower. It eventually fell to the point where it was like less than 5% charge left on the phone.
For some stupid reason, the Atrix does not recharge the battery when you do not have a proper working installation currently on the phone, like a corrupt install where something didn't do what it was supposed to do.
The catch is that once this happens and you have a corrupt install of whatever rom half-ass installed that doesn't boot, perhaps maybe even if the rom improperly wiped out the recovery so you can't boot into recovery, the phone will not recharge itself anymore. This is one MAJOR reason why you should always flash your phone with a FULL battery charge, not because it's cool to have a full battery icon on the statusbar, but when the fit hits the shan and things go wrong, you have some spare life left to be able to to try flashing something else to recovery your phone with before it drains too low.
You have 2 options at this point, you basically have to find a full charged up battery to use for about 10 minutes. Reason I say you have to find a battery and not just say find someone with an Atrix is because you can also use the battery from the Motorola Droid.
This was what I did once I finally found someone near by with a Droid, I borrowed their battery for 10 minutes to restore my phone and it worked like a charm.
Atrix battery model is BH6X and the Droid battery is BH5X which is the same size but has a weaker mAh. Long term I dont know how safe it is to continually use that battery but for something like restoring your phone, using that battery is perfectly ok unless you have a friend who has an Atrix also. Have him charge his battery up to full and then swap batteries with him so he can continue charging while being able to use his phone and you will have a full charge which buys you enough time to recover your phone before you drain the battery from flashing.
This was the exact reason I purchased this charger & battery just in case of just in case
Only thing is that this generic battery is 1800mAh 6.7Wh and the factory battery is 1880mAh 7.0/7.1 Wh but I never had any issues with the generic battery.
You can optionally get this nice Dual Dock Cradle + 3 batteries
Here's another option, 2000mAh battery with external charger
The way I solved my issue was to download a fresh copy of a 2.3.4 SBF file and a good copy of RSD Lite. Once I popped in the battery into my phone, I hooked it up to RSD Lite and just let it do it's job to restore everything back to square 1. Locked bootloader, not rooted, deodexed or zipaligned. But back then these things didn't matter as long as I was able to recover my phone and not have to pay $125 to send it to AT&T insurance dept. just to get a refurbished one in exchange.
I truly believe this is one situation which does earn the necessary required use of an SBF file to be flashed with RSD Lite. There's risks involved with flashing SBF files and so it's best to avoid them altogether but there are only a handful of certain situations which do call for their use such as recovering\restoring your device from an unusable state.
Definitely do some more reading about the matter and what your options are here. You're going to have to keep an eye out for the pros vs. the cons of using certain methods to recover a soft bricked phone. I'm sure last thing you want your phone to be is a hat weight right? lol, but do yourself a favor and read up more about this before you decide your course of action. Don't just start flashing anything that pops up that seems like it will work
android-DEP said:
You have 2 options at this point, you basically have to find a full charged up battery to use for about 10 minutes. Reason I say you have to find a battery and not just say find someone with an Atrix is because you can also use the battery from the Motorola Droid.
Click to expand...
Click to collapse
You mean Droid X, right? The Motorola Droid use the BP6X, as the Motorola Milestone / Milestone 2, and it's really small when compared to the BH6X.
Yea thats what i meant, can't keep up with these incredible nexus droid htc photons prophilactic splendifures flux-capacitator names they went overboard with on naming android phones in the last 2 years. It's ridiculous when you have to think back to which model some phone was last year that you might've had but not sure because it looks like 10 other phones and the model names all sound like comic book super heros or something.
Specially a few years ago when I used to repair the hardware internally on iphones, blackberry & android smart phones. Sometimes I'd be so sure without a doubt in my mind about getting the right parts for phones and then later realize it's in the same family but a diff model #. Good thing with Android they atleast make parts to fit exactly or not fit at all. Like a safety net coupled with common sense, if it looks identical and does fit, then it'll work, otherwise its not compatible. Just like these 2 batteries, so regardless if it's Droid X or Droid DeathShovel Excalibur Pluto Carbide Titanium XIII Deluxe, the model number of the parts is the most important thing to look for
{
"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"
}
The spare charger and battery I bought actually never needed to be used for a situation like that again as after the first time it happens to you, you learn a lot of info on how to not land in the same spot again in the future. It is how ever useful if you like to flash roms a lot and sample different ones frequently. it's nice to have a battery in the phone you can use while having another one on charger to swap over once your current battery drains. This way you never need to be plugged into a charger via usb to recharge anymore.
---------- Post added at 09:50 PM ---------- Previous post was at 09:37 PM ----------
I just stumbled upon this online, this is a must have for anybody with an atrix and it's only $20 free shipping HD motorola dock with remote control
Hi all
I have a LG Joy (h220) and would like it to power on automatically when the charger is plugged in.
At the moment it turns on and shows the battery charging icon. I have done some research and have read that there is a file in the /system/bin folder that contains the boot animation. I am not able to find anything, the closest is charger_monitor but it contains gibberish rather than some commands! It seems to manage charge current.
I did try to find a model specific forum but this model was not listed.
I have root, but no idea where to go next. Any help would be much appreciated.
Any feedback would be appreciated.
Hi,
I know that this issue have been discussed before, but I would like to know if there is any news about a solution to the problem.
I have two mobile phones (Samsung S6 edge & HTC one M7 - both rooted), that I have tried to get it to work on, without any luck
On the Samsung I have tried to edit the "\system\bin\lpm" file with this code: "#!/system/bin/sh" + "/system/bin/reboot" - That made the phone unstable and sometimes lock-up
On the HTC, I have tried to run the "Fastboot oem off-mode-charge 0" command, but this model do not know that command
If I just could get one of the phones to power-up when charged, it wouldbe great :laugh:
Can someone please help with a solotion to the problem :fingers-crossed:
Many regards
MrNisse
Hello,
So I tried to flash a global rom into my chinese GT 2 pro which didn't actually work, and in the process of fixing this and having to go to work etc the phone battery died and now that I have all the resources to "unbrick" the phone I can't flash anything because of the low battery and I can't charge the phone because it won't even load the recovery mode. I am trying the .bat file that I found in this forum where it charges rebooting the fastboot mode but it's charging 2mv every 3.5 minutes and if my maths are correct, this would take me 2 months to charge to 30% in order to flash anything which obviously is not viable . And I've seen suggestions about splitting a cable and charging the battery with the wires directly but I can't find any information on how to actually do this. Would this work at all? Or is there anything I can do? Please give me some hope! Thank you all in advance
boot into TWRP from fastboot and let it charge
I have tried this but still not working. It's says OKAY after "sending boot" but nothing happens, just a black screen. Although I'm not completely sure that I'm doing this right or even using the right image. Would you be able to guide me with this a bit further please?
try this to disable start-up on usb
Code:
fastboot oem off-mode-charge 1
fastboot oem enable-charger-screen
Thank you, I will try this tomorrow and update either way in case it helps someone else (because hopefully it does work! )
Hello all, so those codes didn't work. I got a guy to try and unbrick it who in the attempt to do so he actually hard bricked it I had given up at this point but he didn't. He wanted to try a test point which involves opening the back of the phone, which actually worked! (Apparently we tried to flash the wrong ofp) anyway, in the process of opening the back case I damaged the power flex (and the actual back case too, but I wasn't too worried about that as I thought I had no phone anyway).... I would attempt to replace both but I can't find where to buy replacements. If I try to google it everything I find is for realme gt neo. Any ideas where I can find a new power flex and back cover? Thank you!