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

[Q] Internal sd card issue

hello, I have the Samsung Captivate and am having a problem with the internal sd card. I went to put android 2.2 froyo and everything went well said success threw odin but my phone will boot up but once it gets to the galaxy s screen it stops. I have done the update threw odin several times and I run into the same problem. I got into system recovery mode and formatted everything cause it says that there was an error in the internal sd card, and needed to be formatted so I did that. Now when I go to reinstall packages it gives me this list.
--install from sdcard...
Finding update package...
opening update package...
Verifying update package...
E: failed to open /mnt/internal_sd/update.zip (no such file on directory)
E:signature verification failed
Installation aborted
any help would be much appreciated thank you.

yeah....reinstall packages doesnt do anything unless there is a file on your sdcard called UPDATE.ZIP
what you need to do is go back into DOWNLOAD mode, not recovery mode and use ODIN.....

I did that and after everything finishes and reset comes up in the blue box the phone starts it will go threw a list and it comes to a data wipe failed in red and formatting CACHE and DBDATA then applying multi-csc, installing multi-csc. Then Install default apk files, please wait
E:Can't mount /dev/block/mmcblk0p2 (invalid argument0
E: copy_data_default_apk:cannot mount DBDATA:
your storage not prepared yet, please use UI menu for format and reboot actions.
Then I format the sdcard and go threw everything again and it does the same thing. Im trying to give all the details.

I've got the same problem with GT-i9000.
Tried to flash with pit 512 and re-partition and pit 803 with re-partition, but the problem remains.
{
"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"
}

exactly the same problem here
anyone got the solution right?

off topic but....
@thebeast
Your posts are hard to read. I keep thinking you are throwing your phone.
threw - past tense of throw "I threw it out the window"
through - by way of "I updated through odin"

Yeah I have that problem sometimes cause I'm typing relatively fast while focusing on other Things. I also do not proof read, relying on spell check too much. Considering I was trying to explain exactly what was happening to my phone from memory and going "through" the process over and over some mistakes are bound to happen. I had my lil bro hussle an att support store and get me a new one hence why I never checked this thread.
If you are having the same problem as me you do or did Not have an update.zip file on your internal SD. You deleted it or it was removed some how so before u tried to install anything you should of put it back to stock and hopefully that would of fixed it but I do not know the solution based on the fact I never bothered fixing mine.
Sent from my SAMSUNG-SGH-I897 using XDA App

lol @ the grammar police.
Stupid question - have you tried to use ODIN to go back to stock before attempting to re-flash? ODIN usually completely wipes the phone and any of the silly issues that come up.

The problem that is encountered is using oden to update while its missing that file so it deletes and starts to install the new rom but cannot. So the phone is stuck in limbo, I tried to use the one click flash countless times left it for hours and it would never work. So maybe if you did that before u tried to put the rom it might have worked but not once the damage is done. As far as I know.

thabeast said:
The problem that is encountered is using oden to update while its missing that file so it deletes and starts to install the new rom but cannot. So the phone is stuck in limbo, I tried to use the one click flash countless times left it for hours and it would never work. So maybe if you did that before u tried to put the rom it might have worked but not once the damage is done. As far as I know.
Click to expand...
Click to collapse
I had a similar issue I think like 2 days back when I goofed up something in the framework folder. Nothing seemed to work.
So I had to revert back to stock using one click. That was the only thing that worked.

Yeah one click would not work for me at all trust me I tried that forever until I got the replacement.
Sent from my SAMSUNG-SGH-I897 using XDA App

thabeast said:
Yeah one click would not work for me at all trust me I tried that forever until I got the replacement.
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
Did u try going to clock work recovery and doing a "reset to factory settings"

I did and would not work. But I have a fully workout one now so maybe the Guy who is having the problem now should answer these questions lol
Sent from my SAMSUNG-SGH-I897 using XDA App

[Q] Help, Accidentally damage the "Fonts" folder, My Phone wont start

