Database Develop

*-a bootloop crash course and trouble shooting guide-*

WANT TO RUN HERO? READ THIS FIRST​
I understand that new people dont really know much about hero, and that is alright. They will learn to search and figure things out on their own, but i am a little frustrated with seeing this constantly in the hero ROM threads. " i am stuck in a bootloop, my phone stays on the htc screen"
THIS IS NOT A BOOTLOOP! A bootloop is when you see the hero with the little green android and then the HTC "flashing" logo. I will post a video of a bootloop in little bit, but in the meantime here are a few ways to fix a bootloop.
For a video of what a bootloop is, click on THIS IS A BOOTLOOP RIGHT BELOW THIS​THIS IS A BOOTLOOP​
1) wipe phone and wipe ext and reflash.
to wipe the phone boot into recovery and press alt+w or if running CMRecovery 1.3 or 1.4 you should be able to use the trackball and select the option that way. To wipe ext use these commands in either adb shell or recovery console... NOT IN TERMINAL!!!​
This is how I installed without any problems:
: rename to update.zip (if you are running cm1.4 recovery you can just place the zip in the root of sd)
: place in the root of sd card
: shut off device
: boot into recovery
: wipe
: go to console and hit enter (you can also use adb shell)
(enter)
# mount -o rw /dev/block/mmcblk0p2 /system/sd
# cd /system/sd
# rm -rf /system/sd/*
# reboot recovery
: now wipe again
: repair ext system
: flash
Enjoy!!
Click to expand...
Click to collapse
- Courtesy of Drizzy Drake Rogers
2) check to make sure you are running a PVT board. Cant remember right now if it is the three finger salute or power+camera. To do the three finger salute, boot holding the green button, menu, and the red button. At the top of the screen that shows up it will either say PVT or DVT.
3) redownload the .zip file for the rom you are trying to flash. Sometimes you may get a corrupt download or the transfer from computer to sd may go bad. A fresh download may help.
4) reformat your sd and recreate all partiitions usingparted in cyanogens 1.4 recovery image. It is one of the easiest ways to do things if you are not running linux.
5) and last but not least, if all else fails just go back to a stable cyan build or jf build.
Hope this helps everyone and cuts down on the questions junking up threads. I will bump this every now and then unless it gets stickied. Also expect edits to this for other questions that get asked. Before junking up threads try these options and SEARCH!!!
{
"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"
}
​
-helpful links-
CyanogenMod Stable
CyanogenRecovery Image 1.4
How to partition using gparted
THIS IS A QUICK TELL ALL TO GET DANGER SPL, RADIO, AND A STABLE ROM RUNNING
Happy flashing everyone!
WANT TO RUN HERO? READ THIS FIRST​

Fantastic Info. People need someone to spell out what's what.

Thank you it works. When I apply updates do you re-do all of this?

bump this. this will cut threads in half

sillyshyme said:
Thank you it works. When I apply updates do you re-do all of this?
Click to expand...
Click to collapse
not all updates, always read the changelog for a ROM. if you are simply UPDATING to a NEWER version of the SAME ROM, you MIGHT NOT have to do all this. this is mostly for when you get a bootloop. if you are changing hero roms, i would say yes, do everything you can, wipe, wipe ext, and what not. this will help about the bootloop.

I use Hero-V1.5 by Drizzy and it does not state in change-log.

sillyshyme said:
I use Hero-V1.5 by Drizzy and it does not state in change-log.
Click to expand...
Click to collapse
ok so what are you trying to do? go to a different Hero rom? if yes, then you need to wipe phone and ext, if updating from drizzy 1.4, i would say not to wipe, but if you get a bootloop wipe phone and try again.

please make this a sticky!!!! this a good info. hopefully if people search,it will help them out . great write up polosjr

palosjr said:
ok so what are you trying to do? go to a different Hero rom? if yes, then you need to wipe phone and ext, if updating from drizzy 1.4, i would say not to wipe, but if you get a bootloop wipe phone and try again.
Click to expand...
Click to collapse
Do this cause I just updated to drizzy's newest hero. I went from another hero Jac hero and I just did the update zip and got bootloop. I did whats on the top of this page and im running new rom so thanks

Ok, so I've followed all of these steps, except repairing the file extensions. When I try to do that I get an error in the recovery console. Does anyone know of anything else I can try?

rp1783 said:
Ok, so I've followed all of these steps, except repairing the file extensions. When I try to do that I get an error in the recovery console. Does anyone know of anything else I can try?
Click to expand...
Click to collapse
format your sdcard and then recreate your partitions

