Related
ROOT:
We've been discussing about this for about a month, and I think it's time to sum it all up and open a new cleaner thread.
First, how do you root the Alcatel Onetouch 997D?
This phone is quite new (less than 2 months in the market) and is one of the few phones which can't be rooted by the script developed by Bin4ry or the other well-known methods, such as Unlockroot or SuperOneClick, but it is not unrootable.
In order to root this phone, you must first boot it into Factory mode, a special menu, present in all Mediatek based phones, which can be used to test the various parts of the phone. You get to this menu by turning the phone on while pressing the volume down batton and power button at the same time, until it appears.
Once in factory mode menu, you can connect the phone to a pc, which, if the appropiate adb drivers are installed, will detect it. At this point, the phone can be rooted, by the use of an app called MTK Droid tools. I've succesfully tested versions 2.2.8 and 2.2.9.
After MTK Droid Tools finds the phone, you just have to press the "root" button. The phone will be rebooted two times, and after the second reboot, MTK Droid Tools achieves a temporary root which enables it to install Superuser, su and busybox, so the root is permanent.
During this process, MTK Droid Tools asks whether you want to make a backup. You'd better answer no, since this process is very buggy and fails on this phone, so it's a complete waste of time.
When "Task is complete" message appears, you can reboot the phone, but it won't work right away. Due to a problem not yet identified, it's mandatory to wipe data from recovery for the phone to work. Some people have reported the loss of Google Play Store, and others have lost a lot of apps. Anyway, a wipe solves the problem and the phone remains rooted.
MTK Droid Tools 2.2.8 can be found here: http://www.4shared.com/zip/NyHaro3-/MTKdroidTools.html
CWM Recovery:
We have a 99% working CWMR. I compiled it myself with the help of the dsixda kitchen and the MT6577 CWMR porting plugin developed by Bruno Martins.
I say it's 99% working because backup doesn't work 100%. Alcatel phones have a non standard partition called "custpack", which contains a lot of apps bundled with the phone and whose deletion prevents OTA updates from working, so it's not something one would like to remove. My knowledge of Android is not enough to try to dig inside CWMR source code, to see if I can modify the backup process and make it recognize the custpack partition, so I left it as is. Instead, I decided to develop a shell script which can make CWMR-compatible backups, which can at least be restored from it.
Everything else is fully functional. It's version 6.0.1.2.
To flash it, you need to root the phone, using the method explained above, and flash the recovery image using Mobileuncle Tools utility, which can be freely downloaded from Google Play Store. It's very important to download the latest version from Google Play, since previous versions lying around, and the version MTK Droid Tools installs during the root process can't flash a recovery on MT6577 processors.
To flash the recovery with Mobileuncle tools, you have to place it on the root of the external sd card and open Mobileuncle tools. After granting root permissions, if you haven't done yet, you choose "change recovery" and choose the corresponding .img file. Once the process is done, the phone will automatically reboot into the new recovery. It may fail, which you'll notice because the phone boots into the stock recovery, and you may need to do it again. I've noticed that, at least in mine, it works best if I do it while the phone is unplugged from the computer.
As I said abpove, everything, except backup, works well. Restore works, if you have the correct backup (more on this later).
My CWMR can be downloaded from my Mediafire account: http://www.mediafire.com/?v7wfjr6v1t7b0z5
NANDROID BACKUP:
After noticing the backup process in CWMR can't backup the Alcatel exclusive custpack partition, I began trying to solve this. I guess the best way to do it should be modifying the source code of CWMR to adapt the backup process, but, since that exceedes my current knowledge level, I tried differemt approaches. I downloaded the app Online Nandroid backup from Google Play, and learnt that a nandroid backup can be easily done using a shell script, given you have a rooted phone and a way to execute shell scripts. The good news is that it's done, and I have achieved my goal, and now have a working shell script, which creates backups that can later be restored from CWMR.
This script creates 7 files, like the standard CWMR backup process does. The files are:
1) boot.img
2) recovery.img
3) system.ext4.tar
4) cache.ext4.tar
5) data.ext4.tar
6) .android_secure.vfat.tar
7) nandroid.md5
Files 1, 2, 4, 5 and 6 are exactly what you now get if you use my CWMR port and perform a backup. The difference lies in file 3.
In a backup created from our current CWMR, this are the contents of the tar archives:
system.ext4.tar: files under /system, and all its subdirectories
cache.ext4.tar: files under /cache, and all its subdirectories
data.ext4.tar: files under /data, and all its subdirectories
.android_secure.vfat.tar: files under /sdcard/.android_secure
In a backup created by my script, it's slightly different:
system.ext4.tar: files under /system, and all its subdirectories, and also files under /custpack, and all it's subdirectories
cache.ext4.tar: files under /cache, and all its subdirectories
data.ext4.tar: files under /data, and all its subdirectories
.android_secure.vfat.tar: files under /sdcard/.android_secure
On both backups, boot.img and recovery.img are images compatible with Mediatek Flash Tool or Mobileuncle Tools (in the case recovery.img), and nandroid.md5 contains the md5 sum of every file, so the restore process can validate the integrity of them, to prevent you from ever restoring a corrupt archive.
In order to use my script, you need an app which can execute them. My preference (and the only one I have fully tested the script with) is GScript, which can be freely downloaded from Google Play Store.
There's also a paid version, but the only difference between them is that the paid version is updated more often than the free one.
How to install the script:
1) Download and install GScript, free or paid. You can use the apk file provided by me inside the attached zip.
2) Download the attached zip file with the scipt, if you haven't done so to install GScript.
3) Put the script on the external sd card, under a folder called "gscript". Use lowercase characters for the name and never change the name, as this would result in GScript not working or finding your scripts. The resulting structure should be:
/sdcard/gscript
|
------------> bin
Inside /sdcard/gscript you have the script itself, called "Alcatel_OT_997D_nandroid.sh" and inside /sdcard/gscript/bin, you have the busybox
binary, used by the script. Even if you have busybox already installed, don't delete this binary, since it's the only one the script will use, and
the only one it's been fully tested with.
4) Open GScript.
{
"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"
}
5) On the GScript main window, you can see a pair of sample scripts already included. You need to touch the menu button and then on "Add script".
6) Browse for the .sh file on /sdcard/gscript, and tick "Needs SU?" if it's not already ticked, since this script needs a rooted phone.
7) Once the new script is in the list of installed scripts, you only need to touch its name to launch it. The first time you do it, GScript will ask for root permissions. Allow it.
Once you open the script, it will run automatically, and will end around 5-10 min. later, depending on how loaded your phone is. In order to be able to see every message shown by the script, it's better to raise the screen timeout, to at least 10 minutes. After execution, the output window will auto close, unless you cancel auto closing by touching anywhere on the screen except, of course, the close button.
The backups are stored under the /sdcard/clockworkmod directory (the script will create it if its not already there), under which it will create a new subdirectory, with the date and time of the backup, just in the same format CWMR uses.
During the execution of the script, you may see two error messages, which are not really errors, but warnings you can ignore. These errors are:
1) Errors creating directories at startup. If the script has already been used, or you have tried the backup inside CWMR, sdcard/clockworkmod/backup already exists. The script will tell you that, but it will keep working.
2) Removing leading "/" from member names: tar utility removes "/" from the input parameters, just that.
3) XXXXXXXX: socket ignored, where XXXXXXXX is the name of a file. Sockets are temporary files Unix apps use to communicate with other apps. Since they are temporary, tar just ignores them, so you can also ignore the error message.
On mi phone, after I close the results window, GScript force closes, but this doesn't affect the execution of the script. As I've read somewhere, it
looks like this is a problem common to a lot of users.
DISCLAIMER:
This script is offered AS IS, with no warranty. It has been successfully tested on my own phone, and the generated backup was then perfectly restored from recovery with no issues, but I can't say it won't fail on other people's phones.
It's the first version, fully functional, but with some room for improvement. As it is right now, it's not error free, since it doesn't check if you have enough space left on the sdcard, or if you don't have any apps moved to the sd card. In fact, I have not tested it in such a situation, and I don't know what would happen if you backup your phone with no apps moved. On the other hand, it doesn't bakcup sd-ext, so if anyone has a second partition on the sdcard, to use Link2SD o a2sd, that partition won't be backed up, although data for apps linked to the second partition will. Anyway, even if it fails, you don't have to worry, since it won't change anything inside the phone. If you later restore a backup made with this script, you are doing it AT YOUR OWN RISK. I will not accept any responsibility for damage or data loss caused by the use of this script or restoration or any backup created with it.
Don't forget this script needs a rooted phone, and that performing some things on rooted phones is risky. If the worst case, you will always be able to recover the phone using Alcatel One Touch Upgrade on your pc.
Any comments or improvements are welcome, but if you change / improve anything, don't forget to share it with the community, so everyone can take advantage of it.
IMPORTANT:
This script is only suitable for the Alcatel OT-997D, and probably other phones by the same brand, if they have the "custpack" partition, exclusive to Alcatel. It won't work, unless code regarding the custpack partition is modified, in other phones, and I will not give support to users complaining the script doesn't work on their non Alcatel phones, or their Alcatel phones without s custpack partition.
FINAL NOTE:
Ok, that's it. Now, I'm going to have a rest, maybe until Alcatel release the long waited Jelly Bean update.
EDIT:
I had forgotten the "thanks" section:
Thanks to:
@dsixda, for the great kitchen
Bruno Martins (@bgcngm) for his valueable advice and his scripts to unpack/repack recovery of any MT657x based device
@yuweng, who developed the great kitchen plugin to port CWMR to any MT657x based device. and also pointed me in the right directory when I was trying to root the phone
@ameer1234567890, author of the great onandroid script. I haven't used your code, but it taught me I had to unmount and remount the sdcard on a different location to be able to backup .android_secure
Reserved
Reserved too
Any chance of working on a custom rom? i would love to get the standard google theme instead of the alcatel icons
maybe i try to get this done, changing the icons is'nt that hard normally
btw i'm still looking to cleanup this phone, you know the partitions pretty wel, where is the location of all the stock apps like chrome etc, i would love to make the phone as close to googles standard as i can get it
edit: you can always pm me, i don't want to ruin this topic
Hey jman10 thank you very much for your awesome tutorial.
But i still have to ask, if the restore works 100%, because of lack of gps signals i made a cwm backup of my current stock-rom(4.0.4) and tried, if the newest update(4.0.4-01001) still has problems with gps signals. Well actually it didn't get any better, so i decided to go back to the old version with the help of my backup.
CWM said there were no errors while restoring, so also thought it. But i get a few bugs using the old version, the stock camera-app gets force closes, even after reboots or a data wipe. The stock e-mail app shows weird artefacts on the email subjects, a very large 'x'. It seems, like a lot of system files are missing or sth.
Can you help me?
Thanks!
kassipopassi said:
Hey jman10 thank you very much for your awesome tutorial.
But i still have to ask, if the restore works 100%, because of lack of gps signals i made a cwm backup of my current stock-rom(4.0.4) and tried, if the newest update(4.0.4-01001) still has problems with gps signals. Well actually it didn't get any better, so i decided to go back to the old version with the help of my backup.
CWM said there were no errors while restoring, so also thought it. But i get a few bugs using the old version, the stock camera-app gets force closes, even after reboots or a data wipe. The stock e-mail app shows weird artefacts on the email subjects, a very large 'x'. It seems, like a lot of system files are missing or sth.
Can you help me?
Thanks!
Click to expand...
Click to collapse
If you use my script to backup your rom, restore from CWMR will work 100%. So, your way to go is to start from scratch. Download Alcatel Onetouch Upgrade to a pc, connect the phone and get the latest full version rom on their servers (which sometimes is not the latest one available). Then, connect via wifi and get the latest OTA update. After that, you can root the phone, flash CWMR and make a working backup. From that moment, you'll be able to restore whenever you want and not risk anything.
By the way, which problems are you having with the gps? Mine is working like a charm, even indoors. Where are you from and what kind of tests have you done with it?
Hey thanks for your quick answer, actually i did the whole process that way:
-root stock firmware 4.0.4
-installed cwm per mobileuncle tools
-created image per script
-updated with the help of one touch manager to 4.0.4-01001
-tried gps, didnt work
-rooted
-installed cwm per mobileuncle tools
and then i wanted to return to point 1, but as soon as i restored the backup, my camera doesnt work and i get random fc's of several apps. i would like to return to stock 4.0.4, because since the new update the system is more laggy
do you know a way? do you have a *.img of the old version?
my gps is really weird, i would say it works at 10%. in my home city i couldnt make it work, then i tried it randomly in 2 other cities and it worked instantly, but then i try it again at the same spot, where it worked a couple of hours earlier and it doesnt work anymore its really weird.
thanks man!
kassipopassi said:
Hey thanks for your quick answer, actually i did the whole process that way:
-root stock firmware 4.0.4
-installed cwm per mobileuncle tools
-created image per script
-updated with the help of one touch manager to 4.0.4-01001
-tried gps, didnt work
-rooted
-installed cwm per mobileuncle tools
and then i wanted to return to point 1, but as soon as i restored the backup, my camera doesnt work and i get random fc's of several apps. i would like to return to stock 4.0.4, because since the new update the system is more laggy
do you know a way? do you have a *.img of the old version?
my gps is really weird, i would say it works at 10%. in my home city i couldnt make it work, then i tried it randomly in 2 other cities and it worked instantly, but then i try it again at the same spot, where it worked a couple of hours earlier and it doesnt work anymore its really weird.
thanks man!
Click to expand...
Click to collapse
Did you do a factory reset after rooting? It's really important to do so, and the phone doesn't work if you don't.
Hey mate,
sure i did, i have no problems with root at all. My problem is to restore my cwm backup i did with the old firmware, because i really want it back badly. Do you have a image file of the "roll out" stock firmware?
Thanks in advance!
Hi,
it seems like I am missing something.
I installed the MTK-Tools 2.2.8, connected the phone but the phone is not recognized. I see there is missing some MT65xx AndroidPhone-Driver. Where can I get one?
The installation of the OneTouchManager does not help. Any ideas?
kassipopassi said:
Hey mate,
sure i did, i have no problems with root at all. My problem is to restore my cwm backup i did with the old firmware, because i really want it back badly. Do you have a image file of the "roll out" stock firmware?
Thanks in advance!
Click to expand...
Click to collapse
The system image I have is vastly modified by me, so it might not be suitable for you. If you did the backup using my script, it should work right away. Can you tell me what files (names, sizes, etc.) you have in your backup?
Roland_SGN said:
I installed the MTK-Tools 2.2.8, connected the phone but the phone is not recognized. I see there is missing some MT65xx AndroidPhone-Driver. Where can I get one?
Click to expand...
Click to collapse
There is a driver directory inside mtk tools zip. Let windows take that driver manually.
we now have kernel (and more) sources online from alcatel:
http://sourceforge.net/projects/alcatel/files/OT_997D_20121228.tar.xz/download
I'm downloading them...
fear_factory84 said:
we now have kernel (and more) sources online from alcatel:
http://sourceforge.net/projects/alcatel/files/OT_997D_20121228.tar.xz/download
I'm downloading them...
Click to expand...
Click to collapse
Now we just need a CM10 rom, then we're on!
Sent from my Packard Bell [email protected] v20 using Tapatalk
MadMav88 said:
Now we just need a CM10 rom, then we're on!
Sent from my Packard Bell [email protected] v20 using Tapatalk
Click to expand...
Click to collapse
You need also to implement dual sim support on it.. it's a huge work!!!
For now we can aim to fix those annoying bugs on stock rom (if we can) and get a 100% working recovery.
My bugs on latest stock rom:
- bluetooth freezes when bt headset is disconnected by lack of signal
- compass doesn't give good values at all
- need for speed most wanted sound is borked and is not 100% smooth like on other mtk 6577 devices.
In addition I would like to have:
- smaller system bar on the bottom
- search button and menu button always visible on system bar
- extended power menu with the option to have "extended desktop" (system bar hidden by killing it, and then restarted when reenabled)
These can be made by editing framework with smali and friends.
Prerequisite is a fully deodexed rom (and that is easier) and a lot of spare time!
Any news?
Sent from my ALCATEL ONE TOUCH 997D using xda app-developers app
fear_factory84 said:
You need also to implement dual sim support on it.. it's a huge work!!!
For now we can aim to fix those annoying bugs on stock rom (if we can) and get a 100% working recovery.
My bugs on latest stock rom:
- bluetooth freezes when bt headset is disconnected by lack of signal
- compass doesn't give good values at all
- need for speed most wanted sound is borked and is not 100% smooth like on other mtk 6577 devices.
In addition I would like to have:
- smaller system bar on the bottom
- search button and menu button always visible on system bar
- extended power menu with the option to have "extended desktop" (system bar hidden by killing it, and then restarted when reenabled)
These can be made by editing framework with smali and friends.
Prerequisite is a fully deodexed rom (and that is easier) and a lot of spare time!
Click to expand...
Click to collapse
About bugs:
- When I'm calling someone that is listed as favourite for a specific sim, the system asks which number I want to use.. I know about the configuration, I settled the first sim as principal (every call) and the second sim just for some contact. So, why is still asking which number is able to use for them? Is it a bug?
- The digital compass doesn't work well, or better, it's not working at all! The North it's not properly indicated, it follows the gravity verse..
Addictions:
- The status bar can be toggled by power menu or maybe by a sequence (example: vol - vol -)
Etc.
Sent from my Packard Bell [email protected] v20 using Tapatalk
MadMav88 said:
About bugs:
- When I'm calling someone that is listed as favourite for a specific sim, the system asks which number I want to use.. I know about the configuration, I settled the first sim as principal (every call) and the second sim just for some contact. So, why is still asking which number is able to use for them? Is it a bug?
Click to expand...
Click to collapse
It's the same on mine.
I tried to set one contact associated to 1st sim and an other to the 2nd sim, and I set the 1st sim for all call.
When I want to call:
-if I phone one contact without associated's sim, call goes direct by the 1st Sim.
-If I phone one contact with the 1st sim associated, call goes direct by the 1st Sim.
-If I phone one contact with the 2nd sim associated, the sim choice windows appear but it's written "suggested" on the 2nd sim.
So the call don't start automatically.
and I set no principal sim for call (every time you need to choose), I have the sugestion on the associated's Sim.
Many people complained about this contact sim preference bug.. I never used this function, so I can't tell.
To toggle status bar, the better working solution I've found is the Hide bar app (search it on xda).
Yesterday I was fighting with my phone that looses signal on the secondary sim when on charge. It may be a bug with my sim/operator combination when sim1 has 3g enabled.
Sim1 Wind Italy, 3g enabled on it, Sim2 Tim Italy no 3g (obviously), when I attach charger or usb cable, I loose Tim signal.
Swapping usim card slots does nothing.
If I enable 3g on Tim Italy, and no-3g on Wind Italy, it works flawlessy. Same if I disable totally 3g.
Anyone with similar issues?
I collected radio logcats and sent them to Alcatel Italia. Probably they will not reply at all, but I have tried...
Please do the same for other bugs! Maybe they'll hear us..
Converning CWM Backup: What about making the backup with online nandroid backup using an adapted partition layout like for those devices here?
That would be restorable by your cwm, too?
Based on the original guide that helped me get here: http://forum.xda-developers.com/showthread.php?t=2109041 Hope he doesn't mind but i also copied and pasted all the repeated process parts but hugely modified everything else ( MT6577 MTK MTK6577 MTK6XX MT6XX )
Purchase this phone HERE
Note: This will fix ANY broken H2000+ camera If your rear camera has stopped working with any other firmware, this one will work don't worry about clearing any cache / data / dalvik or anycrap, just follow this guide!
HERO H2000+ Rooting
Here is a new ever safer solution on how to root the "unrootable" Hero H2000+
WHAT ARE WE GOING TO DO?
(Main Modification)
Well in this mod it will remove the android IOS theme or normal unrootable android firmware that comes with the stock phone, most will find out when you try and root the stock it only gives it a partial root ( no access to /system ) or just ends up screwing the camera if you finally do figure it out, i've combined about 10 different mods i've found around the web over the last 3 days of selective google keyword searching to combine it into this simple mod, i haven't done much myself except Modded the scatter installation to include CWM and i created the .zip file that removes the bloatware and adds SuperSu.
(optional Modifications)
- Swap sdcard with sdcard2 (fix application saving options for he external card
- Remove the 3 onscreen buttons and remap the Top side mute key into a back button for a better screen view and more authentic iphone style use.
Make sure you DOWNLOAD THIS first, It's the most vital part and has almost everything you will need, in one whole simple file, to achieve what i'm going to show you how to do, I'm going to try and include lots of detail so listen up, any sources & links from places i got most my information & downloads from will be included at the bottom of this page, if you are interested.
Warning! This is at your own risk,i am not responsible for any damage this may do to your device and always backup before ( Seriously don't complain about it to me, i never took any precautions when playing around and my device is fine but i'm sure there are risks of breaking your device.
Warning: Pretty sure this deletes anything on the phone's Internal SD / Phone storage and system storage, but the external SD card should be safe, but i'd still back it up incase but mine was left untouched, if not i'd of lost about 20GB of music so it's your call.
1. Download the file provided, you should have the following files:
- Folder: 2000+ SUPER ROOT SUROOT SYSTEM ACCESS
- Folder: PHONE DRIVERS MTK MT6577
- Folder: SP_Flash_Tool_v3.1220.01 VERSION 1
- Zip: MTK_Drive.zip
2. How to install the correct drivers are included in the MTK_Drive.zip + the MTK MT6577 driver folder, the drivers are for when the device is just started up with USB plugged in, for when it's in a flash mode, it will be detected as MTxx or something on the driver installation window, you don't have to worry too much about this until you start flashing and it will pop up the first time you attempt to flash with "installing drivers" message, the 2nd time it SHOULD flash but it took me about 30x when i first started, so yeah good luck with that.
3. COPY THE "COPY ME TO THE 2GIG INTERNAL SD NOT EXTERNAL.ZIP" to the internal sd card before or after the flash (BEFORE WOULD BE BEST) via USB on the phone when it's booted, if you're using the H2000+ phone it will be the storage with 2GBish.
4. OK lets begin, Open folder "SP_Flash_Tool_v3.1220.01 VERSION 1" right click on Flash Tool.exe run as Admin, Then click on "Scatter-loading", then in the browsing folder open "2000+ SUPER ROOT SUROOT SYSTEM ACCESS" and load the "MT6577_Android_scatter_emmc.txt" then click download, if any messages pop up just click yes or ok,
then on your phone PLUG IN THE USB hold the power off button CLICK RESTART and the tool should detect the phone and install the files on the 2nd - 3rd time +, You will know when you have achieved this by a BIG GREEN circular ok Message
5. Now you should have the rom installed with superuser root and CWM all included in one flash ( Your welcome ), turn on your phone holding the power button + the Volume Up button.
6. Click install zip from sdcard - choose zip from internal sdcard - COPY ME TO THE 2GIG INTERNAL SD NOT EXTERNAL.zip install and BOOM done (PART 6 ISNT ESSENTIAL BUT...) it removes a lot of Chinese bloatware crap from the phone, replaces superuser for SuperSU which i prefer myself, and installs a few apps i like to have. and you are done, information on what below.
QUICK INFO
once done i can't remember but i'm sure i removed all the crap, slow, process hogging, battery **** eating apps! So you WILL need to download like a browser, media player, etc...
My favorites for this phone are:
GOOGLE MUSIC PLAYER
CHROME
EXPLORER (Free root explorer)
Titanium Backup (Good to delete system apps safely)
WEATHER & CLOCK accuweather (INCLUDES WIDGET SUPPORT)
Paid apps:
Camera MX
Keyboard (swiftkey)
I SUGGEST remove the **** launcher (But first download this beautiful life saving launcher) once you install that use Titanium Backup to uninstall the old launcher and this will maximize your battery.
Followed up by THIS THEME makes it look nice and sexy
or combine these
ILauncher (best on market from what i've tested )
Iphone Notifications (Adds more authentic iphone notifications)
Related guides:
How to unbrick your device: http://forum.xda-developers.com/showthread.php?t=1943442
Sources:
Chinamobile page ( need to register to download) Pages 1 - 5 is where i found some downloads
http://www.4shared.com/rar/BCwt0zz_/Taiwan101_Hero-H2000_CWM_Recov.html - this was the first rom i found with good root but breaks rear camera.
http://www.daten-hoster.de/file/details/388840/Recovery.zip
http://www.android-hilfe.de/tags/hero h2000+.html
http://4pda.ru/forum/index.php?showtopic=384509&st=140&p=16917723&#entry16917723
http://chinamobiles.org/downloads.php?do=file&id=760 - main rom i modded i think
http://www.4shared.com/rar/GXGsjWuQ/zopo_USB_Drivers.html
Other tutorials i made:
http://forum.xda-developers.com/showthread.php?p=37729457#post37729457
OTHER FILES:
COPY ME TO THE 2GIG INTERNAL SD NOT EXTERNAL.zip
HERO H2000+ Rooting (OTHER MODS)
Sdcard2 to sdcard1 permanent mounting swap mod guide below
This guide is useful so your external sd card you have to physically put into the mobile your self will be able to be used as a storage for apps to be installed directly to, which is normally only possible if you use annoying apps like app2sd which are just a huge inconvenience.
ANYWAY right click this file and save it onto your phone or computer to copy to your phone http://www.cactuz.net/files/zp100/vold.fstab
once you load up your phone using a file manager with root permissions copy the file and replace it with the one installed onto the phone.
(SYSTEM/ETC/VOLD.FSTAB)
restart your phone and you're done!
edit:
Just added the VOLD.FSTAB into a .zip incase it's removed in future.
Here or attached at bottom also
---
Remove 3 button virtual keys + use mute key as back (the key above the volume keys)
This will help you have a bigger screen view, more authentic iphone feel, and basically remove useless buttons.
Steps
1. First download ((THIS)) or the attached KEYREMAP.zip at the bottom of this post.
2. attach your phone via USB then copy the KEYREMAP.zip to your phones sdcard.
3. Unzip the file there you will get a folder called KEYREMAP, once you have done that inside that folder there will be 2 more folders
- MODDED (COPY AND PASTE THE SYSTEM TO SYSTEM)
- ORIGINAL (COPY AND PASTE THE SYSTEM TO SYSTEM)
-Disconnect your phone now.
4. Using an explorer (explorer or rootexplorer on your phone) go to the folder MODDED (COPY AND PASTE THE SYSTEM TO SYSTEM) then copy the folder "system" to the folder "system" at the main (ROOT) directory of your phone and replace the already exisiting files.
5. restart your phone and you are done
edit: Changed modded keymap due to system drop down menu button disappearing, fixed so now you can have a drop down menu button and still remove the 3 virtual buttons at the bottom
Sources:
http://forum.xda-developers.com/showpost.php?p=34865298&postcount=11 - REMOVE 3 BUTTON GUIDE
http://forum.xda-developers.com/showpost.php?p=9399440&postcount=1 - KEYREMAPPER TOOL TO HELP CHANGE MUTE KEY
INFO: /system/usr/keylayout/mtk-kpd.kl / MUTE key = key113 / system\build.prop / ro.bird.control.naviBar=true - persist.sys.naviBar=true - ro.naviBar.height=54
Does this wipe my phone
Will using this method wipe anything on my phone???
When i did it anything on the external sd card was safe, everything else got nuked
Hi !!
This guide seems to be the one I was waiting for (I've already managed to root my H2000+ but I don't have RW access to /system)
Download link is soooo slow any mirror on Dropbox or faster download sites ?
Thanks !
I installed the SUPER ROOT SYSTEM ACCESS with SP Flash tool and all is OK !!
Root with Read/Write access for /SYSTEM
Thanks a lot
this has not wipe my phone ! I still have my apps and my launcher (ilauncher) installed
Back camera is still working too
It's not that bad, i added some more mods i think i'm done now, got everything i wanted to do to my phone, hope this guide helps people and me incase i forget or lose these mods in future, which is the main reason i did it :')
it works,
lol this may sound stupid but yeah,I did the root and it was successful but the screen flickers badly now,i need some help.
did you try to wipe data/factory/dalvik caches and reinstall the Rom + root procedure ?
I worked nice for we without any problem
Maybe you have a specific version of the H2000+ with some weird video drivers ? new device out of the factory with new hardware ?
Hmm ok,I'll try that,if I do all those wipes would things in my phone memory dissappear?lol(just started this stuff).Yeah probably its my hardware,I dont think its the root either.Thanks anyways.
regis59 said:
did you try to wipe data/factory/dalvik caches and reinstall the Rom + root procedure ?
I worked nice for we without any problem
Maybe you have a specific version of the H2000+ with some weird video drivers ? new device out of the factory with new hardware ?
Click to expand...
Click to collapse
Finally i Rooted
Hello my friends.
After one month on trying at my free time finaly today i rooted my H2000+.
I did not lost anything from my contacts or programs that i had before. My Wifi,Camera - front and back,Bluetooth are working fine.
The only think that hapens different today, was that when i did load the Scatter file in flash tool then his screen filled with lines of files that it going to use. All the other times that i was trying to falsh my phone there was only the line with the Scatter file. I do not know why but all the other times the loading of the Scatter file from the flasher was unsuccessful.
Thanks a lot.:good:
So the link you posted from dino direct the phone is out of stock from them anyways, however there is a phone the Changjiang A5000 it seems to be the identical model just different name to the Hero 2000+ I have seen around it's suppose to be the upgraded model of the H2000+ not sure what true is there about that, but it it possible in your opinion that this root method may work? Theoretically that is if everything is the same. I don't have the phone yet but when/if I do i will see if i can disassemble a little to see if i can find similar markings to the H2000+
Hi.
I followed the tutorial to root my hero h2000+ phone and the key remapping tutorial. The root tutorial worked fine for me but the key remapping one not. When i remap the keys, home button just doesn´t work as intended, it looks like it works as DPAD_UP and the MUTE button(original mapping) just doesn´t do anything. I tried Keynumbertracker to know the key numbers and change the mtk-kpd by myself but i totally messed up and had to go back to original config . If anyone can help me, please these 3 buttons are hurting my eyes!!!
(sorry about my english )
Hello, this method is valid for this kernel?
(Kernel: Linux 3.0.13 vers test @ test-virtual-machine # 1 SMP PREEMPT Thu Dec 20 20:41:06 CT 2012)
thanks¡¡
So I would like to say that this does in fact work for the changjiang a5000 phone, the custom modded zip as well, seems the changjiang is identical as i thought it might be
Can anyone confirm this working on the Changjiang A5000?
Compatible?
Does this guide works with Windows 8? - Because i've tried rooting once and somehow my speakers were screwed up and I had to sent it back for repair o__o''
Also which Android version is this? Still 4.0.4? - Because I heared this Android version has a bug of running the battery low much faster than normal :/.
very nice rom and tutorial
liamguest said:
HERO H2000+ Rooting (OTHER MODS)
Sdcard2 to sdcard1 permanent mounting swap mod guide below
This guide is useful so your external sd card you have to physically put into the mobile your self will be able to be used as a storage for apps to be installed directly to, which is normally only possible if you use annoying apps like app2sd which are just a huge inconvenience.
ANYWAY right click this file and save it onto your phone or computer to copy to your phone http://www.cactuz.net/files/zp100/vold.fstab
once you load up your phone using a file manager with root permissions copy the file and replace it with the one installed onto the phone.
(SYSTEM/ETC/VOLD.FSTAB)
restart your phone and you're done!
edit:
Just added the VOLD.FSTAB into a .zip incase it's removed in future.
Here or attached at bottom also
---
Remove 3 button virtual keys + use mute key as back (the key above the volume keys)
This will help you have a bigger screen view, more authentic iphone feel, and basically remove useless buttons.
Steps
1. First download ((THIS)) or the attached KEYREMAP.zip at the bottom of this post.
2. attach your phone via USB then copy the KEYREMAP.zip to your phones sdcard.
3. Unzip the file there you will get a folder called KEYREMAP, once you have done that inside that folder there will be 2 more folders
- MODDED (COPY AND PASTE THE SYSTEM TO SYSTEM)
- ORIGINAL (COPY AND PASTE THE SYSTEM TO SYSTEM)
-Disconnect your phone now.
4. Using an explorer (explorer or rootexplorer on your phone) go to the folder MODDED (COPY AND PASTE THE SYSTEM TO SYSTEM) then copy the folder "system" to the folder "system" at the main (ROOT) directory of your phone and replace the already exisiting files.
5. restart your phone and you are done
edit: Changed modded keymap due to system drop down menu button disappearing, fixed so now you can have a drop down menu button and still remove the 3 virtual buttons at the bottom
Sources:
http://forum.xda-developers.com/showpost.php?p=34865298&postcount=11 - REMOVE 3 BUTTON GUIDE
http://forum.xda-developers.com/showpost.php?p=9399440&postcount=1 - KEYREMAPPER TOOL TO HELP CHANGE MUTE KEY
INFO: /system/usr/keylayout/mtk-kpd.kl / MUTE key = key113 / system\build.prop / ro.bird.control.naviBar=true - persist.sys.naviBar=true - ro.naviBar.height=54
Click to expand...
Click to collapse
very nice rom and tutorial.I´ve installed rom everything good except the rear camera photos are blurry. Do you know how to fix?
Best regards
rt1010 said:
very nice rom and tutorial.I´ve installed rom everything good except the rear camera photos are blurry. Do you know how to fix?
Best regards
Click to expand...
Click to collapse
Personally friend, the camera is dirt, It might be 8MP but it's the lowest standard sorry. I only really got this phone because of it being super light weight so i could jog and stripped it off programs just about last a days use.
Work for me
liamguest said:
Personally friend, the camera is dirt, It might be 8MP but it's the lowest standard sorry. I only really got this phone because of it being super light weight so i could jog and stripped it off programs just about last a days use.
Click to expand...
Click to collapse
Many Thanks
It work for me, now my back camera work again! and root.
Thanks
Do you have a IOS rom that work with this guide?
Hi all,
I'd like to politely ask for your help with adding Google Play to my friend's tablet which unfortunately doesn't provide this app in factory setting.
First of all I'd like to mention that I've searched here before (and other sources over the internet as well) and found many threads with similar issues. Still I was unable to get everything working because of some problems that I'm not able to solve as I'm still just a user... Unfortunately it seems that each device is unique and requires a little different stuff to reach the goal.
So here's some basic information about the device:
Maxell Maxtab C8
Android 4.0.4
Kernel version: 3.0.8+
Here's what I was able to do so far:
Successfully rooted the device
Successfully set -rw to /system (using the "Mount /system (-rw / -ro)" app
I've tried many various Google Play installers including:
Android Market_install_files.zip
PlayStore_v4.6.17.apk found somewhere here in the forums
And about 5 more other without any success. Result is that Google Play is there but it doesn't work - I mean the icon has been added, Gmail account has been "assigned" to it during its first run and then every time I try to run Google Play there occurs an error saying that "Google Play stopped working" and it simply won't run. I also tried the simple solution with "Android-Market_install_files" package (4 apps) - as I found out it's the official way how to use Google Play on devices where it's not preinstalled. Still it didn't work as well - again ended up with the same error (stopped working). But there is maybe some kind of problem with the installation because two of four .apk files included in the "Android Market_install_files.zip" package cannot be installed as the device tells me that this app cannot be installed because of the conflicting signature (I found more about this here: http://stackoverflow.com/questions/...g-package-by-the-same-name-with-a-conflicting). I'm using files signed by Google. Advices are to firstly uninstall the original apps and then install these but I'm not able to uninstall as I can't find them. Guess these are some kind of system apps and I'm not sure where to find them exactly. Still no luck even using Root Explorer. These apps are called "OneTimeInitializer-signed.apk" and "GoogleServicesFramework-signed.apk". I think maybe Google Play from this package could work but the problem is caused by the device which doesn't overwrite the original apps (because of the signature).
Currently I've also found GApps Manager (http://forum.xda-developers.com/showthread.php?t=2589167) - I think this might work but I'm not able to test it at all. Simply I can't find how to get this Maxell tablet into recovery mode to find the "install from zip file" option.
Interesting is that there is no "Phonesky.apk" file in the device's memory...
Sorry for my post being soooo long but I'd like to provide as many additional information as possible.
Could you please give me advice how to install GApps on Maxell Maxtab C8 device or any other solution?
This could look easy for many of you but I'm working on it over two weeks now and I'm really clueless, even more when there are users confirming that Google Play works with this device. So I hope you're be so glad to help. Any help will be highly appreciated! Thanks!
With kind regards
PJ
Some info, since you have root, you can simply move .apk to your /system/app folder.
Also you had stated there is a conflicting issue with the same type of signature, this is because there is already an existing file of the same source.
To uninstall this .apk it usually located in the following folder(s).
- /system/app
And
- /system/priv-app
Just select and delete it. Reboot the device. And move your new files into /system/app and reboot. Make sure you also move Ann app called "Google Play Services.apk or GP will not start
Great things come in small packages.
Re:
Hi krishneelg3,
many thanks for your answer. Your advice looked really easy and reasonable but it didn't work.
I deleted all required .apk files from /system/app. Maxell tablet doesn't have /system/priv-app folder. Then I copied all the GApps files to corresponding folders in the tablet (/system/app, /system/etc, /system/framework, /system/lib). Then the setup wizard started but when I tried to confirm the setup guide touching the green Android icon it did nothing. After restarting the tablet I didn't see the setup wizard app any more. Tried about 5 times in a row from the beginning (copied the original files from the backup back to tablet, then replace them with the new ones from GApps) and always ended up with the same result.
There's also META-INF folder included in the GApps package. It seems to contain some certificates but I'm not sure what to do with it or where to copy these files. Could this be causing the problem?
Thank you very much.
PJ
I would like to tell you that, the GApps package is supposed to flashed via recovery.
The META INFO contains scripts to install and also certs
So if you have a custom recovery available for your device flash the custom recovery img and if you already have it then just flash it via recovery.
Sorry for the delay... I didn't manage how to switch the device to recovery mode. I tried many solutions reported to work for this device but they didn't for me. Some tested, some not because apparently my knowledge is user-level. To be honest after over 3 weeks trying I gave up.
But thanks for your effort.
Regards
PJ
Dear Friends,
About to pull a trigger on an AT&T LG G4, can someone give me a short answer, ASAP?
Is it possible to have permanent Root and Xposed on the AT&T variant WITHOUT ridiculous bugs like a "green dot" in the camera of the phone? (what does the green dot even mean? It's on every picture? Is it a watermark? Just on the GUI?)
If possible, how? And should I buy the phone?
Appreciate any QUICK responses, about to buy now! Thanks so much in advance!
I just bought the G4 a couple of days ago. I was able to root, but there is no twrp or xposed as far as I know. I also don't have the green dot and everything is working fine!
Thanks for the quick response, my friend. Can you share the method/thread/image you used to Root?
I think you can install Xposed without TWRP via FireFlash? Can someone please confirm?
Thanks guys!
Just got my G4 two days ago. You can root and you can install Xposed with FireFlash. Root requires pushing a rooted version of whatever software version you are currently running. If you can't find one you can inject root into your own system.img using Ubuntu. After root get FireFlash and the right xposed zip and be patient, it can sit black screen, appearing dead for 20-30 minutes. Over all not too hard. Took me a couple hours from The un-boxing to Xposed. Definitely do it. The green dot on camera comes from the PR system.img. I'd stay clear of that. Everything is working great on mine!
@Nowak4G - Thanks bud, that's what I read too. Can you point me to the guide and img file you used that worked for you? I doubt I'd prefer the Ubuntu way...
One other question... Is there a way/app/Xposed module that's kind of like G3TweaksBox for us? Letting us change the Status bar icon colors and toggle colors?
I highly doubt themes work for us since we can't Flash them without custom recovery?
Thanks again!
GravityBox works for status bar stuff and yeah here are the threads I used. Good luck bud!
http://forum.xda-developers.com/showthread.php?p=62028519
http://forum.xda-developers.com/g4/general/lg-g4-100-root-success-directives-root-t3180586
http://forum.xda-developers.com/showthread.php?p=62664473
I'm not totally sure what stuff can and can't be flashed using FireFlash. But for applying icon themes with Xposed I use this module, Unicon:
https://drive.google.com/file/d/0B1nrydqmmOBUdFoyV0FBLUM1OVE/view?usp=docslist_api
I've had my LG G4 rooted and running Xposed with a lot of modules enabled.
If the phone you buy is on the 10G software version (and want to stay on that version), you should be able to root it following the method in the LG G4 Low Effort Root thread. Follow it to the dot and enjoy partial freedom.
If the phone you buy is on 10I, there is a rooted image floating around. So you could take the 10I update (or make sure your phone's on the 10I version), and root it using the Low Effort Root method.
I would also recommend the following:
1. keeping a copy of your untouched fresh system image in your internal memory (as early as possible after buying the phone). In case of a bad flash you have something to possibly go back to - otherwise you'll end up with the PR ROM and the green dot. The method and commands to extracting the system image is very similar to rooting, except instead of dd'ing into the system partition from SD, you do the opposite (from system partition to SD)
2. disabling system apps and system updates using the debloater tool and a tutorial here on the forums
Regarding flashing files via recovery, I usually extract the files and place them in the correct directory with the right permissions. Usually most files use 0644 permissions, but I would first check the existing permissions with ES File Explorer.
Hello @Nowak4G and @mu3g,
Guys thank you for your response. I can confirm that the seller I bought the phone from took the 10l upgrade. I have little to no experience rooting locked bootloader phones, and I have to be honest, I am more confused than I have the answers. Now that I have confirmed that I will end up with 10l update, can you guys give me a noob boost and give me step by step on how to root, Xposed, and possibly back up my stock image, since I do NOT want to end up with the PR build, with the green dot, in case things go wrong?
Am I correct that the right answer to my problem is, Low Effort Root with the floating 10l rooted img file, located here: https://drive.google.com/file/d/0B54ceS-n3ZAiaVAxMkJFLXNMYmM/view?pli=1
Please help me out guys, would even appreciate more if we can maybe connect on Google Hangouts for some dynamic help? Please let me know and thank you again for your wonderful so far !
Yes, exactly. Use the floating around 10I rootedsystem.img with the Low Effort Root instructions. But definitely keep a unrooted system.img on the internal storage as a backup. Instructions are in the LER thread. Just read carefully and follow the steps and you should be fine. All copy and pasting.
You have the correct 10I rooted system img file. I would recommend following the LER steps and backing up the system image for 10I (see post 2 of the LER thread). This would give you the stock image for later use. Then follow the LER steps to the dot using the rooted system image file you have from the google drive link. The LER thread has pretty clear instructions on backup and flashing system image files for the G4. Just make sure to rename your downloaded file as "system.rooted.h81010i.img" and use it in the command...the file name here is the most important!
Thank you guys, couple of follow up questions:
1. Do I run the backup command to copy my Non Rooted image, right after the step that gives us the DIAG Port Number? Or do I do it after the "id" step?
2. The generated back up, I assume will be done as an .img file in the root of my phone, correct? I assume I just back this up on my computer and/or External HD?
3. This is the scariest step. When I am running the step for flashing the rooted img, I need to rename the downloaded file to, "system.rooted.h81010i.img" as @mu3g recommended? Why not, "system.rooted.h81010m.img" for example?
4. I just use the exact file name we determined above for my downloaded rooted 10l image file, in the flash command when following the LER guide? Exactly that file name, correct?
Thank you again for all your help and excuse me for my continuous noobness!
Answers:
1. Run the backup command in Step 7 of the LER root ("Run the command specified in the section below titled 'Commands to Run' to flash the rooted system image.") <<---replace the commands to run with the command to backup your unrooted clean system image to your internal memory ---- if you compare the commands, it will become obvious on how the data is being moved (pushed or pulled from the phone).
2. The generated backup will be on the root of the internal memory of the phone. Yes, you can then move it to your computer or any other location for safekeeping AFTER you've booted your phone up properly - don't do any of this while you're still in the LER state.
3. I just gave you a recommendation on the name..you can name the rooted system image file whatever you want - you can even leave it as the way it is....just make sure to use the EXACT file name for the image in the commands to run (also 10I, 10M etc. are software version numbers..I'm not aware of a 10M version being released for AT&T. In any case, just use the EXACT file name for the rooted image.
Thank you @mu3g! I think I am now ready to go through the process myself with confidence.
I am, however, still a bit confused about the file name of the rooted image that I will be flashing. If the phone already has 10l installed, and I leave the name of the rooted image intact, that is, "system.rooted.h81010l" would the phone still accept/get tricked into, thinking that it's getting an "update"? Or did you mean that the file name could literally be anything like, "filename.img" and if the commands match it, all will be installed correctly? As in, when the system boots, it will have all the correct build and software information with it being a 10l update and etc?
Please forgive the annoying, detailed questions, but I want to not mess this up, since every guide triple emphasizes the importance of the command being absolutely right! Thank you!
You can literally name it blahblahblah.img as long as you use blahblahblah.img in the commands to run for the rooted system image. The file naming scheme has nothing to do with the acceptance or rejection of a system image. When you're in the bootloader mode ready to download files (which is the mode for LER), you can inject any file into any partition, anywhere on the phone...it's just whether the phone can use it or not properly and whether or not it ends up being a brick
Your file name for the system has nothing to do with the build number showing on the phone after booting up.
EDIT: The only reason I gave you that file naming scheme is because you don't seem to be too comfortable with the command line, thats all..that way you could copy paste the command from the LER guide and just replace "g" with "i" - that's all..if you're good with the command line and careful, you'll be fine..just make sure the file name is correct..you can't get much else wrong.
Understood brother, just needed that clarity. I am not an absolute noob with cmd line, but you know how it goes when you're rooting your phone, the perpetual fear of an expensive paperweight!
I cannot find the thanks button here, wish I could, so I could thank you over and over and @Nowak4G, but either way, thank you so so much @mu3g!!
good luck!
How did it go? Were you able to go through with it?
While the green dot does usually appear on 810 phones running the PR KDZ, I have heard reports of it on some 815 ...its pretty random. I just did a warranty exchange for my 810 so I will likely be staying on the ATT software.
Hi Guys, wanted to update this thread with my results...:
I successfully rooted on H810l (AT&T) with 0 issues, following the Low Effort Root. Per the recommendations of the process, I also backed up my Stock, Unrooted, .img file for restoration to Stock, if it were needed. Well, I might be moving on from this phone and need to return to stock. Can someone advise the exact steps/commands to return to stock using the unrooted .img file I backed up before pushing the rooted .img? And can you confirm that you did this successfully as well?
I would really appreciate it! Thank you!
I have not done it myself, but if you uninstall all your root apps completely, make sure to enable any and every disabled app you may have (like for example AT&T apps etc.) using the debloater software and then follow LER to install the stock image on it, it should come back to bone stock. Remember, the key here to to ensure that no root apps exist on the phone - I guess SU will get wiped out, but its better to do it clean. And secondly, any disabled apps need to be re-enabled for a smooth process. These are just my $0.02...so proceed with caution.
My device
(IPRO SENSEI FI)
(OS : KITKAT)
(ROOTED"Using kingoroot but I change to supersu") (ORIGINAL ROM NO CUSTOM)
(STOCK RECOVERY)
(NO HAVE ORIGINAL BACKUP OR Etc. T_T )
If you need more information Ask me.
My problem is Bootloop "Or you have another name, because I do not understand", just stop on logo but it still can go into recovery mode.
The story before the events bootloop or whatever name this problem, So as I recall before this incident I edit files and install Tweaks build.prop with applications My pimp and try other features, it works, but when I restart my device. You know what happened. when just stopped in my logo I does not do anything just to wait so that I fell asleep and when I woke up I realized this a bootloop Or what ? I do not know his name.
At that time I was just doing the usual way way., list.
(Wipe data / Factory reset)
(Wipe cache partition)
(reboot system now)
but no change
(Restore user data)
(backup user data)
(Reboot again)
Still same
(Apply update from ADB - I do not have a pc)
(Apply update from sdcard - No have ORIGINAL ROM, BACKUP ROM, CUSTOM ROM Etc.)
(Apply update from cache - I do not understand what this)
Just information There is writing on my recovery mode "Android System Recovery <3e> ALPS.KK1.MP7.V1" I do not know what this is but I show in case you need it.
Just info :
"I have submitted my problem is on the web and social media owned IPRO but no response, I also have to ask in the thread "is concerned about this issue but no response. I do not know if I really make this thread in the forum Q & A if any anyone please notifications where should I post this thread, I hope anyone can help me here, if no input on how to make this a better thread again please write your comment"
I think your reading if this type of problem?
Is it still could be improved?
Installing custom rom whether other devices can fix this? What is this due to file damage build.prop?
How to fix it?
Can you tell tutorial to solve this problem?
If you told me to look for tutorials on the internet what keywords for this problem?
What is correct I asked here or I OOT?
What do I need to make this thread or just my neighbor asking questions like this course in every thread that said key bootloop?
You do not have to answer all of them just answer that you know or your own statement to me, I am newbie please guidance, Sorry in advance, and thanks afterward
Nano.nano said:
My device
(IPRO SENSEI FI)
(OS : KITKAT)
(ROOTED"Using kingoroot but I change to supersu") (ORIGINAL ROM NO CUSTOM)
(STOCK RECOVERY)
(NO HAVE ORIGINAL BACKUP OR Etc. T_T )
If you need more information Ask me.
My problem is Bootloop "Or you have another name, because I do not understand", just stop on logo but it still can go into recovery mode.
The story before the events bootloop or whatever name this problem, So as I recall before this incident I edit files and install Tweaks build.prop with applications My pimp and try other features, it works, but when I restart my device. You know what happened. when just stopped in my logo I does not do anything just to wait so that I fell asleep and when I woke up I realized this a bootloop Or what ? I do not know his name.
At that time I was just doing the usual way way., list.
(Wipe data / Factory reset)
(Wipe cache partition)
(reboot system now)
but no change
(Restore user data)
(backup user data)
(Reboot again)
Still same
(Apply update from ADB - I do not have a pc)
(Apply update from sdcard - No have ORIGINAL ROM, BACKUP ROM, CUSTOM ROM Etc.)
(Apply update from cache - I do not understand what this)
Just information There is writing on my recovery mode "Android System Recovery <3e> ALPS.KK1.MP7.V1" I do not know what this is but I show in case you need it.
Just info :
"I have submitted my problem is on the web and social media owned IPRO but no response, I also have to ask in the thread "is concerned about this issue but no response. I do not know if I really make this thread in the forum Q & A if any anyone please notifications where should I post this thread, I hope anyone can help me here, if no input on how to make this a better thread again please write your comment"
I think your reading if this type of problem?
Is it still could be improved?
Installing custom rom whether other devices can fix this? What is this due to file damage build.prop?
How to fix it?
Can you tell tutorial to solve this problem?
If you told me to look for tutorials on the internet what keywords for this problem?
What is correct I asked here or I OOT?
What do I need to make this thread or just my neighbor asking questions like this course in every thread that said key bootloop?
You do not have to answer all of them just answer that you know or your own statement to me, I am newbie please guidance, Sorry in advance, and thanks afterward
Click to expand...
Click to collapse
I edit files and install Tweaks build.prop
Click to expand...
Click to collapse
more than likely, it is not booting because you made some bad edits to the build prop. i see this happen a lot.
you will need to find a stock firmware for your device and install it back to fix the problem.
use search terms like "(your device name) return to stock" to try and locate the files.
bweN diorD said:
more than likely, it is not booting because you made some bad edits to the build prop. i see this happen a lot.
you will need to find a stock firmware for your device and install it back to fix the problem.
use search terms like "(your device name) return to stock" to try and locate the files.
Click to expand...
Click to collapse
Thanks for your suggestions and answers, Before I made this thread I have searched from internet Stock firmware or stockrom for my device but I never found it, Is there any other way than to install stock rom or firmware to fix my device, or install a custom rom firmware or install other devices can be made in alternative
Nano.nano said:
Thanks for your suggestions and answers, Before I made this thread I have searched from internet Stock firmware or stockrom for my device but I never found it, Is there any other way than to install stock rom or firmware to fix my device, or install a custom rom firmware or install other devices can be made in alternative
Click to expand...
Click to collapse
you can try searching for a custom rom, that should fix it.
other than that, with no stock firmware, i dont see any way you could fix it.
no, you cant use files from another device, unless it specifically says its ok for your device (very rare, but happens occasionally)
bweN diorD said:
you can try searching for a custom rom, that should fix it.
other than that, with no stock firmware, i dont see any way you could fix it.
no, you cant use files from another device, unless it specifically says its ok for your device (very rare, but happens occasionally)
Click to expand...
Click to collapse
Thank you for your prompt response.
Similarity such as what should I look for when taking custom rom or files from other devices?
Nano.nano said:
Thank you for your prompt response.
Similarity such as what should I look for when taking custom rom or files from other devices?
Click to expand...
Click to collapse
look for it to say directly, it can be used on your device. thats the only way.
bweN diorD said:
because you made some bad edits to the build prop.
Click to expand...
Click to collapse
So there will be plenty of experiments,
CMIIW.
If this error in build.prop can I fix it with this way?:
-Take the backup file build.prop.bak with ADB
-Then Edit it by removing the code that previously I input
-And I input back into the system folder in my device with ADB
-And delete files that are in init.d
What a way as it could to improve my device, because I think if it's just damage build.prop file.
And if I use a custom rom whether he would change the system information such as kernel, android version, and whether he will change the code in the file build.prop and What it will also transform the tweaks in the init.d folder or even add to the pile? I think if a custom rom working to add code or tweaks both in build.prop or init.d I think it will worsen, CMIIW, because I think if true custom rom works like that then it is not a good solution
Nano.nano said:
So there will be plenty of experiments,
CMIIW.
If this error in build.prop can I fix it with this way?:
-Take the backup file build.prop.bak with ADB
-Then Edit it by removing the code that previously I input
-And I input back into the system folder in my device with ADB
-And delete files that are in init.d
What a way as it could to improve my device, because I think if it's just damage build.prop file.
And if I use a custom rom whether he would change the system information such as kernel, android version, and whether he will change the code in the file build.prop and What it will also transform the tweaks in the init.d folder or even add to the pile? I think if a custom rom working to add code or tweaks both in build.prop or init.d I think it will worsen, CMIIW, because I think if true custom rom works like that then it is not a good solution
Click to expand...
Click to collapse
1. i have no idea what CMIIW means
2. yes, if you have an original copy of the build prop or can remove edits from the current one, and can replace with adb, that would be good.
3. i would try fixing one thing at a time to see what actually caused the issue. init may or may not need to be fixed.
4. custom rom would clean and replace the entire system including kernel, so it should fix the issue. however, this is your choice, its not a bad option, just a different one.
bweN diorD said:
1. i have no idea what CMIIW means
2. yes, if you have an original copy of the build prop or can remove edits from the current one, and can replace with adb, that would be good.
3. i would try fixing one thing at a time to see what actually caused the issue. init may or may not need to be fixed.
4. custom rom would clean and replace the entire system including kernel, so it should fix the issue. however, this is your choice, its not a bad option, just a different one.
Click to expand...
Click to collapse
CMIIW is Correct Me If I'm Wrong.
Finally, I have two ways for the try, the title and content of this thread may be changed if it is successful.
Thank you for helping me
Thank you for patiently explained
Now I know what to do,
thank you for your participation
thank you very much :good:
no problem