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

CWM Recovery v.5.0.2.6 in English

this i got from Wildfire S section.
IT CAN BE PUT INTO SALSA, AND IT WORKS.
DWYOR
save the recovery.img and flash_image in the root of your adb folder.
Code:
adb reboot bootloader
make it fastboot usb
Code:
fasboot flash recovery recovery.img
from the hboot menu, go to recovery.
{
"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"
}
Please say thanks if you are fine with it

kanded said:
this i got from Wildfire S section.
IT CAN BE PUT INTO SALSA, AND IT WORKS.
DWYOR
save the recovery.img and flash_image in the root of your sdcard.
Code:
su
Code:
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
Code:
cp /sdcard/flash_image /system/bin
Code:
su
Code:
flash_image recovery /sdcard/recovery.img
get into recovery by typing : adb shell reboot recovery
Click to expand...
Click to collapse
u tried? get some screenshots up lol is it fully functional with backups enabled?

how did you run these commands? what did you use?

these command should be done via adb debug.
open it, and do the same.
http://www.freeimagehosting.net/umo22

keeps failing, heres a screen shot of what its doing.
any ideas?
goes to bootloader then just hangs

man, check your battery, minimum 50% power.

kanded said:
man, check your battery, minimum 50% power.
Click to expand...
Click to collapse
it was around 62% but ill charge it up fully and try again.
..........................................Edited.........................................................
OK charged it to 83% tried it again, still hanging for well over 20mins at that point.
somethings still not right.....

i edit the post. check this, i bet you wont get into probs again. let me know.

nope still not working! you missed a t from fasboot lol, but no, tried everything now and still nothing.

Tried from my other computer and still no luck.
sent from my custom HTC Salsa.

it works man, friends did it, why you still not work ?

Have no idea mate, puzzles me to be honest.
sent from my custom HTC Salsa.

let me know your probs, mate,

It stops in exactly same place as before, I've done everything stated. And it just won't nudge lol, even used a different computer with sdk installed,and still does it then.
For now ill leave it be, till I can figure it out.
I've flashed back to rom before and using that now as market is stable there.
What's the idea with this internal memory then? As this rom has very little space left lol and could do with the sapce available really
sent from my custom HTC Salsa.

so, do you have cwm ? if you have its fine. i still wonder wht exactly your problem is. if you got market problem, you just go back to your stock rom, leave the chinese rom, and get back to your original rom.

I've gone back to usable rom now. Leave it there for awhile.
sent from my custom HTC Salsa.

Hi,
@BigBearEvo isn't the case that you perhaps have your device still s-on?

snatch_this said:
Hi,
@BigBearEvo isn't the case that you perhaps have your device still s-on?
Click to expand...
Click to collapse
Not likely my friend, the xtc clip makes you s-off.
Sent from my HTC C510e using Tapatalk

After the installation if i wanna uninstall the recovery, can i do it and how?
Thanks...

any_body said:
After the installation if i wanna uninstall the recovery, can i do it and how?
Thanks...
Click to expand...
Click to collapse
reinstall your ruu and it wipes the handset completely inc recovery

[Q] Android install methods?

I have tried installing Android on my TouchPad by using the rootzwiki, XDA, Idiots Guide 2.0 on YouTube and it just wont install. I have double-checked and triple-checked every step in the guides and it still will not install moboot.
When I go into USB mode and input the commands on CMD it wont do anything and it will stay in USB mode and wont go into double-penguin mode.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I have installed Android on this touchpad before but I didn't like the early CM7 builds so I uninstalled Android and just used stock WebOS. Could that be the problem or are the guides outdated?
Is there a different method to installing Android on the Touchpad?

liftedngifted1 said:
I have tried installing Android on my TouchPad by using the rootzwiki, XDA, Idiots Guide 2.0 on YouTube and it just wont install. I have double-checked and triple-checked every step in the guides and it still will not install moboot.
When I go into USB mode and input the commands on CMD it wont do anything and it will stay in USB mode and wont go into double-penguin mode.
I have installed Android on this touchpad before but I didn't like the early CM7 builds so I uninstalled Android and just used stock WebOS. Could that be the problem or are the guides outdated?
Is there a different method to installing Android on the Touchpad?
Click to expand...
Click to collapse
It's been a while since I installed android, but for CM9, I think you have to use Acmeinstaller 2.