BSG - Boot script generator

Hi to all, i made a python program that help user to install/update the system.
With this program you can stop using the android boot menu, you can put all in the script.
What you can do with Boot Script Generator:
- install system
- update system
- backup system, data (with old and new method)
- apply updates
- clean data and system
- install apps located in /sdcard/andboot/apps
UPDATE 22 / 08 / 2010
New interface
Add new backup options
Add image size options
No more press d-pad or volume up
No more install procedure
cross platform and only python is needed
you can choose where install
NAND - SD - IMAGE both for system and nand
and what you want to do before boot
Little how-to
flash modded nbh or put initrd.gz in andboot for haret users
open python script in a terminal:
Code:
python bootscriptgenerator.py
then choose what you want to do, (i.e first install)
put install-seq.sh in your sd in andboot folder (with other files)
turn on the phone.
you don't need to touch any button just wait
As you can see you can change many things.
Update initrd and nbh on 4/7/10
If you are an "haret" user use this initrd.gz
Boot Script Generator (right click on link -> save as file)
Simple how-to run android from windows - Simple guide to flash android on Nand
{
"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"
}
It could be very useful if you want to speed up your system update

Reserved

Exciting, now you just need to make a android app as well to do this, that way you can set the options and hit reboot
Good job

I'm just working on it.
i think that next dzo nbh will include this changes

Any feedback?

Strange...
I download the latest version of python (2.7).
When I select any options in your tool, and want to create the .sh, impossible to find it !! I think he's not created...
I use it in a windows PC (Windows XP pro SP3).
I try with all options and it's the same thing. Sorry for that.
I hope you can find the problem.
Cheers.
l1q1d said:
Any feedback?
Click to expand...
Click to collapse

I make a simple modification, try with updated version

Source code...
I will try but when I want to download the link in first page, I've the source code...
Could you upload your tool ?
Cheers.
l1q1d said:
I make a simple modification, try with updated version
Click to expand...
Click to collapse

Re update link (extract with win rar/7-zip or other)

Hi l1q1d,
I've download this new version but same result : no product file...
I try to find it in my PC but no file...
I don't know how to help you
Thank you for your release of your tool key mapping
I'm on holiday now : go to Spain...
Cheers.
l1q1d said:
Re update link (extract with win rar/7-zip or other)
Click to expand...
Click to collapse

Hi,
I try to install Android on a Polaris and created an install script with your bootscript creator, but it always stops with the error:
'd: invalid number '512
where 512 is the size of the data image I have set in the creator gui.
Am I doing something wrong?
Thanks in advance
Abomb

Could you please submit a screen shot of your settings and the output file? Thanks

Here they are.
I forgot to mention that I commented out the data.img remove part, because that part gives me the error that the script file did end although a "then" was expected or something like this. But seeing as I do a fresh install and have no old data.img I thought it should not be a problem.

Any other error before?
Could you please test with 256?
Thank you

I tried two things, first with 265 MB and the disk.img remove code left in, the second time with the code commented out.
The first time I got a bootlog.txt that I attached here, the second time I got the error again
'd: invalid number '256
but sadly no bootlog.txt. Oh and no error before the invalid number one.

I update a new version of bootscriptgenerator
Try now

I tried with the new version, but exactly the same thing, tried first with disk.img delete code left in, second time commented that out.
Error messages were the same, first time bootlog was created, second time not.
I also double checked if I was using the new version of the creator.

Could you please make a test with this.
Please don't edit it (it could be a windows endline problem)

With the file from your last post it works!
Did I do something wrong then?
I didn't edit the .sh file for the first try, only when that didn't work I edited it.

The problem is the windows end line.
It isn't your fault is WINDOWS :-(
i update a new version, now i need someone to test it

Partitions not mounting @boot

Hey Guys,
first off i had this issue once before, but in that case i could restore a cwm backup from sd card and after sometime the problem fixed itself,
this time, i switched to bacon and i wanted to prepare the p880 for my sister to use, i downloaded zaiben, formatted my external sd card and put the rom on it, i rebooted to recovery wiped( i used the clean to install new rom in philz recovery if i remember correctly) everything and flashed the rom and exactly as last time, the flash seems to go way too fast and ofc i cant boot into android. now as i formatted my sd i have no backup to restore to. kdz flashing seems hopeless as well, as none of the tools recognize the phone when i put it in s/w upgrade mode,
for proof: i checked /system with aromafm and found it being empty after flashing a rom, i even tried extracting the rom zip on sd and moving the content from the zip to /system manually but after a recovery reboot, /system was empty again( only empty "bin" folder)
is somebody able to explain me why i have this issue and maybe how to fix it, or upload a clean cwm backup of whatever rom for me to use?
thx

