Related
This is my first post, so here goes. I have been reading all day after following the guide on the developers forum on unlocking, rooting. Everything went well, it is unlocked, cwm flashed, and rooted. However, rootcheck comes back with "this device does not have proper root access." I did some reading and found out i would have to do more to get a "full root." Superuser is installed and i can use a root browser so I am guessing i have a limited root....
Does anyone have suggestions? Really want to get this done before flashing any custom roms. If it helps, i had 4.1.1 JB before all of this. Suggestions on roms to flash would help, i read i should only flash a rom based on JB. I dont know if its related but i have been unable to do a backup with CWM...results in error.
I hope provided pertinent info. Thanks in advance.
bobrebn3 said:
This is my first post, so here goes. I have been reading all day after following the guide on the developers forum on unlocking, rooting. Everything went well, it is unlocked, cwm flashed, and rooted. However, rootcheck comes back with "this device does not have proper root access." I did some reading and found out i would have to do more to get a "full root." Superuser is installed and i can use a root browser so I am guessing i have a limited root....
Does anyone have suggestions? Really want to get this done before flashing any custom roms. If it helps, i had 4.1.1 JB before all of this. Suggestions on roms to flash would help, i read i should only flash a rom based on JB. I dont know if its related but i have been unable to do a backup with CWM...results in error.
I hope provided pertinent info. Thanks in advance.
Click to expand...
Click to collapse
Drop CWM... download/flash TWRP (team win recovery partition) i call them TWiRP, lol
But, with CWM, it just stood still for 30min?! i tried 3 times...nothing
flashed over the alternate recovery from TWRP, and whalA! i can do backups
plus the TWRP gui is ALOT more user friendly, and alot more options.
go here, http: //teamw.in /project /twrp
on the right, top, choose your device...
its the same way as with CWM and FastBoot..
But...
I still cant get ROOT either, busybox SAYS, rooted, but SU and Titanium backup say no root, so does RootExplorer...
so im stuck at that part...
im running, JB 4.1.1
my steps i did:
downloaded/installed asus unlocker tool
followed the directions to install cwm/TWRP ( i chose TWRP, cause CWM is a POS with this tablet)
ran/flashed that root-signed.zip, it said SUCCESS
rebooted..
it said, Optimizing Apps 1 of 140
then loads fine, but like you its givng me LIMITED root access...
**************************** UPDATE ***********************************
This method i just did and got Rooted successfully on the UNLOCKED version of Asus JellyBean 4.1.1
Now we will root the tablet
7) Copy Superuser-3.2-RC3-arm-signed to the internal storage of your tablet. then reboot into the bootloader again.
8) This time you need to select the RCK icon with volume up to enter the recovery image.
9) In recovery flash Superuser-3.2-RC3-arm-signed and reboot into the system
10) Install Supersu from Google Play
11) Open up Supersu, it will ask you to update the binary, choose yes.
12) Now your tablet should be rooted
== Part 4 - Remove the Bloatware ==
Check second post
== credits ==
- eyeballer for TWRP recovery
- untermensch for CWM recovery
- sparkym3 for his automated rooting toolkit
- Redefined301 for his guide
Click to expand...
Click to collapse
original posting:
http:// forum.xda-developers.com /showthread.php?t=1845377
****************************************************************************************
like i said, i JUST did this and it worked!
Now, RootExplorer,Titanium backup,RootChecker,SU, they all now see i have 100% root access
*p/s
do not use TitaniumBackup for restoring...use TWRP (or CWM) TB screws crap up...
its best to use it for Restoring Apps, or Cleaning Davilik Cache..etc, but DO NOT use it to restore system files/structures...
cool
CyberdyneSystems said:
Drop CWM... download/flash TWRP (team win recovery partition) i call them TWiRP, lol
But, with CWM, it just stood still for 30min?! i tried 3 times...nothing
flashed over the alternate recovery from TWRP, and whalA! i can do backups
plus the TWRP gui is ALOT more user friendly, and alot more options.
go here, http: //teamw.in /project /twrp
on the right, top, choose your device...
its the same way as with CWM and FastBoot..
But...
I still cant get ROOT either, busybox SAYS, rooted, but SU and Titanium backup say no root, so does RootExplorer...
so im stuck at that part...
im running, JB 4.1.1
my steps i did:
downloaded/installed asus unlocker tool
followed the directions to install cwm/TWRP ( i chose TWRP, cause CWM is a POS with this tablet)
ran/flashed that root-signed.zip, it said SUCCESS
rebooted..
it said, Optimizing Apps 1 of 140
then loads fine, but like you its givng me LIMITED root access...
**************************** UPDATE ***********************************
This method i just did and got Rooted successfully on the UNLOCKED version of Asus JellyBean 4.1.1
original posting:
http:// forum.xda-developers.com /showthread.php?t=1845377
****************************************************************************************
like i said, i JUST did this and it worked!
Now, RootExplorer,Titanium backup,RootChecker,SU, they all now see i have 100% root access
*p/s
do not use TitaniumBackup for restoring...use TWRP (or CWM) TB screws crap up...
its best to use it for Restoring Apps, or Cleaning Davilik Cache..etc, but DO NOT use it to restore system files/structures...
Click to expand...
Click to collapse
CyberDyne
Thanks. I just flashed the TWRP recovery...I really like the gui. I have a question though...the superuser3.2 file you said to flash...where do i find that? I'm up to that point. Thanks again, for your help. Also, another question...is it correct that I have to only install roms based on official ASUS JB 4.1.1 ? I'm really unclear on that stuff. If i flash another rom will it undo what I just did in flashing TWRP? I'm getting a little confused between flashing these recoveries and flashing roms...help
CyberdyneSystems said:
Drop CWM... download/flash TWRP (team win recovery partition) i call them TWiRP, lol
But, with CWM, it just stood still for 30min?! i tried 3 times...nothing
flashed over the alternate recovery from TWRP, and whalA! i can do backups
plus the TWRP gui is ALOT more user friendly, and alot more options.
go here, http: //teamw.in /project /twrp
on the right, top, choose your device...
its the same way as with CWM and FastBoot..
But...
I still cant get ROOT either, busybox SAYS, rooted, but SU and Titanium backup say no root, so does RootExplorer...
so im stuck at that part...
im running, JB 4.1.1
my steps i did:
downloaded/installed asus unlocker tool
followed the directions to install cwm/TWRP ( i chose TWRP, cause CWM is a POS with this tablet)
ran/flashed that root-signed.zip, it said SUCCESS
rebooted..
it said, Optimizing Apps 1 of 140
then loads fine, but like you its givng me LIMITED root access...
**************************** UPDATE ***********************************
This method i just did and got Rooted successfully on the UNLOCKED version of Asus JellyBean 4.1.1
original posting:
http:// forum.xda-developers.com /showthread.php?t=1845377
****************************************************************************************
like i said, i JUST did this and it worked!
Now, RootExplorer,Titanium backup,RootChecker,SU, they all now see i have 100% root access
*p/s
do not use TitaniumBackup for restoring...use TWRP (or CWM) TB screws crap up...
its best to use it for Restoring Apps, or Cleaning Davilik Cache..etc, but DO NOT use it to restore system files/structures...
Click to expand...
Click to collapse
Awesome...it worked! I found the .zip file you mentioned and flashed it with TWRP, installed supersu and it all worked. If someone could answer the remainder of my question about which roms to flash, I would appreciate it. Thanks again CyberDyne!
bobrebn3 said:
Awesome...it worked! I found the .zip file you mentioned and flashed it with TWRP, installed supersu and it all worked. If someone could answer the remainder of my question about which roms to flash, I would appreciate it. Thanks again CyberDyne!
Click to expand...
Click to collapse
flash any rom, thats made for the tablet, the rom will be based off the recent os,like jelly bean,just gutted,ripped and optimized.
there are several, hydro, which is like stock,just performance enhanced, black jellybean, optimized for other stuff.
just research the differences...and read the reviews...the users might have issues that havrnt been worked out yet.
to gain root access to the files and delete system apps, *buy* Root Explorer.
then change a folders view from, r/o to r/w, becareful what u delete.
ALWAYS BACKUP BEFORE MESSING AROUND!!
ANYTHING else?
thanks
CyberdyneSystems said:
flash any rom, thats made for the tablet, the rom will be based off the recent os,like jelly bean,just gutted,ripped and optimized.
there are several, hydro, which is like stock,just performance enhanced, black jellybean, optimized for other stuff.
just research the differences...and read the reviews...the users might have issues that havrnt been worked out yet.
to gain root access to the files and delete system apps, *buy* Root Explorer.
then change a folders view from, r/o to r/w, becareful what u delete.
ALWAYS BACKUP BEFORE MESSING AROUND!!
ANYTHING else?
Click to expand...
Click to collapse
Thanks again for your help. I completed my backup in a couple minutes, then used titanium backup for the apps. I will research the roms you mentioned and others. You solved all my problems...transformer related problems that is....have a good day.
TF700?
Hey guys, I have the same problem as OP and the subsequent poster only that my device is a TF700, can you guys tell me if this method works for the infinity?
CyberdyneSystems said:
flash any rom, thats made for the tablet, the rom will be based off the recent os,like jelly bean,just gutted,ripped and optimized.
there are several, hydro, which is like stock,just performance enhanced, black jellybean, optimized for other stuff.
just research the differences...and read the reviews...the users might have issues that havrnt been worked out yet.
to gain root access to the files and delete system apps, *buy* Root Explorer.
then change a folders view from, r/o to r/w, becareful what u delete.
ALWAYS BACKUP BEFORE MESSING AROUND!!
ANYTHING else?
Click to expand...
Click to collapse
As far as I know, you can only flash custom JB ROMS that are based off the JB bootloader. Once you did the OTA upgrade to JB, the bootloader was updated as well. If you try to flash any ROMS that are based off the ICS bootloader, you're going to brick your tablet. That's what I keep reading. I'm still on a locked tablet, but I read everything on the forums.
CyberdyneSystems said:
Drop CWM... download/flash TWRP (team win recovery partition) i call them TWiRP, lol
But, with CWM, it just stood still for 30min?! i tried 3 times...nothing
flashed over the alternate recovery from TWRP, and whalA! i can do backups
plus the TWRP gui is ALOT more user friendly, and alot more options.
go here, http: //teamw.in /project /twrp
on the right, top, choose your device...
its the same way as with CWM and FastBoot..
But...
I still cant get ROOT either, busybox SAYS, rooted, but SU and Titanium backup say no root, so does RootExplorer...
so im stuck at that part...
im running, JB 4.1.1
my steps i did:
downloaded/installed asus unlocker tool
followed the directions to install cwm/TWRP ( i chose TWRP, cause CWM is a POS with this tablet)
ran/flashed that root-signed.zip, it said SUCCESS
rebooted..
it said, Optimizing Apps 1 of 140
then loads fine, but like you its givng me LIMITED root access...
**************************** UPDATE ***********************************
This method i just did and got Rooted successfully on the UNLOCKED version of Asus JellyBean 4.1.1
original posting:
http:// forum.xda-developers.com /showthread.php?t=1845377
****************************************************************************************
like i said, i JUST did this and it worked!
Now, RootExplorer,Titanium backup,RootChecker,SU, they all now see i have 100% root access
*p/s
do not use TitaniumBackup for restoring...use TWRP (or CWM) TB screws crap up...
its best to use it for Restoring Apps, or Cleaning Davilik Cache..etc, but DO NOT use it to restore system files/structures...
Click to expand...
Click to collapse
Hey I have a similar problem for k3 note (k50a40) can you help me with that
Thanks
Update : Problem Solved
I've been flashing ROMs, recoveries etc for years on every android device I've had, from Samsung to nexus, HTC. Everything. This is my first Motorola and I'm having a lot of problems.
Unlocked the boot loader, flashed TWRP but wouldn't backup my stock ROM so put on Pholz recovery and it wouldn't backup either.
Tried to install C-Rom after the usual wipes and just sticks at boot screen. Tried Tweakone ROM I think its called and same problem.
Any ideas? I have the XT1032
I know about restoring to factory but what I'm asking is, is there anything specific I'm doing wrong? I'm quite an experienced flasher. Research is showing me how to recover the phone but what's gonna stop it happening again
Sent from my Nexus 5 using Tapatalk
A lot of users report issues not being able to flash rom's on 4.4.2 kitkat.
A fix is to downgrade to 4.3, then flash roms.
I dont know why. I bought my device upgraded to 4.4.2 already, and i can flash roms with no issues.
Search the forum for the topic and you will find the info you need.
Roshi69 said:
I've been flashing ROMs, recoveries etc for years on every android device I've had, from Samsung to nexus, HTC. Everything. This is my first Motorola and I'm having a lot of problems.
Unlocked the boot loader, flashed TWRP but wouldn't backup my stock ROM so put on Pholz recovery and it wouldn't backup either.
Tried to install C-Rom after the usual wipes and just sticks at boot screen. Tried Tweakone ROM I think its called and same problem.
Any ideas? I have the XT1032
I know about restoring to factory but what I'm asking is, is there anything specific I'm doing wrong? I'm quite an experienced flasher. Research is showing me how to recover the phone but what's gonna stop it happening again
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
It wont backup saying what error?
Twrp just said 'failed' in red writing after the data backup I think. And philz touch said something along the lines of Not being able to write a file into the \clockworkmod folder.
I bought the device with 4.4.2 on it and followed the guides after reading up about the problems etc but TWRP 2.7.0.0 had a lot of reports that everything was working on it so went ahead with it
Sent from my Nexus 5 using Tapatalk
Ya that's strange because philz works great for me. Do you have a USB otg to try an external backup?
Sent from my XT1032 using Tapatalk
I got the phone booted again by following a guide and flashing a stock rom.
Installed Philz recovery again and still getting the backup error. it says: E: Error while backing up boot image!
So understandably i am now scared to flash another rom in case i get a boot loop again.
*update* Strangely i flashed TWRP via CWM, rebooted into TWRP 2.7.0.0 and performed a backup successfully.
Roshi69 said:
I got the phone booted again by following a guide and flashing a stock rom.
Installed Philz recovery again and still getting the backup error. it says: E: Error while backing up boot image!
So understandably i am now scared to flash another rom in case i get a boot loop again.
*update* Strangely i flashed TWRP via CWM, rebooted into TWRP 2.7.0.0 and performed a backup successfully.
Click to expand...
Click to collapse
Why dont you use Clockwork mod recovery for flashing Rom. I have flashed 10 Roms with that and all are backed up with out any problems. TWRP has no official support for moto g, and instead of all that why don't you try Cyanogenmod ?
(sorry if my english is not perfect)
Hello,
I have exactly the same problem with my XT1032.
Bootloader unlocked, CWM (6.0.4.7) successfully installed and backup done with no issues.
But custom roms won't load...
CM11 is stuck at "bootloader unlocked warning screen" and SlimKat is stuck at slimkat logo.
I never had such problems on my Nexus..
Please help me, I don't know what's going on
TheSkweed said:
I have exactly the same problem with my XT1032.
Bootloader unlocked, CWM (6.0.4.7) successfully installed and backup done with no issues.
But custom roms won't load...
CM11 is stuck at "bootloader unlocked warning screen" and SlimKat is stuck at slimkat logo.
Click to expand...
Click to collapse
Same here. It may be possible to downgrade to 4.3 (see here), but would it then be possible to flash a 4.4.2-based custom ROM ? I'm not sure.
Heres the steps I took.
*******Before device was stuck at bootloop*******
1. Bought phone (XT1032)
2. unlocked boot loader
3. Rooted
4. Flashed Philz Recovery (wouldn't backup rom)
5. Flashed TWRP and CWM with same issue.
6. Flashed 2 ROMs to try it (TweakyOne + C-Rom, Both wouldn't boot. and tried on all recoveries.
********Steps after being stuck at bootloop*******
1. Followed this amazing guide here (https://www.youtube.com/watch?v=laU6NQ0LxR0)
2. Set up the stock ROM again
3. Flashed TWRP 2.7.0.0 via Fastboot
4. Backup worked successfully
5. installed CM11 and setup successfully
6. installed Lego rom just to assure myself (currently running this ROM)
I know this is no solution at all but just wanted to share my steps to see what maybe fixed my phone. possibly the stock 4.2.2 rom I flashed was the solution. Maybe the original factory ROM that came on the phone was the issue?
I've had an LG E970 running the stock ROM for about a year and decided to try out CM. I'm new to this, but I did some research and went ahead and rooted the phone, and then installed ClockworkMod. That went smoothly, so I tried to install CM through CWM and it appeared to work until it finished booting up and led me to the encryption PIN screen. My PIN from the stock ROM won't open it. CWM can't mount the encrypted data partition to wipe it.
I can boot to CWM or the CM encryption screen. I tried doing a restore on CWM but keeping getting MD5 errors. I haven't had any luck finding the stock ROM anywhere online, I tried an LG tool to get the kdz but it kept giving me error messages when I entered the serial number. I used Titanium to backup everything beforehand, but I can't figure out how to use the files to restore the old ROM. I can put files onto the SD card with my computer, but don't know if that'll be any help. I tried using the ADK to connect to the phone in fastboot, but the phone doesn't show up when I enter the fastboot devices command. Will an older version of CM thats based on the same version of Android the phone was encrypted with be able to open the data? I've tried researching this but everything I've found suggests going about it in different ways and nothing I've tried has worked.
If anybody could give me any help I'd appreciate it.
You may wish to refer to [GUIDE][E970]Using LG Flash Tool To Flash .tot Files {Alternate To LGNPST}[WIP]
Of note to you is Post #8 If you still have issues, you can post on that thread as well.
I followed that guide, but got stuck because the LG Flashtool is identifying my phone as a Nexus 4 and not allowing me to install the E970 files. I think the phone ID changed because the CM version I downloaded was converted from the Nexus ROM. I was able to flash an earlier version, but it had the same problem. Do you have any suggestings for a ROM with the correct phone ID? Is there any other ROM that might be able to decrypt the stock Android encrypted data?
Thanks!
I fixed it!
By plugging my SD card into the computer, I was able to add new ROMs to it and flash them in CWM. I was trying out different ROMs, hoping one would show up as the right phone model in LG Flashtool, and I found one for LG Official Kitkat 4.4.2 Stock. It was able to decrypt the data and now my phone is usable again. I'll revert to the stock recovery, wipe the phone (including encryption) and then start over with CM.
Here's a link to the ROM in case anybody else has this problem later:
http://forum.xda-developers.com/showthread.php?t=2771440 - Thread
http://level99.nighthorsemedia.com/geeb/LG-KK-4.4.2-Fixed.zip - Download Link
Thanks!
Hey there fellas,
Being a part time/spare time "mod wanna be", I've successfully modded different cell phones every now and then.
Lately I bought, 2nd hand, a XT925 running as it was in the attached screen shot + unlocked BL, rooted and CWMR touch 6.0.4.4.
Since the phone was rebooting itself kinda often, since I've been told that Epinters builds was JBBL based and also based on the phone info 3.0.x Kernel, I thought it was ok to flash a stock ROM and after that, upgrade to KK via OTA.
I've flashed the JB 4.1.2 BR Retail via fastboot and everything went ok. I let it boot, ran through configurations and just made myself sure that basic options were working ok. The OTA pops up, I downloaded it and proceed to install...an error pops up while it was somewhere around 25-30% of the flashing process.
I talked to the previous owner and he said that he went to CM because the cell never was able to install OTAs, there was always errors on the installation process.
With that in mind, I proceed to research some tutorials about alternative methods on how to install KK OTA.
I've found one here and another one on other forum, which was more suited to my needs since I'm at Brazil. Both are suggesting the same method:
Requirements:
1.Stock/unmodified JB4.1.2
2.Stock recovery
3.Unrooted
4.Bootloader unlocked
Since I met all the requirements, I proceeded to give it a try.
The next steps was:
1.Download a JB custom recovery and flash it via fastboot
2.Correct OTA installed on the external SD card
3.Install the OTA via custom recovery
4.install KK custom recovery
5.Root
Steps 1 and 2 were ok but again, while attempting to flash the OTA there was errors. Since Ive tried the whole process several times with different files, doing MD5 checksums, with different custom recoveries, I may divide the errors in 2 separate categories:
Error category 1:
While verifying current system, different .apks has unexpected contents. Status 7 as the final status error.
Since I was battling with this for 36 hours non stop, just before going to have some sleep, I decided to format internal SD since I thought maybe there was some leftovers from previous installations.
Apparently everything went ok and i proceed to flash the another SBF this time (I was trying the JB4.1.2 BR Retail). Since I've heard one of the latest KK kernel was the DE I decided to give it a try. Downloaded it from the official motorola page and flahed it via fastboot. This time I didn't stayed on front of PC because I needed some coffee! When I cam back, everything seemed to be ok since there was a message at the end saying so.
Phone rebooted and JB4.1.2 was installed, basic configurations done and OTA downloaded through the cell phone. Installation failed again! With this OTA fail already in mind, I previously downloaded the DE OTA from a post here and had it downloaded already to the external SD card. Installed JB custom recovery and proceed to flash the OTA...it failed again!
There was almost 40 hours without sleeping so my brain didn't allowed me to keep going.
After 10 hours of rest, I was back to keep fighting....and there comes the next type of errors:
Error category 1 +2 +3+4
1+2+3 because after several attempts on the whole process, the error 1 popped up some times, there was, as well, a new error (error 2) while flashing the OTA via custom recovery (please see the attached screen shot).
Finally, the errors 3+4 (actually the error number 3 is the one I'm concerned the most about). Its sort of a bootloader menu error message and the error number 4 shows up while trying to flash SBF and or Custom recoveries and they are as follow
Bootloader menu error message:
10.98(*) (sha-5b608bc, 2012-11-23 19:48:44)
eMMC Info: Size16GB
Device is UNLOCKED. status code: 3
Fastboot reason: Boot menu selected
USB Connected
downgraded security version
Update gpt_main version failed
Pre flash validation failed for gpt
Fastboot error messages while trying to flash SBFs and or custom recoveries
<bootloader> Variable not supported!
target max-download-size: 30MB
FAILURED (remote failure)
My conclusions/doubts are as follows:
1.Does that internal SD format has something to do with the bootloader menu errors message? I feel it has started to show up after I did it...maybe it's just coincidence though!
2.The .xml editing part still making me feel something suspicious about the Fastboot error messages.
3.Does that Epinters CM11 KK 4.4.4 Kernel 3.0.101-11512-g9511901 has something to do with that scaring Bootloader error message about downgrading?
...or is it just me being a noob?!?
However, If you came this far, congrats! I really truly respect your commitment to help people and your passion for computer/programming/Android related things!
People like this are the real responsible for bringing men out of caves all the way through the days we live in and as far as to reach the moon!
Now if you help me to get out of this and reach my goal of having KK4.4.4 official DE(or any newest other one which works where I live), rooted, unlocked BL, I'll be more than happy to ask for your permission to invite you to some beers!
Cheers!
RMarques said:
Hey there fellas,
Being a part time/spare time "mod wanna be", I've successfully modded different cell phones every now and then.
Lately I bought, 2nd hand, a XT925 running as it was in the attached screen shot + unlocked BL, rooted and CWMR touch 6.0.4.4.
Since the phone was rebooting itself kinda often, since I've been told that Epinters builds was JBBL based and also based on the phone info 3.0.x Kernel, I thought it was ok to flash a stock ROM and after that, upgrade to KK via OTA.
I've flashed the JB 4.1.2 BR Retail via fastboot and everything went ok. I let it boot, ran through configurations and just made myself sure that basic options were working ok. The OTA pops up, I downloaded it and proceed to install...an error pops up while it was somewhere around 25-30% of the flashing process.
I talked to the previous owner and he said that he went to CM because the cell never was able to install OTAs, there was always errors on the installation process.
With that in mind, I proceed to research some tutorials about alternative methods on how to install KK OTA.
I've found one here and another one on other forum, which was more suited to my needs since I'm at Brazil. Both are suggesting the same method:
Requirements:
1.Stock/unmodified JB4.1.2
2.Stock recovery
3.Unrooted
4.Bootloader unlocked
Since I met all the requirements, I proceeded to give it a try.
The next steps was:
1.Download a JB custom recovery and flash it via fastboot
2.Correct OTA installed on the external SD card
3.Install the OTA via custom recovery
4.install KK custom recovery
5.Root
Steps 1 and 2 were ok but again, while attempting to flash the OTA there was errors. Since Ive tried the whole process several times with different files, doing MD5 checksums, with different custom recoveries, I may divide the errors in 2 separate categories:
Error category 1:
While verifying current system, different .apks has unexpected contents. Status 7 as the final status error.
Since I was battling with this for 36 hours non stop, just before going to have some sleep, I decided to format internal SD since I thought maybe there was some leftovers from previous installations.
Apparently everything went ok and i proceed to flash the another SBF this time (I was trying the JB4.1.2 BR Retail). Since I've heard one of the latest KK kernel was the DE I decided to give it a try. Downloaded it from the official motorola page and flahed it via fastboot. This time I didn't stayed on front of PC because I needed some coffee! When I cam back, everything seemed to be ok since there was a message at the end saying so.
Phone rebooted and JB4.1.2 was installed, basic configurations done and OTA downloaded through the cell phone. Installation failed again! With this OTA fail already in mind, I previously downloaded the DE OTA from a post here and had it downloaded already to the external SD card. Installed JB custom recovery and proceed to flash the OTA...it failed again!
There was almost 40 hours without sleeping so my brain didn't allowed me to keep going.
After 10 hours of rest, I was back to keep fighting....and there comes the next type of errors:
Error category 1 +2 +3+4
1+2+3 because after several attempts on the whole process, the error 1 popped up some times, there was, as well, a new error (error 2) while flashing the OTA via custom recovery (please see the attached screen shot).
Finally, the errors 3+4 (actually the error number 3 is the one I'm concerned the most about). Its sort of a bootloader menu error message and the error number 4 shows up while trying to flash SBF and or Custom recoveries and they are as follow
Bootloader menu error message:
10.98(*) (sha-5b608bc, 2012-11-23 19:48:44)
eMMC Info: Size16GB
Device is UNLOCKED. status code: 3
Fastboot reason: Boot menu selected
USB Connected
downgraded security version
Update gpt_main version failed
Pre flash validation failed for gpt
Fastboot error messages while trying to flash SBFs and or custom recoveries
<bootloader> Variable not supported!
target max-download-size: 30MB
FAILURED (remote failure)
My conclusions/doubts are as follows:
1.Does that internal SD format has something to do with the bootloader menu errors message? I feel it has started to show up after I did it...maybe it's just coincidence though!
2.The .xml editing part still making me feel something suspicious about the Fastboot error messages.
3.Does that Epinters CM11 KK 4.4.4 Kernel 3.0.101-11512-g9511901 has something to do with that scaring Bootloader error message about downgrading?
...or is it just me being a noob?!?
However, If you came this far, congrats! I really truly respect your commitment to help people and your passion for computer/programming/Android related things!
People like this are the real responsible for bringing men out of caves all the way through the days we live in and as far as to reach the moon!
Now if you help me to get out of this and reach my goal of having KK4.4.4 official DE(or any newest other one which works where I live), rooted, unlocked BL, I'll be more than happy to ask for your permission to invite you to some beers!
Cheers!
Click to expand...
Click to collapse
thats a lot to process lol
i have a 926 not a 925 and know nothing about the specifics of updating.
however, you have and may have made some universal errors.
- when flashing with rsd a couple partitions can not be flashed equal or downgraded. these are tz/trustzone and gpt/partitioning file. therefore these lines need to be edited out of the xml unless you are upgrading. thats why you have the fastboot error, from trying to downgrade the partition table. any correct flash, updating or removing the partition and tz lines, should make this go away.
- as far as the update files. if they are true update pulls and not modified files made to flash in custom recovery, they need to be flashed in stock recovery, not cwm. without seeing the post the files came from, i cant say which you have, but the poster should have identified which they are.
there isnt much else i can comment on, but hope that helps get you on the right path.
Thanks for stopping by, reading and replying!
I'll try to touch it point by point, saying so:
1. I have flashed several times attempting to succeed on this, all of them I've used Fastboot.
2. I didn't knew, nor read nothing anywhere about the partitions that can not be flashed equal or downgraded anywhere I researched before I decided to proceed.
3. I've got what you said and I pretty much agree with that, in fact, i was pretty sure about that there was some mistake(s) in the .xml.
4. "Fastboot error, from trying to downgrade the partition table. Any correct flash, updating or removing the partition and tz lines, should make this go away." Are you talking about the following error?
"downgraded security version
Update gpt_main version failed
Pre flash validation failed for gpt"
...if so, thank God, it scared me to dead!
- As for the update files, I followed the tutorials and it was clearly stated that they was meant to be flashed using a JBBL custom recovery. http://forum.xda-developers.com/showthread.php?t=2760840&page=60 (Post #599)
Thanks again and from where I'm at atm, any kind of input helps a lot!
RMarques said:
Thanks for stopping by, reading and replying!
I'll try to touch it point by point, saying so:
1. I have flashed several times attempting to succeed on this, all of them I've used Fastboot.
2. I didn't knew, nor read nothing anywhere about the partitions that can not be flashed equal or downgraded anywhere I researched before I decided to proceed.
3. I've got what you said and I pretty much agree with that, in fact, i was pretty sure about that there was some mistake(s) in the .xml.
4. "Fastboot error, from trying to downgrade the partition table. Any correct flash, updating or removing the partition and tz lines, should make this go away." Are you talking about the following error?
"downgraded security version
Update gpt_main version failed
Pre flash validation failed for gpt"
...if so, thank God, it scared me to dead!
- As for the update files, I followed the tutorials and it was clearly stated that they was meant to be flashed using a JBBL custom recovery. http://forum.xda-developers.com/showthread.php?t=2760840&page=60 (Post #599)
Thanks again and from where I'm at atm, any kind of input helps a lot!
Click to expand...
Click to collapse
yes, that error should be fixed by any good flash.
if for some reason its not, get "mfastboot" and flash the most current version you have ever had on the phone and *** flash the partition file first, followed by the rest of the files. mfastboot can write equal partition files. if the partition file flash fails, you dont have the newest one.
hopefully re-flashing without the partition file works, then you wont need to mess with mfastboot.
looks like that is a modified ota file as you stated, sorry but i cant help with whatever the issue is with that part.
Solved!
http://forum.xda-developers.com/showthread.php?p=56598858
Sent from my Razr HD/Unlocked KKBL/TWRP2.8.1.0/Latest CM11 M11 Nightly/ART Runtime
Hey all,
I had a thread a while ago regarding how to get out of bootloop, now I seem to have a different issue so I wanted to make a new thread to refine the details of the problem.
These are the current settings, the only ones that work, but the rom has to be kept in airplane mode to avoid errors displaying
Phone = Huawei Honor 6 16GB (H60-L02) FDD-LTE
Bootloader = Unlocked
Recovery = CWM 6.0.5.1 exFAT
Rom = MIUI v4.9.6 (miui_hw60_slydermi_4.9.6_6c22a194a4_4.4.zip) Downloaded from the official miui website
I have tried to use the honor6 multi tool to flash different recoveries (official/stock) and none work except the above CWM version.
I have also tried to flash different roms, mainly from needrom.com and what i could download from this chinese forum
Note i have also been following tutorials in this thread
in an attempt to get back the stock rom, mainly the two sections
3 Button Restore not working and full restore method
I am unsure what step to take next, everything puts my phone into a bootloop, i would happily go back to stock recovery/rom but again they cause bootloops too
my last guess is it might have something to do with Build & Local Prop files? im not entirely sure what they are or how to use them.
thanks for any help offered!
1) Spent time to flash literally every single stock recovery offered by the Honor 6 Multi-tool,
- All EMUI 2.3 recoveries worked except for B120SP03
- Not a single EMUI 3.0 recovery worked, i tried every stable, developer and custom recovery.
2) I picked up an error in CWM, when i goto mounts and storage and try to format /cust
it gives me the following error:
Code:
Formatting /cust...
E:format_volume: make_extf4fs failed on /dev/block/platform/ff1fe000.dw
mmc0/by-name/cust
Error formatting /cust!
3) Could someone please inform me to what exactly build.prop and local.prop do, and how i can restore them? (I assume just push somewhere using adb)
I think my next plan of action is to push some of the stock prop files and then flashing their recoveries to see if that will get them to work.
Feel like a crazy person replying to my own thread but its helping me keep all information in one place and might help someone that is going through the same stuff.
After running through which recovery worked and which didnt (Still strange that some do and dont)
I flashed the highest version i could which is B121SP06 recovery using the honor 6 multi tool.
After that I downloaded a fresh copy of the B121SP06 rom, extracted the SYSTEM.img and flashed it
This booted and got me into android which is great, but its not having fun updating now.
It prompted me to update and gave me the OTA update from B121SP06 to B307SP03
I downloaded it and it reset into recovery and tried to flash it, the progress bar got less than 2% then it would stop and give me a big red exclamation mark with Software install failed! and the only option to shutdown system now
I also tried updating through the HiSuite and it again failed.
managed to install B310 with a little trickery
Using the multi tool, i performed the unbrick method with B121SP06 image files
Then i had the B310 update.app in the dlaod folder and performed the 3 button recovery method
it worked perfectly and i now have B310 on my phone, although updates are still not working, so i might have to manually download OTA's to update them.
Also recoveries that weren't working before like TWRP are.