Hi,
I've got some trouble to get a proper root mod on my phone. After i used some of the hints which can be found in this forum i didn't managed to get it running.
History of my mod-trys:
I got it running until i patched my stock Rom to the latest version via fota. (the feature pack for German roms)
Then i tried to go back to a stock Rom here at the forum - but with little success. I installed it but important not able to get the root mod running without errors.
This is a screenshot of superuser:
{
"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"
}
If i try to update i am getting an error.
Sadly i don't know what to do now to get this fixed. Iused many fresh installs / cleanup etc but everytime i install the update.zip via recovery - its messed up.
gesendet mit Tapatalk 2
try to flash CWM with ODIN.. do not use adb shell because it needs root.. the try flash another ROM.. IT'S VERY RISKY.. I'M NOT RESPONSIBLE IF YOUR PHONE BRICKED
i've got cwm at the moment installed. As far as i understood the "root / unroot" thread it's not recommended to use this while rooting via recovery.
i used cwm to create a backup of my system and i rolled back it many times - so - thats working fine.
But my problem is that i don't find a suiteable custom rom for me - because it has to be "as stock as possbile". Meaning - i'm doing much development and testing with that phone - so it's not good if the mod can do things which i can't do with a stock rom. (Rooting is ok - i can handle that "mod" - if it works )
But i'm not firm enough with android core development to fix the root problem right now. Are there any manuals to use the "USB Debugging" Shell? I'm able to use that, too.
OR - if exsists - is there any _german_ stock rom out including the "value pack" addon? I just found a stock rom which is missing that. I guess there's coming with the value pack that causes rooting via update.zip going mad
i cant also root mine and i also have the value pack update but before i had the value pack i can still root my phone :CC
Related
Hello, I recently got xperia play, and decided to root my phone for better performance. Just for fun went to youtube and found this:
Then I remenbered this page, and just found few threads: http://forum.xda-developers.com/showthread.php?t=2240285 and http://forum.xda-developers.com/showthread.php?t=1312859.
My phone specs:
{
"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"
}
If I am correct, according to first thread above, I cant root my device and second one is saying that I cant install JB on my device.
AAAAAAAAND... Im totaly confused now and dont know what to do.
Can you be more clear on what exactly are you trying to achieve?
if you wanna root your phone you must enable "unknown sources" inside applications and also under developing you must enable "USB Debuging".
Then plug your phone in the usb while it's turned on normally and execute the run-me in the zerg rush files.
after that you can install rom manager and get a recovery going on,
when you do have a recovery going on you can use it to flash a new rom.
dev639 said:
Can you be more clear on what exactly are you trying to achieve?
if you wanna root your phone you must enable "unknown sources" inside applications and also under developing you must enable "USB Debuging".
Then plug your phone in the usb while it's turned on normally and execute the run-me in the zerg rush files.
after that you can install rom manager and get a recovery going on,
when you do have a recovery going on you can use it to flash a new rom.
Click to expand...
Click to collapse
Ok, I rooted my device, what is rom manager? CM10?
In this thread you will be guided to install a recovery
http://forum.xda-developers.com/showthread.php?t=1437840
It's basically install the apk ask the apk to install a recovery and you're done.
Now you will have theability to boot into recovery mode.
To do so you have to keep pressing volume down as you turn on your device.
You will then be able to proceed to installing custom roms.
You might also wanna research for flashtools from there on.
I unlocked my bootloader and rooted my HTC One X. I have used the ClockworkMod recovery.
I had CyanogenMod 10.2 installed and it ran perfectly fine.
Later on, I downloaded the 'cm-11-20140308-SNAPSHOT-M4-endeavoru.zip' file to install the the CM 11.2
But it seems something terribly has gone wrong.
This error message was shown during installing CM 11.2
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
and it got stuck on this screen after rebooting
Later on I tried flashing the 'boot.img' of CM 10.2 to get back to that ROM, but I encountered this error.
But when I tried installing the 'cm-10.2.1-endeavoru.zip', it was a success, but I am still stuck at the same position.
Please help me restoring the phone back, I dont care if I have to revert back to HTC's Original ROM, as long as the phone is back working.
I am novice at this thing, so please bear with me if I ask some stupid questions.
khepacheley said:
I unlocked my bootloader and rooted my HTC One X. I have used the ClockworkMod recovery.
I had CyanogenMod 10.2 installed and it ran perfectly fine.
Later on, I downloaded the 'cm-11-20140308-SNAPSHOT-M4-endeavoru.zip' file to install the the CM 11.2
But it seems something terribly has gone wrong.
Please help me restoring the phone back, I dont care if I have to revert back to HTC's Original ROM, as long as the phone is back working.
I am novice at this thing, so please bear with me if I ask some stupid questions.
Click to expand...
Click to collapse
First of all if you want to install CM11 you must to use latest CWM from CM11 thread or TWRP2.7 or Philz latest. And now mount sd card copy your sense rom to the card install it, flash the boot img. and you are good to go. After this read again thread for CM11 and how to install and try agin but be shure you read the thread
use the recovery that thommy put in the first page of the cm11 post (or the philz last recovery) it seems that the cmw that you have doesen't support kitkat
Hello everyone and have a Merry Christmas,
I'm trying to update my TWRP recovery because I want to go 100% stock. I'm still running TWRP 2.7.0.2. The most recent version of TWRP is 2.8.3.0.
I downloaded the TWRP manager app from the Play store and easily selected the last available version of the recovery to install.
After downloading the .img file, I get a pop up that looks like this:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
The pop up says: "Be sure that the listed path is correct for your device. An uncorrect check may result in bricking your device. You can't flash a recovery directly on Android on some devices. If you can't flash through Android, please choose a different method".
It looks like a "routine" alert, but nonetheless it sounds very alarming. How can I say if the listed path is the correct one for my device (HTC One M8 unbranded GSM international version)?
Thank you for helping.
why update twrp ? twrp is not stock ! and you can also fastboot flash it. oldskool way
Because the procedure to go stock requires some flashing and it was adviced to have the latest version running.
I'm not such an expert, I'm more the type who tries to read as much as possible before trying anything, and upgrading TWRP was a sort of "pre-step".
Also I'm not very keen to use fastboot: I got that it is great, but it is not very straightfoward for beginners.
The tool from the Play store seemed to do the job pretty good and easily.
Mr Hofs said:
why update twrp ? twrp is not stock ! and you can also fastboot flash it. oldskool way
Click to expand...
Click to collapse
What if I flash a custom recovery over a custom recovery? Is it possible to simply flash it and overwrite an already existing custom recovery?
there is no other way, the recovery will always overwrite the old one. its impossible to run 2 recoveries
{
"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"
}
Be careful: this is for the new 2016 of the P8000, which I believe is only available in Europe. That version is known as "P8000 6.0"
I have been trying to port PhilZ v2 to the new version and although it still has a few bugs/problems, at this point it at least allows you to root your device.
Download (recovery + root):
https://mega.nz/#!kUFBmSDb!RW3sTDPA-imxcNQihCiTfnsXAw_e0Fy-9djliPbxavo
(If you need scatter file, it's attached to this post)
To root:
1. Put Beta-SuperSU.zip on your internal memory
2. Download SuperSU from the Play Store
3. Turn off phone and flash recovery
4. Immediately boot into recovery (don't go into Android first or the recovery will be gone)
5. Choose flash zip from sd card
6. Select the Beta-SuperSU.zip
7. Reboot phone to Android from the menu (if the recovery asks to install root, choose no!)
8. Rooted
The recovery is now probably gone from you phone, because it resets to stock every time you boot into Android. If you like to keep it, rename /system/recovery-from-boot.p to recovery-from-boot.p.bak using ES File Explorer in root mode or something. Then flash the recovery again in SP Flash Tools.
Known bugs for recovery:
- ADB (plugging in cable) crashes recovery
- No access to external SD card, that's why you have to flash root from internal memory
- Touch not working
--
Use at own risk, I'm not responsible for anything.
Fix IMEI on P8000
Thanks to users @FrauHofrat and @ardrift
FrauHofrat said:
With a lot of thanks to user ardrift:
with *#*#6813#*#* entered on the stock dialer you can acess the "IMEI-Tool" which allows you to enter a new IMEI for both SIM cards. The new IMEI stay permanent even after reboot and this also works on 'old' P8000.
first I thought this is a joke but actually it worked - sometimes life can be so easy
Click to expand...
Click to collapse
Emileh said:
Thanks to users @FrauHofrat and @ardrift
Click to expand...
Click to collapse
Dont think it works on blueflame's CM. beliewe he tossed all the MTK stof :crying:
Ported TWRP 3.0.2 from several sources., but touch screen don't work. I've ported for other devices (MT6753,MT6580,MT6582) and never faced this issue. Need help (P8000 6.0)
Like many of you, I also had the problem that the phone had a bootloop after a flash. No matter what I tried, nothing worked. I found and tried this tool xiaomitool from Francesco. With this tool you can flash any rom without bootloop. Please save your data before
Thus tool does a flash completely automatically. You even didn't need TWRP pre-installed on your device
http://www.xiaomitool.com/
All credits goes to Francesco
Xendetor said:
Like many of you, I also had the problem that the phone had a bootloop after a flash. No matter what I tried, nothing worked. I found and tried this tool xiaomitool from Francesco. With this tool you can flash any rom without bootloop. Please save your data before
Thus tool does a flash completely automatically. You even didn't need TWRP pre-installed on your device
http://www.xiaomitool.com/
All credits goes to Francesco
Click to expand...
Click to collapse
Hi,
First, I'd like to thank you for finding the tool and publishing it here.
It's a really handy Application.
After moving around in the app quite a bit, I couldn't find any way to install any custom roms.
All it offers - Miui Global/Beta, Chinese Official/Beta roms and some other tweaks (TWRP, SU etc.)
How to flash any other custom Rom..?
Am I missing something here..?
Please describe.
Thanks in advance.
damnsaif said:
Hi,
First, I'd like to thank you for finding the tool and publishing it here.
It's a really handy Application.
After moving around in the app quite a bit, I couldn't find any way to install any custom roms.
All it offers - Miui Global/Beta, Chinese Official/Beta roms and some other tweaks (TWRP, SU etc.)
How to flash any other custom Rom..?
Am I missing something here..?
Please describe.
Thanks in advance.
Click to expand...
Click to collapse
You have to download the ROM, then go to: "Local ROM file"
{
"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"
}