Thanks for the help until now, really.......
In Further investigation i could find out that Roms ARE actually flashing properly, but /system and probably other partitions are not being mounted
At Boot or in recovery(manually mounting works Here) which is why aromafm reports an empty /system, after a manual Mount in either recovery itself of Aroma console i can See /system being filled with Rom files, now i will change the thread title accordingly, and now ASK: can i force /system to be mounted at Boot somehow? Someone pls answer this time

Okay this is ridicoulous.... why am i getting no help AT ALL?, thank you srsly.....
i investigated even further and suspected that something with fstab might be wrong, but fstab file looks fine to me:
Code:
/dev/block/platform/sdhci-tegra.3/by-name/CAC /cache ext4 rw
/dev/block/platform/sdhci-tegra.3/by-name/UDA /data ext4 rw
/dev/block/platform/sdhci-tegra.3/by-name/APP /system ext4 rw
if someone bothers to answer: what do you think?
pls help........

bump
please help

What recovery are you using? Are you sure your partitions aren't formatted to F2FS? (which would explain why the (F2FS-) recovery can mount the partitions but the system cannot as it expects an ext4 formatted partition rather than a F2FS formatted one)

i'm using an older version of philz touch (i dont think it has f2fs functionality), as i had weird flickering issues with latest philz,
using cat /proc/mounts shows ext4 for /system and other partitions

~MaX~ said:
i'm using an older version of philz touch (i dont think it has f2fs functionality), as i had weird flickering issues with latest philz,
using cat /proc/mounts shows ext4 for /system and other partitions
Click to expand...
Click to collapse
Did you try to boot another ROM (Slim, nameless, whatever) or using another kernel?

laufersteppenwolf said:
Did you try to boot another ROM (Slim, nameless, whatever) or using another kernel?
Click to expand...
Click to collapse
i tried latest aospa,zaiben, pa 3.99 and iodak kernel (stock or cm according to the kind of rom i tried to boot)
thank you for helping btw, i appreciate it
EDIT: I attached an image of output of cat /proc/mounts (sorry for the size)
{
"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"
}

~MaX~ said:
i tried latest aospa,zaiben, pa 3.99 and iodak kernel (stock or cm according to the kind of rom i tried to boot)
thank you for helping btw, i appreciate it
EDIT: I attached an image of output of cat /proc/mounts (sorry for the size)
Click to expand...
Click to collapse
hmm, can you please grab me a kmsg? (from when it is stuck)

laufersteppenwolf said:
hmm, can you please grab me a kmsg? (from when it is stuck)
Click to expand...
Click to collapse
could you give me a quick how to on using adb in recovery from pc? i put the phone in sideload mode and tried "adb shell dmesg" but the output just was "error close" and using the command in aromafm terminal gave me an endless stream of log
(Also currently need to charge the phone a bit)
EDIT: NVM kmesg incoming....
okay next question, how can i dump the output into a file and how do i know where it hangs? time in recovery is not correct anymore(i set it once but after reboot it was wrong again, also in kmesg the time again seems to be different)

does that part help? i think it has to do with boot

~MaX~ said:
does that part help? i think it has to do with boot
Click to expand...
Click to collapse
nah, I need the entire log
here's how you get it:
boot the system until it is stuck
hard reboot into recovery (don't enter sideload)
then run the following commands:
Code:
adb shell cat /proc/last_kmsg > /sdcard/last_kmsg
adb pull /sdcard/last_kmsg C:\whatever\path\you\like\last_kmsg
then post the file via pastie.com or any other online paste site

laufersteppenwolf said:
nah, I need the entire log
here's how you get it:
boot the system until it is stuck
hard reboot into recovery (don't enter sideload)
then run the following commands:
Code:
adb shell cat /proc/last_kmsg > /sdcard/last_kmsg
adb pull /sdcard/last_kmsg C:\whatever\path\you\like\last_kmsg
then post the file via pastie.com or any other online paste site
Click to expand...
Click to collapse
no such file or directory
by hard reboot you mean vol - and hold power without pulling battery after hang?

~MaX~ said:
no such file or directory
by hard reboot you mean vol - and hold power without pulling battery after hang?
Click to expand...
Click to collapse
Yes, I meant that. But no kernel log seems like your boot partition/kernel is messed up... I guess you'll have to find a way to restore your entire phone via LG tools, I can't see any other way around that..

laufersteppenwolf said:
Yes, I meant that. But no kernel log seems like your boot partition/kernel is messed up... I guess you'll have to find a way to restore your entire phone via LG tools, I can't see any other way around that..
Click to expand...
Click to collapse
two last things then: when i hold vol - and then hold power until i reboot, recovery does not start, it tries to boot android again (has always been like that)
and also: all roms except cm official show no bootanimation before hang, cm does

~MaX~ said:
two last things then: when i hold vol - and then hold power until i reboot, recovery does not start, it tries to boot android again (has always been like that)
and also: all roms except cm official show no bootanimation before hang, cm does
Click to expand...
Click to collapse
1) yeah, I know, easiest way to fix that is to simply pull the battery and then boot into recovery
2) if the bootanimation shows up, it means the kernel as well as the ramdisk have booted properly. So in this case, you should be able to grab a last_kmsg as well as a logcat