The situation is like this,
first am new to the android world and i was reckless i know, but some help would be nice
Case:
-Device: Xperia X8
-Rom: Stock 2.1
-USB Debugging Enabled
-Root (SuperOneClick)
-BusyBox v1.18.4
-Bootloader locked ( default state didn't touch it so its locked i guess)
-No Recovery of any kind
-** Very Important to keep the files, so please no solutions includes wiping the internal memory
What happen:
i was using "Font installer" app to change fonts and accidentally replaced "ALL" the font files in "System/Fonts" and that led the device not to boot now stuck on "Sony Ericsson" black screen
So:
- I think i need a copy of the original "System/Fonts" of any Xperia X8, if you guys can upload?
- and i need to know how can i access the phone internal memory so i can replace the content of "System/Fonts" with the new files
Thanks In Advance

Restore via pcc
Sent from my E15i using xda app-developers app

ElmirBuljubasic said:
Restore via pcc
Sent from my E15i using xda app-developers app
Click to expand...
Click to collapse
As i said "-** Very Important to keep the files, so please no solutions includes wiping the internal memory"

medomoo said:
As i said "-** Very Important to keep the files, so please no solutions includes wiping the internal memory"
Click to expand...
Click to collapse
Then I guess you are outta luck.. You have to re-flash your ROM. That'll delete data from internal memory. Data on SD Card will be safe..

May be you can use adb to push folder or files you want to its location. It will save your precious data.
Sent from my R800i using xda premium

creative_md said:
May be you can use adb to push folder or files you want to its location. It will save your precious data.
Sent from my R800i using xda premium
Click to expand...
Click to collapse
Thank you i will try that, but still i need the original "Fonts Folder", can any one please upload ?

Try to download any ftf file extract it then copy fonts folder from there
Sent from my R800i using xda premium

creative_md said:
Try to download any ftf file extract it then copy fonts folder from there
Sent from my R800i using xda premium
Click to expand...
Click to collapse
Thanks, got the fonts folder still working on how to push it

tried adb, but i cant get root
After adb shell i get $ when i type su i get "[1] segment fault su"
i tried and i searched every where with no luck !! any help please
{
"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"
}

!!!!! Any Help !!!!!

1. Hope u have enabled usb debugging !
2. Go to recovery (if u have it,if not you are in the trouble)
3. Go to mount/storage
4. Mount system,data
5. Download Android Commander or QtADB !
6. Connect usb cable to pc and x8
7. Open Android Commander and QtADB
8 If phone is sucessfuly connected,u can copy Fonts folder from working rom and replace it with damaged fonts folder.
9. Reboot
10. Enjoy!:laugh:

2010matej said:
1. Hope u have enabled usb debugging !
2. Go to recovery (if u have it,if not you are in the trouble)
3. Go to mount/storage
4. Mount system,data
5. Download Android Commander or QtADB !
6. Connect usb cable to pc and x8
7. Open Android Commander and QtADB
8 If phone is sucessfuly connected,u can copy Fonts folder from working rom and replace it with damaged fonts folder.
9. Reboot
10. Enjoy!:laugh:
Click to expand...
Click to collapse
Reading would have saved you some precious minutes that you now will never get back:
medomoo said:
Case:
-Device: Xperia X8
-Rom: Stock 2.1
-USB Debugging Enabled
-Root (SuperOneClick)
-BusyBox v1.18.4
-Bootloader locked ( default state didn't touch it so its locked i guess)
-No Recovery of any kind
Click to expand...
Click to collapse
@medomoo - There might be a way to access the internal memory with specialized equipment, but don't quote me on that one. Go to a phone repair shop or try talking directly to Sony.
The only thing you can do by yourself now is close your eyes and lose the information. You screwed things up really badly with no backup and no recovery. Learn, let it go and move on.

Fortun said:
@medomoo - There might be a way to access the internal memory with specialized equipment, but don't quote me on that one. Go to a phone repair shop or try talking directly to Sony.
The only thing you can do by yourself now is close your eyes and lose the information. You screwed things up really badly with no backup and no recovery. Learn, let it go and move on.
Click to expand...
Click to collapse
Thank you, But why i cant get root access in ADB

Let's put it another way. When your PC freezes, is there anything you can do to manipulate the files? No. Let's take one step further: when you get the blue screen of death while starting the system, is there anything you can do to anything inside your harddrive? No.
It's the same with your phone. Your phone is freezed even before mounting all of the partitions fully and correctly. So, ADB will do nothing. In short, in this regard, there's nothing you can do.
So, take your phone directly to Sony or to a phone repair shop. Or just lose the information.

OK lets say am going to flash a new ROM,
BTW just to take a lesson from that:- what is the safety steps i should take to prevent situation like this from happening again etc what kind of recovery and what else than recovery i can do ??

Backup all apps through titanium backup. And always make nandroid backup through recovery. Its advantage is that if you messed with your phone(like in this case) you can recover backup and you get your old phone back (with data of any kind).
Sent from my R800i using xda premium

Thank god, its working now and didn't have to flash new ROM and all my files are save,
1- Got "Shell Root" with SuperOneClick v2.3.3
2- Used "Android Commander" to push the Original Fonts to its place. and done.
Thanks everyone

New start

HI, I got this phone yesterday, it is now rooted with a custom CWM recovery and it's a great phone!
No issues so far, seems fast and stable and even plays flac files!
DISCLAIMER:
Rooting your phone and using custom Recoveries and ROMS have risks and may result in bricking your device, and has nothing to do with Google or the device manufacturers. In case of any mishap I am not responsible if you brick/ruin your phone in any way.
Basic computer skills are required and minimal knowledges about phones and phones utilities too.
Make sure that whatever you do, you are doing it at your own responsibility.
How to root :
You need to download four files
1. CWM Carliv 6 Elephone M2.zip
or TWRP_M2.zip
2. SP_Flash_Tool
3. UPDATE-SuperSU-v2.46.zip
4. MTK_Drivers_carliv_repack_win7_x64.zip
Copy UPDATE-SuperSU-v2.46.zip to your internal storage card on your phone. You will need this later.
In Windows (not virtualbox) extract CWM Carliv 6 Elephone M2.zip, SP_Flash_Tool_5.1532.00.000_Windows.zip and MTK_Drivers_carliv_repack_win7_x64.zip
Go to the MTK_Drivers_carliv_repack_win7_x64 folder and click flash_tool
Then Click the Download tab at the top.
In that window click the Scatter Loading button and browse to the CWM Carliv 6 Elephone M2 folder and select the CWM Carliv 6 Elephone M2 file.
View attachment 3563620
Click Download.
Turn off your phone
Plug the USB cable into your phone and into the computer
Don't turn on your phone
When the Windows driver installer pops up cancel searching Windows Update and make it install the driver from MTK_Drivers_carliv_repack_win7_x64
You may have to force this by agreeing to install a non-signed driver, don't worry, it will still work.
Your phone should stay on a black screen, if not do this again until Windows has the correct driver.
You need to have the Preloader driver installed, once it is the flash_tool will flash the recovery.
The phone boots to Preloader then normal boot, if you miss the preloader option you have to restart and try again.
If your phone does not reboot (mine did not) you need to turn off the phone and then turn it on while holding Volume +
You will get three options on the screen
Recovery
Fastboot
Normal
You change the option with volume +
You choose the option with volume -
We want recovery
In Recovery
The volume buttons move up and down
Power selects the option you are on
You need to Install Zip
choose file from /sdcard
0/
UPDATE-SuperSU-v2.46.zip
After installation choose reboot and YES fix root!
Your phone will restart and you will now have root access.
All credit for the recovery : Caliv

sorry, but how did you root it?

Flash the custom recovery and then flash update_supersu.zip from the internal storage card.
Edit : Guide in first post.

If I do this process, will I lose my apps contacts...?

amilcar50 said:
If I do this process, will I lose my apps contacts...?
Click to expand...
Click to collapse
No, if it works as it should you will have no changes except a su binary and apk to control access.

Hello Kangburra i am from germany and i have no x64 bit PC-System. Have you the MTK_Drivers_carliv_repack_win7 for 32 bit system? So that i canflash it on a german WIN 8.1 32-bit system ?
CWM means it is also a recovery for the case if the flash fail
Thank you for answer.

......drivers
Hello,
thanks for the detailed instructions, but could you also provide us a download link for the 32 bit x84 mtk Drivers, who work with Windows 7?
Thanks

32 bit drivers and Windows 8 drivers added to post 1

Kangburra said:
No, if it works as it should you will have no changes except a su binary and apk to control access.
Click to expand...
Click to collapse
Thanks

Finally I obtain access root on Elephone M2. I try three time but was my error.
Thanks Kangburra for your attention and instructions.

CWM Carliv 6 For Elephone M1 can anyone help me?

Got no popup and cannot install the MTK_Drivers_carliv_repack_win7_x64. My phone reboots normal :/

Is the phone plugged in when you restart it? Is there a failed device in Windows Device Manager?

No failed device in Device Manager and the phone is plugged in. I've got it working and can access it with the Explorer in Windows. But the Flash-App doesn't flash a recovery

The driver for windows is not the same as the preloader needed to flash.

That's correct. But how can I change it (windows 7)? Don't know what I must uninstall and how I can install the correct drivers.

mmeidl78 said:
That's correct. But how can I change it (windows 7)? Don't know what I must uninstall and how I can install the correct drivers.
Click to expand...
Click to collapse
Try this http://forum.xda-developers.com/showthread.php?t=2206421

THANK YOU! I had to delete a hole lot of drivers from a bunch of phones. Now everything worked fine.

why would I root? bought m2 for 3gb RAM, but only 780 there
Kangburra said:
32 bit drivers and Windows 8 drivers added to post 1
Click to expand...
Click to collapse
Kangburra, great post, txs
Lost my suscription, so starting again as newby
Why would I root? Many sites warn against it.
Rooted my previous non-brand Chinese phone with Android 4.1.1., only 1GB of RAM and partitioned phone memory (12 Mb)
Used Kingroot, worked like a charm, usefull because of partitioned phone memory and could get rid of junk & tmp files. Did not solve low RAM btw (Android too old for swap apps)
bought M2 for bigger RAM, but only 780 Mb out of 3 GB available for apps (in my phone, checked with several appps); get the impression that this is due to the launcher that Elephone installed (becomes visible after installing Nova). As I understand it, the so called UI is only a launcher (60 Mb). Why then so much RAM in use?
So my question(s) to you: (1) do you agree with memory findings, and (2) will this improve with root?
TXS in advance for your thoughts

jos# said:
bought M2 for bigger RAM, but only 780 Mb out of 3 GB available for apps (in my phone, checked with several appps); get the impression that this is due to the launcher that Elephone installed (becomes visible after installing Nova). As I understand it, the so called UI is only a launcher (60 Mb). Why then so much RAM in use?
So my question(s) to you: (1) do you agree with memory findings, and (2) will this improve with root?
TXS in advance for your thoughts
Click to expand...
Click to collapse
I am seeing a lot of free space and not much given to Launcher3.
{
"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"
}

Permissions issue - no USB connection. Anything I can do?

Hey guys, ased this is osm0sis's thread and he advised me to post here - copy paste incoming with link to original post and screenshot included to show what dirs look like. Issue:
Hey guys - hoping there may be a script or something that can be done to fix my Nexus 6 nightmare. I totally messed perms up for /root dirs in recovery - tried both the perm fix zip from here and TWRP fix perms, no luck. Nandroid no luck either. I literally cannot wipe internal - no USB connectivity, Qi charger is all I can use. Is there absolutely any script or anything that can be done to fix my Shamu? SS attached to show a few dirs. I'd be more than appreciative of any help - desperate here, not gonna lie.
{
"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"
}
Original post in osm0sis's thread http://forum.xda-developers.com/showpost.php?p=68465219&postcount=837
Any help at all would be most appreciated - desperate here guys!

No USB is bad, very bad. Suggestive of something bigger gone wrong bad. Like you corrupted the bootloader or something since fastboot doesn't work.
My only thought is this: So you've probably got root? FlashFire stock boot.img and system.img from the latest factory image and have it format data and cache. Allow FlashFire to do its EverRoot thing to retain root for the case it doesn't work. Since it's a Nexus, if that doesn't work you could try FlashFire to reflash the latest bootloader as well. Nothing really to lose at this point.

Whats about the USB port, did you try to fix it ? Its easy to get to the motherboard, may its enough, if you very carefully try to compress the port.

osm0sis said:
No USB is bad, very bad. Suggestive of something bigger gone wrong bad. Like you corrupted the bootloader or something since fastboot doesn't work.
My only thought is this: So you've probably got root? FlashFire stock boot.img and system.img from the latest factory image and have it format data and cache. Allow FlashFire to do its EverRoot thing to retain root for the case it doesn't work. Since it's a Nexus, if that doesn't work you could try FlashFire to reflash the latest bootloader as well. Nothing really to lose at this point.
Click to expand...
Click to collapse
I flashed an N system image that doesn't wipe data, seemed to fix perms up mostly. Not having issues accessing things, but some displays odd in /root still. Things are all working now, though. I restored Nandroid from before messing up perms and rolled back to my MM AOSiP backup after lettting system image do its thing. As for USB - it's actually hardware failure. The port goes in and out. It's been getting bad a while but recently it's unusable most of the time. I can charge if I let phone sit upside down, but data connectivity doesn't work on computer anymore obviously. Does that indicate anything more than actual USB port itself being messed up? I hope not haha. Thanks for the reply!
coremania said:
Whats about the USB port, did you try to fix it ? Its easy to get to the motherboard, may its enough, if you very carefully try to compress the port.
Click to expand...
Click to collapse
Thanks to @rignfool I am looking into getting a USB port replacement possibly here soon and installing... seems easy enough. Thanks for responding!

Oh, that's good bad news with your port, there's an youtube replacement video. And if your USB port only goes in and out, it should be easy to fix it back to the logic board