After the CM7 methods did not work, I tried the CM9 and ACMEInstaller2 methods and it still didn't work.

liftedngifted1 said:
After the CM7 methods did not work, I tried the CM9 and ACMEInstaller2 methods and it still didn't work.
Click to expand...
Click to collapse
Hmmm.. The only thing I can think of is doctor the TP and do a fresh install for android.

chicle_11 said:
Hmmm.. The only thing I can think of is doctor the TP and do a fresh install for android.
Click to expand...
Click to collapse
What do you mean by doctor? Like reset the touchpad to factory settings? Because I have done that already.

liftedngifted1 said:
What do you mean by doctor? Like reset the touchpad to factory settings? Because I have done that already.
Click to expand...
Click to collapse
WebOS Doctor. Read here : http://www.webos-internals.org/wiki/How_To_Recover

You said USB mode - do you mean in WebOS or within the USB loading screen ?
Also, try re-downloading the files from RootzWiki - ACMEInstaller2, moboot, cwm, and the Alpha2 ROM zip. Make sure they're placed in the proper folder on your /media partition (/cminstall, no spaces, no caps), and try that again.
Barring that, you can always try going to THIS THREAD and resetting your TP to factory - it's the most comprehensive way to clear it and start fresh.

I cannot install Cyanogenmod again before unbricking my Touchpad.

Hello people
My problem is this:
Last tuesday I installed a new version of Cyanogenmod on my WiFi 32GB HP Touchpad. I installed CM9 on it a year ago and had no problems in this months, but tuesday night I upgraded it to CM10. Upgraded succeded but after installing a new version of gApps via clockworkmod, I lost the Android partition, so I start tro use webOS again.
Before connecting my Touchpad to my computer, windows saids that it was a problem with the Touchpad hard drive and I selected to format it =S
Well, my Touchpad became a brick for two days until I found this forums(dot)webosnation.com(slah)webos-internals/295881-webos-doctor-12-issue-fixed(dot)html. Ok, I have webOS on it again and is working great, BUT... I cannot install Cyanogenmod 9 or another ROM. Installation get stuck before trying to resize partitions, it says that a previous CM installation was detected and and then it says something like this "Resizing partitions failed because partition size is not the same than its backup... ".
I dont know what to do, I search all the web and didnt find anything :/
Do you guys know what can I do to fix this and install CM9 again?
Im sorry if it is not easy to understand me, thats because English is not my main language

This is what appears on display after running ACMEInstaller3.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I guess the problem is the difference between the reported free space, and the the real free space on system.
How can I fix that?

Gabonjour said:
Hello people
My problem is this:
Last tuesday I installed a new version of Cyanogenmod on my WiFi 32GB HP Touchpad. I installed CM9 on it a year ago and had no problems in this months, but tuesday night I upgraded it to CM10. Upgraded succeded but after installing a new version of gApps via clockworkmod, I lost the Android partition, so I start tro use webOS again.
Before connecting my Touchpad to my computer, windows saids that it was a problem with the Touchpad hard drive and I selected to format it =S
Well, my Touchpad became a brick for two days until I found this forums(dot)webosnation.com(slah)webos-internals/295881-webos-doctor-12-issue-fixed(dot)html. Ok, I have webOS on it again and is working great, BUT... I cannot install Cyanogenmod 9 or another ROM. Installation get stuck before trying to resize partitions, it says that a previous CM installation was detected and and then it says something like this "Resizing partitions failed because partition size is not the same than its backup... ".
I dont know what to do, I search all the web and didnt find anything :/
Do you guys know what can I do to fix this and install CM9 again?
Im sorry if it is not easy to understand me, thats because English is not my main language
Click to expand...
Click to collapse
Follow this guide: http://forum.xda-developers.com/showthread.php?t=
If you have problems with novaterm, there's a good work around on page 12.
Read the whole thing, there's lots of good information there.
If you're going to use cm10 or higher, use acmeinstaller3 to install it.
Good luck.
Edit : use acmeinstaller3 even if you're going to use CM9. Also, if you haven't done so already, update your moboot to 0.3.8 and cwm to 6.xx here's the link : hmm, can't paste. Those files are in goo.im/devs/jcsullins.
Make sure you have a full charge on the battery. You don't want to run out of power in the middle of the procedure.
Here's a good link, fixings the above : http://forum.xda-developers.com/showthread.php?t=1426244