hi
today I installed that application " LG-Optimus-4XHD-Recovery-v1.0.apk "
I have selected ClockworkMod Custom Recovery.
It showed that Operation is successful.
than i clicked on "Boot Recovery" to restart my Phone in CloclworkMod Custom Recovery.
since then I am getting only Starting animation. (LG LOGO).
nothing happens.
My battery was full when i performed this procedure
any help please

Bricked device

Hi guys
I am new to posting here but an avid viewer, now recently I had a problem with my device where the battery died and the device no longer boots and I cannot flash a new rom or recovery, the same as these two posts:
http://forum.xda-developers.com/moto-g-2014/help/device-bricked-0-battery-left-t3085322
http://forum.xda-developers.com/moto-g-2014/help/moto-g-2014-dead-t3072930
Now unfortunately unlike those two I am unable to send my device to Motorola for repairs as it was bought in another country, now I have tried all the options available to me, even all those mentioned in the two posts, including Wipe /data /system /cache in twrp & fastboot, but /data remains unchanged. I was running Blisspop V3.2 before the issue and no matter what I do or how I flash it keeps showing the blisspop boot logo & gets stuck there.
After a few attempts i switched to adb, and in adb I realised that the /data partition is set to "read only"
{
"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"
}
And as you can see chmod cannot change the permissions for the /data partition.
Now my question is this does anyone out there have any clue as how reset the data partitions read-write permissions without using chmod ?
FYI this device is a paper weight at the moment and I would like to see if I can do anything about that and maybe learn something on the way.

Leader0fr4tz said:
Hi guys
I am new to posting here but an avid viewer, now recently I had a problem with my device where the battery died and the device no longer boots and I cannot flash a new rom or recovery, the same as these two posts:
http://forum.xda-developers.com/moto-g-2014/help/device-bricked-0-battery-left-t3085322
http://forum.xda-developers.com/moto-g-2014/help/moto-g-2014-dead-t3072930
Now unfortunately unlike those two I am unable to send my device to Motorola for repairs as it was bought in another country, now I have tried all the options available to me, even all those mentioned in the two posts, including Wipe /data /system /cache in twrp & fastboot, but /data remains unchanged. I was running Blisspop V3.2 before the issue and no matter what I do or how I flash it keeps showing the blisspop boot logo & gets stuck there.
After a few attempts i switched to adb, and in adb I realised that the /data partition is set to "read only"
And as you can see chmod cannot change the permissions for the /data partition.
Now my question is this does anyone out there have any clue as how reset the data partitions read-write permissions without using chmod ?
FYI this device is a paper weight at the moment and I would like to see if I can do anything about that and maybe learn something on the way.
Click to expand...
Click to collapse
adb root; adb remount

Does your phone get recognized by your pc?
Mine went black a few days ago and i cant do anything.

LuK1337 said:
adb root; adb remount
Click to expand...
Click to collapse
Hi LuK1337
Firstly thanks for the help.
adb root returns a message saying adb already has root access.
asb remount only remounts the /system partition (unless im using it incorrectly).
So far I have well and truly wiped every partition of this device excluding the /data partition which returns a message saying partition is read-only

So I have now officially proved that this is a hardware issue at least for me, look here for my findings:
http://forum.xda-developers.com/moto-g-2014/help/battery-drained-encrypted-device-pinned-t3079871/page2
Short version I've used every available software method including 'Fastboot Erase all' which has no effect.
So would anyone be able to help build a usb jig or finding a hardware way to fix this ? my device has been opened so I would be able to provide high res pictures of the motherboard to anyone who needs it, will also upload when my 10 post count has been reached