chicle_11 said:
Follow this guide: http://forum.xda-developers.com/showthread.php?t=
If you have problems with novaterm, there's a good work around on page 12.
Read the whole thing, there's lots of good information there.
If you're going to use cm10 or higher, use acmeinstaller3 to install it.
Good luck.
Edit : use acmeinstaller3 even if you're going to use CM9. Also, if you haven't done so already, update your moboot to 0.3.8 and cwm to 6.xx here's the link : hmm, can't paste. Those files are in goo.im/devs/jcsullins.
Make sure you have a full charge on the battery. You don't want to run out of power in the middle of the procedure.
Here's a good link, fixings the above : http://forum.xda-developers.com/showthread.php?t=1426244
Click to expand...
Click to collapse
Thank you very much but... I cant access to Touchpad as root user when using novaterm in windows and linux. It doesnt say [email protected] It only shows a "]" symbol. When I type "lvm lvscan" or any other command, it says "This command doesn exist"...

Partitions deleted?

Hi!
I have a dual boot teclast x98 c5j6. I had problems with battery, so I tried to install android 4.4.4. During the flash I think I selected to delete partitions, and know, when I power on the tablet, in the dual boot menu I can only see android logo, and not both logos like before. How can I solve it?
thanks!!

I have the same problem. I've choosed the wrong xml file during the flash...
Enviado desde el móvil

Did you solved the problem? I have the same issue. I tried to install stock ROM, I have chosen no partiotion but my system partition size is 1GB and system.img was litte over 1GB and flashing stoped at 86% with error. Then i flashed Mirek Lolipop v6 but it is only android logo on dual boot. When i use "boot to Windows" under android it shows error like below:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
[/IMG]
Is there aby chance to bring Windows back?

Did you solve your partition problems
Dear friends,
did you solve your partition problems? i have the same. My android partition works perfect, but the windows partition isnt more there.
cheers
Hasan

Unfortunately no, I had to reinstall Windows

no usb boot
hello thank you for answering,
i would like to reinstall windows, but there is no more a windows partition.
I installed before windows 10 manually, but when i trying now to do the same, its not booting from the usb stick anymore. I flashed again the bios ver. 2.02. without any success. has somebody any idea?

chinahasan said:
hello thank you for answering,
i would like to reinstall windows, but there is no more a windows partition.
I installed before windows 10 manually, but when i trying now to do the same, its not booting from the usb stick anymore. I flashed again the bios ver. 2.02. without any success. has somebody any idea?
Click to expand...
Click to collapse
Use the OTG USB installation method mentioned by some fellas in the official Teclast X98 forum.
Format a FAT32 thumbdrive.
Copy the 5 *.img files, installer.cmd and partition.tbl to the root of the thumbdrive.
(Ensure u got the right installer.cmd and partition table setting files, view it to confirm).
Connect the OTG cable along with the plugged-in thumbdrive.
Bring the Tablet to Droidboot Recovery Mode (The one with a Big Green Android if original recovery image).
It will automatically start recovery and reboot.

hello kevinlaikf,
thank you for your suggestions, but didnt work. the menu still shows "entering nx mode. waiting for fastboot command". thats it. i copied all the files you mention.
cheers
hasan

Hello, have anyone found any solution to thiw problem? unfortunately it is mine too.... please help me, i need windows back...