Solved: Dead battery stuck in fastboot mode unable to flash any image. Works for all.
Same thing happened to me.
Nothing to do with the hardware.
Steps to Follow:
1) Open fastboot mode in your phone.
2)Connect to your pc and open cmd in platform-tools folder.
3)Place the twrp.img file in platform tools.
4)In cmd, type : fastboot boot twrp.img (Very Important Command)
Now your phone will boot to recovery mode i.e. TWRP and the connect it to charger. It will charge slowly.
Now you can flash anything using ADB Sideload.
(If found helpful, hit the thanks button )

Bricked phone, what can I do?

Hi there. My cousin's phone stopped working some weeks ago. He tried to wipe everything via TWRP and installing different ROMs but no ROM seems to work. Now, when he does a complete wipe, he gets the error "E:Unable to wipe '/sdcard1' -- unknown file system 'auto'" and "Unable to mount storage". Also, now everytime he tries to copy a ROM to the TWRP folder (the only folder which appears on his MacBook or his friend's PC) it stops at 16k and he can't copy it.
What can he do to fix this? Nothing seems to work and a guy at a service center said it was a disk error and that there was no hope for the phone.
Here's a screenshot of it:
{
"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"
}
Thanks in advance!

Uhm... Why don't you remove the faulty micro SD from the phone?
This doesn't look like a bricked phone at all - "storage" and "sdcard1" refer to external storage.
Remove the phones's cover and remove the SD card (do NOT go beyond step 2, FFS). Then you can try to run some diagnostics or format it on your working phone, tablet, MAC or PC or you can buy a new one - they are quite cheap.
Then add a proper ROM (and proper GApps) on the card and stick it back in. Moto G 2014 comes in two variants - make sure your cousin's device is an actual Titan - chances are it is a Thea, if you're in Europe; that's why the TWRP doesn't want to install it. Choose one from here.
Remember you have to delete everything on the internal card through the recovery utility I see in your image before flashing a new ROM - do NOT wipe the SD Card; it stores your installation files: the properly chosen ROM and GApps you add after you format it through a different device.
If it works, make sure you do NOT format it as adopted/internal storage when/if asked by the installation wizard at first run, once the flashing is complete. This is probably why the phone got in this state in the first place.

Now I have it in my hands, this is the situation:
- Both on my PC and in TWRP it says I have 766MB free of a total of 5637MB when I don't have anything stored there and when I try to copy anything onto it it just gets stuck at 0% forever
- Tried repairing and changing file system: apparently Data is F2FS and the rest is EXT4 but everytime I try to repair or change any partition it says it worked but then it's all the same (still not working, with the file system it had before)
- Tried updating to the newest TWRP (via fastboot and also TWRP) - like what happened above, it says "done" but then it shows the TWRP version number I had before (3.0.2-3 and not the 3.1.1-0 I tried to install)
- He had no SD card inside but apparently had already tried to install a ROM with it. I put a 4GB one inside with the lastest LineageOS and all I get is "E1001: Failed to update system image unconditionally... / E:unknown command [log] / Updater process ended with ERROR: 7 / "Error installing zip file '/sdcard1/lineage.zip'
- Also the error "Unable to mount storage" is constant
I am running out of options here, don't really know what else I can do...any help? Thanks in advance!

Framboesa96 said:
Now I have it in my hands, this is the situation:
- Both on my PC and in TWRP it says I have 766MB free of a total of 5637MB when I don't have anything stored there and when I try to copy anything onto it it just gets stuck at 0% forever
- Tried repairing and changing file system: apparently Data is F2FS and the rest is EXT4 but everytime I try to repair or change any partition it says it worked but then it's all the same (still not working, with the file system it had before)
- Tried updating to the newest TWRP (via fastboot and also TWRP) - like what happened above, it says "done" but then it shows the TWRP version number I had before (3.0.2-3 and not the 3.1.1-0 I tried to install)
- He had no SD card inside but apparently had already tried to install a ROM with it. I put a 4GB one inside with the lastest LineageOS and all I get is "E1001: Failed to update system image unconditionally... / E:unknown command [log] / Updater process ended with ERROR: 7 / "Error installing zip file '/sdcard1/lineage.zip'
- Also the error "Unable to mount storage" is constant
I am running out of options here, don't really know what else I can do...any help? Thanks in advance!
Click to expand...
Click to collapse
Why don't you try reflashing the stock rom..Once I encountered a similar problem and reflashing the stock rom solved it