Yes hi, I just got a new Huawei Mediapad M5, and I tried to purchase a code to unlock the bootloader, but they said the firmware on my tablet is too new, and that I would need to downgrade to a firmware from before July 2018 first. But I don't know how to do that, nor where to find the firmware.
I'm good with tablets so I'll be able to do it, but I need to know how to first. Thank you
Okay so quick update, my m5 is the CMR-W09. I downloaded the c432 version of it and unzipped everything, put in in the sd card root folder, and did the power/vol up/vol down button combo and it failed without even starting.
So I tried several other versions of the firmware that I found elsewhere. Trying things several different ways of doing with each one, and no matter what I tried, which was pretty much every version of the way to do this mentioned in the past two months on the bootloader guide thread, and every single one of them got the same failure message, so I seriously do not know what to do. Please help. What am I doing wrong?
Okay so thank you everyone for all the help you've provided, they said sarcastically. But after three days of trying about a hundred different methods, I have officially given up on trying to downgrade the firmware on my tablet.
I've tried so many different methods listed in the guide on this forum, and other methods I found elsewhere.
I tried multiple firmware versions, of both sht and cmr, and none of them have worked.
I've put the dload folder with everything unzipped inside it and that didn't work, I tried with the zips still zipped inside, nope. I tried the dload folder with nothing in it but the update.app file. That is the only time anything happened by the way. It gets to five percent, and then immediately fails, no matter how many times I try, or how many different firmware's I do said method with, it always fails at five percent.
I even spent 17 dollars to join Easy Firmware so I could get one of the firmware versions they had that I couldn't find anywhere else. And same thing.
So I don't know what it is, maybe the firmware that came preinstalled on my tablet is a newer version that doesn't allow downgrading anymore, that's the most likely thing I can think of anyway. But yeah, it ain't happening for me.
So unless anyone has any words of advice, or an idea on what might be going on, please close this thread for me, it's existence is now pointless.
ElsaReyes said:
Okay so thank you everyone for all the help you've provided, they said sarcastically. But after three days of trying about a hundred different methods, I have officially given up on trying to downgrade the firmware on my tablet.
I've tried so many different methods listed in the guide on this forum, and other methods I found elsewhere.
I tried multiple firmware versions, of both sht and cmr, and none of them have worked.
I've put the dload folder with everything unzipped inside it and that didn't work, I tried with the zips still zipped inside, nope. I tried the dload folder with nothing in it but the update.app file. That is the only time anything happened by the way. It gets to five percent, and then immediately fails, no matter how many times I try, or how many different firmware's I do said method with, it always fails at five percent.
I even spent 17 dollars to join Easy Firmware so I could get one of the firmware versions they had that I couldn't find anywhere else. And same thing.
So I don't know what it is, maybe the firmware that came preinstalled on my tablet is a newer version that doesn't allow downgrading anymore, that's the most likely thing I can think of anyway. But yeah, it ain't happening for me.
So unless anyone has any words of advice, or an idea on what might be going on, please close this thread for me, it's existence is now pointless.
Click to expand...
Click to collapse
Ive downgraded using the comments on this thread https://forum.xda-developers.com/mediapad-m5/how-to/bootloader-unlock-guide-t3781275 and then ive unlocked the bootloader using dc unlocker, to know exacly how to downgrade, read all the comments especially the new of them, do not give it up
Seek and you will be found
THE MAXIMUM POWER said:
Ive downgraded using the comments on this thread https://forum.xda-developers.com/mediapad-m5/how-to/bootloader-unlock-guide-t3781275 and then ive unlocked the bootloader using dc unlocker, to know exacly how to downgrade, read all the comments especially the new of them, do not give it up
Seek and you will be found
Click to expand...
Click to collapse
That's the thing though. I have read through every comment in that thread, and tried every single method listed and not a single one works for me.
The furthest it ever gets is 5 percent and then it fails. So I really don't know what's going on with my tablet. I just won't let me downgrade it.
Do you think you can give me a quick play by play on how you did it?
ElsaReyes said:
That's the thing though. I have read through every comment in that thread, and tried every single method listed and not a single one works for me.
The furthest it ever gets is 5 percent and then it fails. So I really don't know what's going on with my tablet. I just won't let me downgrade it.
Do you think you can give me a quick play by play on how you did it?
Click to expand...
Click to collapse
Keep in mind that you need to downgrade to the last version of yours(e. G. You are in the. 196 then you should downgrade to the. 195 and then.. 193 and not directly from. 196 to. 193
My device is CMR-W09C432 Which is MediaPad M5 10.8inch Only wifi EU version, ive downloaded the same firmware of my device (only full otas) which is called update.zip,
I unzipped it
Put it in the root of your sdcard in dload folder (first create a folder in your sdcard called dload, then put ONLY update.app inside dload folder)
It is going to be like this dload/Update.app
Reboot and press and hold volume buttons and power button at the same time
Thats it
Plz write to me if you need any further assistance, i will be glad to help you as i was at the same position as yours
THE MAXIMUM POWER said:
Keep in mind that you need to downgrade to the last version of yours(e. G. You are in the. 196 then you should downgrade to the. 195 and then.. 193 and not directly from. 196 to. 193
My device is CMR-W09C432 Which is MediaPad M5 10.8inch Only wifi EU version, ive downloaded the same firmware of my device (only full otas) which is called update.zip,
I unzipped it
Put it in the root of your sdcard in dload folder (first create a folder in your sdcard called dload, then put ONLY update.app inside dload folder)
It is going to be like this dload/Update.app
Reboot and press and hold volume buttons and power button at the same time
Thats it
Plz write to me if you need any further assistance, i will be glad to help you as i was at the same position as yours
Click to expand...
Click to collapse
Okay thank you thank you thank you. I haven't yet tried this method as I just saw this message, but it's one I haven't seen before so I'm going to try it and hopefully it'll work. But just have one small question.
My M5 is the CMR-W09C567.
I'm in 190 right now, that's what my tab came as. But using Firmware Finder, the only ones I see before it are 175, 167, and 156. Are those the only ones that came before? Or should I actually be looking for versions like 189, 188 and so on? Just making sure I'm not misunderstanding anything.
ElsaReyes said:
Okay thank you thank you thank you. I haven't yet tried this method as I just saw this message, but it's one I haven't seen before so I'm going to try it and hopefully it'll work. But just have one small question.
My M5 is the CMR-W09C567.
I'm in 190 right now, that's what my tab came as. But using Firmware Finder, the only ones I see before it are 175, 167, and 156. Are those the only ones that came before? Or should I actually be looking for versions like 189, 188 and so on? Just making sure I'm not misunderstanding anything.
Click to expand...
Click to collapse
Sorry for my late answer
First download the full ota mf version 175 as the first attachment shows
Second step is to download the update.zip (2 attachment)
Then unzip the update.zip file and copy paste the update.app inside dload folder at the root of your sdcard
hopefully this step is going to work, BUT BE AWARE THAT IF DOWNGRADE WAS SUCCESSFUL, YOU ARE GOING TO LOSE ALL YOUR DATAS SO MAKE A BACKUP BEFORE DOING IT
Then try to use dc unlocker after putting the usb settings to manufacture mode
THE MAXIMUM POWER said:
Sorry for my late answer
First download the full ota mf version 175 as the first attachment shows
Second step is to download the update.zip (2 attachment)
Then unzip the update.zip file and copy paste the update.app inside dload folder at the root of your sdcard
hopefully this step is going to work, BUT BE AWARE THAT IF DOWNGRADE WAS SUCCESSFUL, YOU ARE GOING TO LOSE ALL YOUR DATAS SO MAKE A BACKUP BEFORE DOING IT
Then try to use dc unlocker after putting the usb settings to manufacture mode
Click to expand...
Click to collapse
Nah see, it still won't downgrade for me, it doesn't make any sense like I said.
I clicked the full ota version of 175 like you said, and on the page that came up, I clicked the word download, and of the three files that showed up, I choose to download just the update.zip
I unzipped the update.zip file and moved the update.app file into the dload folder on the root of my sd card.
And then I turned off my tablet, and held down the vol up, vol down, and power button all at the same time until the device booted into a screen that just had the EMUI logo.
Several phrases flashed by beneath it, before it said it was installing the update, but the update sticks at 5 percent, and after being stuck like that for several seconds, it just gives up and I'm left with the Software Install Failed screen once again.
I just don't get it. Do I need to have the SD Card formatted a certain way? Can there be no other files on it besides the dload folder and update file? Is there a setting I don't have turned on that I need on??
Small update, I just tried flashing an actual update instead of a downgrade, and the same exact thing happened.
I'm starting to think that I'm doing nothing wrong and in actuality it's a problem with my tablet.
ElsaReyes said:
Small update, I just tried flashing an actual update instead of a downgrade, and the same exact thing happened.
I'm starting to think that I'm doing nothing wrong and in actuality it's a problem with my tablet.
Click to expand...
Click to collapse
There is another way to flash, which is should work, download all the 3 files (as the 2 attachment shows) and without unzipping any folder, put them instead of Update.app.
It is going to be like the first attachment (yours should read usa instead of eu)
This method should work
THE MAXIMUM POWER said:
There is another way to flash, which is should work, download all the 3 files (as the 2 attachment shows) and without unzipping any folder, put them instead of Update.app.
It is going to be like the first attachment (yours should read usa instead of eu)
This method should work
Click to expand...
Click to collapse
Nope. Now it doesn't even start to install. It just immediately goes Software install failed the second the EMUI logo shows up.
I really think there just might be something very wrong with my tablet, cause something should have worked by now.
ElsaReyes said:
Nope. Now it doesn't even start to install. It just immediately goes Software install failed the second the EMUI logo shows up.
I really think there just might be something very wrong with my tablet, cause something should have worked by now.
Click to expand...
Click to collapse
Ive heard about a method from TeamMT which allows you to downgrade even with a locked bootloader, keep in mind that you need to install ONLY the version of hisuite that is in the videos description
Take a look here https://youtu.be/xFCLpgGZEJM
If it did not work, try the dns method which is in FirmwareFinder app, you need to change your router dns in order to get the firmware through eRecovery
THE MAXIMUM POWER said:
Ive heard about a method from TeamMT which allows you to downgrade even with a locked bootloader, keep in mind that you need to install ONLY the version of hisuite that is in the videos description
Take a look here https://youtu.be/xFCLpgGZEJM
If it did not work, try the dns method which is in FirmwareFinder app, you need to change your router dns in order to get the firmware through eRecovery
Click to expand...
Click to collapse
Okay I don't know what's going on here, but I downloaded that version of hisuite that it lists. And I followed the instructions on how to connect to it. And it connects, but then immediately disconnects. And then connects again and so on and so on. It just keeps connecting then disconnecting.
I really really really appreciate all the hell your giving me, it means more then you can know, but I'm really starting to believe that there is something wrong with my tablet. One of these methods should have worked by now right?
ElsaReyes said:
Okay I don't know what's going on here, but I downloaded that version of hisuite that it lists. And I followed the instructions on how to connect to it. And it connects, but then immediately disconnects. And then connects again and so on and so on. It just keeps connecting then disconnecting.
I really really really appreciate all the hell your giving me, it means more then you can know, but I'm really starting to believe that there is something wrong with my tablet. One of these methods should have worked by now right?
Click to expand...
Click to collapse
I believe that there is not any kind of problems with your device, it is just you might missed something as all m5s are equals except the vendor which has nothing to do with failing downgrade operations.
Try the DNS method from Firmware finder and this should work as it send the choosed firmware to the eRecovery, for more infos choose (Get and update via eRecovery), this method is supposed to work with all EMUIs (3,4,5 and 8)
Write to me if it worked out
THE MAXIMUM POWER said:
I believe that there is not any kind of problems with your device, it is just you might missed something as all m5s are equals except the vendor which has nothing to do with failing downgrade operations.
Try the DNS method from Firmware finder and this should work as it send the choosed firmware to the eRecovery, for more infos choose (Get and update via eRecovery), this method is supposed to work with all EMUIs (3,4,5 and 8)
Write to me if it worked out
Click to expand...
Click to collapse
Sorry but nope...
I changed the DNS number in the wifi settings to the one it gives. And still when I start into eRecovery, the only update it offers is the latest and not the one I choose...
ElsaReyes said:
Sorry but nope...
I changed the DNS number in the wifi settings to the one it gives. And still when I start into eRecovery, the only update it offers is the latest and not the one I choose...
Click to expand...
Click to collapse
Sorry, i do not have any more infos about this specific situation all i can do is to advice you to reread through the unlock bootloader thread (the one ive sent you before) as i used some advices in the comments section which helped me to do a successful downgrade in order to unlock the bootloader
Try again and again and do not give it up?
THE MAXIMUM POWER said:
Sorry, i do not have any more infos about this specific situation all i can do is to advice you to reread through the unlock bootloader thread (the one ive sent you before) as i used some advices in the comments section which helped me to do a successful downgrade in order to unlock the bootloader
Try again and again and do not give it up
Click to expand...
Click to collapse
Thanks for all your help. But honestly I think it'd be best if I just gave up. I don't want to, but clearly the universe does not want me downgrading this stupid thing.. lol
And as I said, already read through that entire thread and followed every bit of advice in it.
ElsaReyes said:
Thanks for all your help. But honestly I think it'd be best if I just gave up. I don't want to, but clearly the universe does not want me downgrading this stupid thing.. lol
And as I said, already read through that entire thread and followed every bit of advice in it.
Click to expand...
Click to collapse
Through trial and errors you should be able to do it, try rebranding your device to the European version through funkyhuawei
THE MAXIMUM POWER said:
Through trial and errors you should be able to do it, try rebranding your device to the European version through funkyhuawei
Click to expand...
Click to collapse
Just wasted 44 dollars on a pass for the funkyhuawei site and it won't let me rebrand without first being unlocked.
Unlocking my tablet is why I want to downgrade.
Yeah I'm done. I really appreciate all your help, I really do, But I've now spent over 60 dollars trying to get this thing downgraded only to fail every single time, so I'm done.
Related
Phone: LG P500h - ANDROID v 2.2.1 buildnumber FRG83.
Country: Brazil
Anyway, what I know is that i have to downgrade it to 2.2 in order to be able to root. I've looked through a bunch of tutorials on a bunch of websites but there are a few questions i have about the process that isn't answered anywhere i've looked.
Apparently downgrading requires me to get a stock ROM from LG, there is a topic here for that but it does not have the right ROM for my country, i tried a couple codes but they all got me 404.
Can I just flash any standard ROM from, US maybe, will it work?
And if yes, how do I flash it? Apparently you can do that by booting into recovery mode, but to get there you need it to be rooted which I can't do.
I've read about KDZ and downloaded that but... it crashes a lot in my PC (whenever i try the Read Device) it gives me error and closes the program (windows program not responding dialog).
I'm afraid it might crash in the middle of it if i try flashing and that would brick my device.
Is there a simple way to flash a new ROM? Is that the first thing I have to do in order to get a custom ROM say Ubuntdroid? It says I need a new recovery... but for that I need to downgrade first? It's a lot to do... and I don't really get the order in which I should do it all in...
Can somebody post me a little "do this, then do that, then finally do that" so that I can understand it all finally?
Thanks in advance, and sorry for long post, was trying to be as informative as possible.
This shows what happens when I try reading the phone on KDZ... also a little part showing that I got my device to be recognized by windows...
also disabled the LGE modem on device manager, read that if I don't it'll get bricked.
Well it won't let me link the image so... just paste the name together.
www
novasite.com.br
/1.jpg
1. Find a suitable v2.2 stock ROM for flashing (link)
2. Use KDZ to flash it (I am not aware of another tool capable of doing that). Try doing that on a PC running Windows XP (important - that's where you're stuck now and I guess you're using Windows 7).
3. Root your phone - search for "z4root" on Market, install it.
4. Install Custom recovery, which will replace your current (stock) recovery mode (link - you may need to create an account on another forum in order to download).
5. Using Custom recovery you can now install any custom ROM and create nandroid backups to restore your phone to a certain (working) state.
You will have to use KDZ again if you ever want to flash a stock ROM, also losing the custom recovery. But you will have no reason to do that, except if you need to take your phone to some warranty repairs.
Good luck!
NEW PROBLEM: About step 1... i finally found a way to get my country's rom, but... it's.. the same thats on my device right now, it says V10a_02 and thats the same on my phone (the kdz read phone tells me that) so... won't I just be flashing the same 2.2.1 again?
http://csmg.lgmobile.com:9002/swdata/WEBSW/LGP500H/ABRABK/V10A_02/V10A_02.kdz <---- the rom the topic tells me to get.
How do I know what version of android is in that rom? and if i can't, can you link me to a rom that does?
I found one from another country that the guy said is 2.2... but... will it work if i flash that one? does it HAVE to be for my country? also my model is p500h (the h) is it different from the p500 (different as in flashing p500 without h roms on it will kill it?)
As for flashing it...
I think maybe a computer with win xp will do the trick for kdz.
i've found this post today:
http://forum.xda-developers.com/showthread.php?t=944881
is it better to use that than kdz? theres no replies on topic saying "hey it worked" so i'm a little worried, but apart from a few errors it seems to work on my win 7....
i guess the reply would be "i only know kdz, do it with kdz" but i thought i might ask...
Indeed, I have not tried that method and therefore I can't recommend it. At least KDZ is successfully tested. If you are patient enough to wait for some replies either here or in that topic, you may find out if it works. I would recommend it only if you have no other choice, like if you're unable to try KDZ on an XP machine.
In the mean time, I remembered that a newer version of Custom recovery is available (v1.2) - here. But you still need to download a file and read the tutorial from that other forum I mentioned in the previous post.
what about the first part of the post? i think i might have added that after you replied i don't know... asking about the rom i found if it isn't the same i have on my phone. and asking if i can just add another country's one...
edumazieri said:
Phone: LG P500h - ANDROID v 2.2.1 buildnumber FRG83.
Country: Brazil
Anyway, what I know is that i have to downgrade it to 2.2 in order to be able to root. I've looked through a bunch of tutorials on a bunch of websites but there are a few questions i have about the process that isn't answered anywhere i've looked.
Apparently downgrading requires me to get a stock ROM from LG, there is a topic here for that but it does not have the right ROM for my country, i tried a couple codes but they all got me 404.
Can I just flash any standard ROM from, US maybe, will it work?
And if yes, how do I flash it? Apparently you can do that by booting into recovery mode, but to get there you need it to be rooted which I can't do.
I've read about KDZ and downloaded that but... it crashes a lot in my PC (whenever i try the Read Device) it gives me error and closes the program (windows program not responding dialog).
I'm afraid it might crash in the middle of it if i try flashing and that would brick my device.
Is there a simple way to flash a new ROM? Is that the first thing I have to do in order to get a custom ROM say Ubuntdroid? It says I need a new recovery... but for that I need to downgrade first? It's a lot to do... and I don't really get the order in which I should do it all in...
Can somebody post me a little "do this, then do that, then finally do that" so that I can understand it all finally?
Thanks in advance, and sorry for long post, was trying to be as informative as possible.
Click to expand...
Click to collapse
First backup your data, then download a factory ROM, it doesn't matter which version u download, what matters is the version. Make sure that it's 2.2 and not 2.2.1 or 2.2.2. Follow all the below steps without skippin any, no matter how simple or stupid they are.
Link for shipped ROM - http://forum.xda-developers.com/showthread.php?t=865479
Now download KDZ updater and uncompress it
http://www.4shared.com/file/UleS4dP3/KDZ_FW_UPD_EN.html
Install msxml.msi from the uncompressed directory
Charge your battery to almost full state (I'm not sure, but it can be reason if phone doesn't start)
Turn phone off somehow (remove battery etc.)
Install drivers properly
Get rid of all usb drivers like Nokia, microsoft visual ++ run time environments
Install the LG drivers by selecting the update manager from the lg site
Disable LGE Virtual Modem. In your Windows operating system, go to Control Panel > System > Hardware > Device Manager > Modems > Right click on LGE Virtual Modem and click Disable.
Press and keep pressed "Volume up"+"Return" and connect USB cable to phone
Yellow screen with text emergency mode should appeared
Shake the handset (I know, it sounds ... strange, but it helps for ones, so... why don't try it?) UPDATE: Read some quotes on bottom.
Run KDZ_FW_UPD.exe (Has administrator).
Select Type : 3GQCT (I have one report that CDMA mod works too)
Select PhoneMode : DIAG (in case of fail try EMERGENCY, and as last chance use CS_EMERGENCY)
I Recommend do not switch phone off. There was some people, which done it and after they was not be able to turn it on again. If flashing failed, just select some another mode and try it again, again, try shake/connect disconnect, again, again....
In KDZ file : Choose the ROM file you downloaded in the first step
Press Launch software update
Shake the handset (I know, it sounds ... strange, but it helps for ones, so... why don't try it?) UPDATE: Read some quotes on bottom.
Now Root it via Z4root - http://forum.xda-developers.com/showthread.php?t=833953
Then install custom recovery - http://forum.xda-developers.com/showthread.php?t=844483
Then download n flash any ROM of your choice, I wud sugget install Void or LOL.
Edit :- By the time I replied, many have already replied. Anyways you can check my reply too :-D
Mithun.
"it doesn't matter which version u download, what matters is the version."
does that mean it doesn't matter what country or operator the rom is for, as long as it is android version 2.2?
i have one from portugal (not my country) and that one is made for P500 mine is P500H... if that makes a difference i don't know, but i do know that rom is android 2.2. can i flash that one?
i also have one that i got from that topic following the instructions of putting my serial number, it linked me to a rom V10A_02... on KDZ when i try to read my device it says i have V10A_02 too. isn't that the same one i have now? with android 2.2.1? if it is it's very pointless to flash the same rom already in it.
any way to check?
because that is my last doubt ;p
edumazieri said:
"it doesn't matter which version u download, what matters is the version."
does that mean it doesn't matter what country or operator the rom is for, as long as it is android version 2.2?
i have one from portugal (not my country) and that one is made for P500 mine is P500H... if that makes a difference i don't know, but i do know that rom is android 2.2. can i flash that one?
i also have one that i got from that topic following the instructions of putting my serial number, it linked me to a rom V10A_02... on KDZ when i try to read my device it says i have V10A_02 too. isn't that the same one i have now? with android 2.2.1? if it is it's very pointless to flash the same rom already in it.
any way to check?
because that is my last doubt ;p
Click to expand...
Click to collapse
Yes.... you can choose any country. I tried the Australian version. Use the below one http://csmg.lgmobile.com:9002/swdata/WEBSW/LGP500/AAUSBK/V10a_00/V10A_00.kdz
edumazieri said:
what about the first part of the post? i think i might have added that after you replied i don't know... asking about the rom i found if it isn't the same i have on my phone. and asking if i can just add another country's one...
Click to expand...
Click to collapse
As far as my knowledge goes, the LG P500h you have is the same phone as the P500, only branded for Telus. The hardware should be identical, therefore you may use any ROM designed for the P500 family.
The only thing you may miss if you install a ROM not customized for a Brasil (or South America) network operator is the internet acces point name, thus rendering your phone unable to acces the internet trough its data service connection, but only trough WiFi. Nevertheless, the phone's APN can be configured manually, all you need are the correct settings from your mobile operator and you're good to go.
Ok since you guys told me i can go ahead and flash any country ROM i just did and now my device burst into flames and then the flames consumed my apartment.
ok, not. it worked too well actually, i did the kdz procedure on my win 7 anyway, despite the errors when reading device info, and it took like, 1 minute, rebooted, took like 2 minutes on the android screen then it came back, with all my data still there... i thought it didn't do anything but... its now version 2.2
i tried z4root, worked ... got the superuser app and.... i'm happy ^^ thaaaanks!
anyway about the custom recovery thing..
i'm going to install the one in that post you gave me...
but i read something about the best one being clockwork something...
shouldn't i go ahead and install that one?
or can i do everything i need with this one you guys linked?
edumazieri said:
Ok since you guys told me i can go ahead and flash any country ROM i just did and now my device burst into flames and then the flames consumed my apartment.
ok, not. it worked too well actually, i did the kdz procedure on my win 7 anyway, despite the errors when reading device info, and it took like, 1 minute, rebooted, took like 2 minutes on the android screen then it came back, with all my data still there... i thought it didn't do anything but... its now version 2.2
i tried z4root, worked ... got the superuser app and.... i'm happy ^^ thaaaanks!
anyway about the custom recovery thing..
i'm going to install the one in that post you gave me...
but i read something about the best one being clockwork something...
shouldn't i go ahead and install that one?
or can i do everything i need with this one you guys linked?
Click to expand...
Click to collapse
Glad that it worked Install the Amon_RA's recovery!!! Many ROM's for OO won't support clock work I suppose. Amon RA's recovery is neat, I've been using that from the time I had an HTC tattoo.
For your Custom Recovery.... http://androidforums.com/getitnowma...ry-optimus-one-p500-thunderg.html#post1896517
edumazieri said:
anyway about the custom recovery thing..
i'm going to install the one in that post you gave me...
but i read something about the best one being clockwork something...
shouldn't i go ahead and install that one?
or can i do everything i need with this one you guys linked?
Click to expand...
Click to collapse
You can do anything you need with ThunderG. Now that version 1.2 supports backup and restore of ext4 partitons (a feature you don't need if you don't plan on installing a custom ROM... but you will, eventually ), it is complete.
Moreover, in ClockworkMod's first topic says: "This recovery will not allow you to flash every ZIP file". ThunderG does, if you choose to allow flashing of unsigned zip files. Sometimes this is useful.
Peeeeeerfect
Recovery installed, LOL ROM installed, all fast smooth and error-free.
no more screen touch lag, it's soooooo much faster now, overclocked, i have yet to test my emulators but i can only guess they're gonna be at least 150% better lol.
thank you all very much for taking the time to help me ^^
ONE LAST QUESTION: I PLAN ON BUYING A NEW SD CARD, JUST PLUG IT IN AND IT'LL FORMAT THEN CREATE THE NEEDED FILES THEN I INSTALL STUFF BACK ON IT, SIMPLE AS THAT?
Simple as that =D
Although there are some criteria with the sd card or you'll get unmounting problems.
Use a class 4 or higher card
format with fat32
I've never officially tried this method but its apparently supposed to help
allocation unit size: 64kb when you're formatting
edumazieri said:
Recovery installed, LOL ROM installed, all fast smooth and error-free.
no more screen touch lag, it's soooooo much faster now, overclocked, i have yet to test my emulators but i can only guess they're gonna be at least 150% better lol.
thank you all very much for taking the time to help me ^^
ONE LAST QUESTION: I PLAN ON BUYING A NEW SD CARD, JUST PLUG IT IN AND IT'LL FORMAT THEN CREATE THE NEEDED FILES THEN I INSTALL STUFF BACK ON IT, SIMPLE AS THAT?
Click to expand...
Click to collapse
So, how does it goes?!
I´m brazilian too, got a brand new LG Optimus One from ViVo, and a want to know if you´re having any troubles with conections, calls, internet, 3G etc.
OK, id did the flash
I´m afraid that if flash any custom rom, it will break or cause any misfuncition of the 3g service.
Any idea?!
== Updated
Ok, I´ve flashd it with KDZ and the log show´s thats all ok
"14:34:45 : ===FINISHED=== "
BUt its taking like FOREVER to start... almost 30min on android screen. Is this normal?! Should i restart the phone?!
leave it some more time , try shaking it ...
shake trick sometimes helps
Help please..
I did as instructed in the step to step procedures. kdz posted finished but my phone is still at the yellow screen..i did shaking but nothing happens..Is this normal?..SHould i wait..
I have an unrooted HTC Aria (AT&T) that i upgraded to Froyo a couple of weeks ago. I have been using it for a while and i don't like the performance with the new upgrade, it used to be a LOT snappier before.
I would like to know if its possible to revert the phone to Factory Defaults (Eclair 2.1) and where i can get the ROM since HTC is no longer providing it in its website.
I'm not interested in rooting my phone nor custom roms i just want it the way it was at the moment I took it off the box and turned it on for the first time.
If the downgrade is possible I would really appreciate if someone could provide a list of steps to follow to make it happen.
Thanks in advance.
Check out this thread: http://forum.xda-developers.com/showthread.php?t=971119. You can but you will still have the updated HBOOT (Bootloader). You will have to use the ROM linked in post 3 (Original 2.1 Rom)
P.S - Search before starting new threads on the same topic.
http://www.mediafire.com/?cj56c2gfk86k8oe
This is the original ship ROM. I downloaded this back when I first got my phone (first day the Aria was released) and have kept it for future use. This was even before they added the ability to receive OTA updates, so you won't even have to worry about being notified about the 2.2.2 OTA update.
Now, you should be able to just run this and have it downgrade everything (except HBOOT, but that isn't a problem unless you want to root). I haven't actually done it before but it should work.
If it doesn't work, there is another way that will definitely work, but I'll explain that if the need arises. Let me know if you run into any problems.
Theonew said:
Nope. Not possible since you don't want to root your device.
Click to expand...
Click to collapse
It is possible. You can downgrade everything except the HBOOT. (Meaning, he will have the original ROM like he wants but be unable to use Unrevoked, which he doesn't care about.)
drumist said:
It is possible. You can downgrade everything except the HBOOT. (Meaning, he will have the original ROM like he wants but be unable to use Unrevoked, which he doesn't care about.)
Click to expand...
Click to collapse
That post I made was a mistake. That's why I edited it. Sorry I didn't get to change it in time.
Theonew said:
Check out this thread: http://forum.xda-developers.com/showthread.php?t=971119. You can but you will still have the updated HBOOT (Bootloader). You will have to use the ROM linked in post 3 (Original 2.1 Rom)
P.S - Search before starting new threads on the same topic.
Click to expand...
Click to collapse
To be honest the advice from those threads is not really very good anyway. You don't need temp root on your device. There are easier methods that ought to work fine. Namely, just putting the 2.1 RUU zip as LIBEIMG.zip on your SD card. But from what I've read, even just running the RUU should be enough.
(Nevermind, this doesn't work.)
Thanks for you advice, in fact did some research before creating the thread, but all the threads i found were about people who wanted to downgrade to get the root back, so they were either redirected to other threads or were given a lot information not relevant to what i really need.
drumist said:
This is the original ship ROM. I downloaded this back when I first got my phone (first day the Aria was released) and have kept it for future use. This was even before they added the ability to receive OTA updates, so you won't even have to worry about being notified about the 2.2.2 OTA update.
Now, you should be able to just run this and have it downgrade everything (except HBOOT, but that isn't a problem unless you want to root). I haven't actually done it before but it should work.
If it doesn't work, there is another way that will definitely work, but I'll explain that if the need arises. Let me know if you run into any problems.
Click to expand...
Click to collapse
I tried this but for some reason i got a BOOTLOADER VERSION ERROR [140] message. Thanks for your help anyway.
eljuanpelos said:
I tried this but for some reason i got a BOOTLOADER VERSION ERROR [140] message. Thanks for your help anyway.
Click to expand...
Click to collapse
Don't give up yet. This next method should work if that one didn't.
Download this file: http://www.mediafire.com/?ct1ay7t93d8g742
Rename the zip file as LIBEIMG.zip (don't extract it) then place it on your SD card (not in a subfolder).
Then turn the phone completely off, and press VOL DOWN + power to turn the phone back on. It should detect the file after a couple seconds and start flashing it automatically. At this point just be patient for a minute or two, then press VOL UP key to start the update process when it asks you to. After that, be patient while it does everything. It takes about 5 minutes to finish installing everything and will reboot once during the process. After it's done (it will tell you when it's done), the phone will reboot and there will be a scary looking screen but JUST WAIT about 10 seconds and it will boot normally. Then you're good to go.
After you're done with this, make sure to DELETE the LIBEIMG.zip file from your SD card. Otherwise it will ask you every time you go into HBOOT if you want to apply the update.
Good luck.
drumist said:
Don't give up yet. This next method should work if that one didn't.
Download this file:
Rename the zip file as LIBEIMG.zip (don't extract it) then place it on your SD card (not in a subfolder).
Then turn the phone completely off, and press VOL DOWN + power to turn the phone back on. It should detect the file after a couple seconds and start flashing it automatically. At this point just be patient for a minute or two, then press VOL UP key to start the update process when it asks you to. After that, be patient while it does everything. It takes about 5 minutes to finish installing everything and will reboot once during the process. After it's done (it will tell you when it's done), the phone will reboot and there will be a scary looking screen but JUST WAIT about 10 seconds and it will boot normally. Then you're good to go.
After you're done with this, make sure to DELETE the LIBEIMG.zip file from your SD card. Otherwise it will ask you every time you go into HBOOT if you want to apply the update.
Good luck.
Click to expand...
Click to collapse
Unfortunately this method doesn't work either, it throws an error that says "Main Version is older, Update Fail!"
I could have sworn I've read about this working before. I would have tested it first myself but I don't have a phone that isn't S-OFF. Sorry for making you jump through hoops.
You could try the methods in the other threads linked above. I guess you do need temp root to do a downgrade.
Alternatively, you could use AlphaRevX to S-OFF, install Clockwork, and install the factory original, unrooted ROM. The downside of this is that it requires voiding your warranty if you have one.
Easiest way would be to run the official 2.2 RUU update from HTC. 100% stock.
Sent from my Liberty
Optic2 said:
Easiest way would be to run the official 2.2 RUU update from HTC. 100% stock.
Sent from my Liberty
Click to expand...
Click to collapse
He wants to return to android 2.1 so that wouldn't help whatsoever. Plus he already did that which is why he wants to downgrade.
Oh my bad, I didn't read the whole thread. Hmm why do you want to downgrade to 2.1?
Sent from my Liberty
Optic2 said:
Hmm why do you want to downgrade to 2.1?
Sent from my Liberty
Click to expand...
Click to collapse
This is the reason which he said in his post:"I don't like the performance with the new upgrade, it used to be a LOT snappier before."
drumist said:
This is the original ship ROM. I downloaded this back when I first got my phone (first day the Aria was released) and have kept it for future use. This was even before they added the ability to receive OTA updates, so you won't even have to worry about being notified about the 2.2.2 OTA update.
Now, you should be able to just run this and have it downgrade everything (except HBOOT, but that isn't a problem unless you want to root). I haven't actually done it before but it should work.
If it doesn't work, there is another way that will definitely work, but I'll explain that if the need arises. Let me know if you run into any problems.
Click to expand...
Click to collapse
One question... I have HTC Gratia, which is operator free, so can I restore your original (backuped) ROM on my phone and update it, so I can use it just like original one?
Hello everybody!
I am starting this new thread to try compile a simple to follow and reasonably written complete guide for rooting an Xperia Neo 2.3.3. I am doing this because, although there are enough information and software on this forum and on the internet in general, these are not really structured and gathered in a way that a non-experienced user (a.k.a. "noob") can easily manage, and the process of rooting 2.3.3. is a bit more complicated than 2.3.2 with Gingerbreak for instance.
This guide is for Xperia Neo running Android 2.3.3 with locked bootloader. Other devices with 2.3.3. might be rooted in a similar fashion.
Update: 2.3.4. for the Neo is out. Everything here still works as described with the difference that you get the latest 2.3.4 when updating OTA.
WARNING: some users reported that after downgrading from 2.3.4 to 2.3.2 in order to root, the battery meter showed 0%. I am not yet aware of a solution to this problem. So beware if your Neo already has the latest version.
Warning: Neither myself, nor anyone else but YOU is responsible if you damage your phone in any way or lose any information after trying to root your phone by folowing this guide! Also note that your warranty will expire when you root. However, unrooting should be possible, in principle.
--- Guide start ---
1. Back up your data. You could do this using an app called Backup Master from the Android Market. Additionally, I had my contacts and calendar synchronized with my Google account. SMS messages were not properly backed up, but I didn't care about them anyway. If you do care, you might want to save them to your SD card, using the built-in option or just use another app. Also make sure your battery is at least half charged before starting.
2. Download FlashTool from here or directly here. Install it by simply unpacking it somewhere.
3. Download the generic firmware 2.3.2 from here or directly here. You do this because Gingerbreak (will come to that) uses a security vulnerability to gain root rights in 2.3.2. that has been fixed with the new 2.3.3. Extract the .ftf file from the .rar archive you just downloaded to the sub-folder "firmwares" of your Flashtools installation from step 2. (You might need WinRar for extracting)
4. Go to your Flashtool installation to the folder "drivers" and install ggsetup-2.2.0.10.exe. Download the USB drivers for your Neo from here. Unpack the contents of the archived folder "amd64" (if on Windows 64) or "i386" (if on Windows 32) to the folder "amd64" or "x86" respectively of the installation folder of Gordons Gate. The path might be something like "c:\Program Files (x86)\Sony Ericsson\Gordons Gate\". Run DPInst.exe to install the drivers.
Alternatively to this step, I think you could install the drivers by just installing PCCompanion and plugging in your phone, but I did it the hard way.
5. Run the file X10FlashTool.exe; click Flash; you should see the firmware you downloaded in step 3 in the appearing window if you extracted it correctly; click OK (I recommend you leave the option "wipe data" checked, although some users reported that it worked for them even without wiping the data); follow the instructions (note that the back button on the Neo is on the other side as pictured); the flashing should take no more than a couple of minutes; start your phone - this will take a bit longer the first time. If after the reboot the battery meter is showing 1%, shut down and take out the battery for a minute, then boot up again.
6. Get Gingerbreak from here of directly here. This is the exploit that actually roots the phone. Copy it to your phone and install. You can do this a number of ways. For example: install ES File Explorer from the Android Market, access your PC via WLAN with it and install it directly from there. You will be prompted to change the setting to allow the installation of apps from unknown sources in case you didn't change it already. Also allow USB-debugging in the same settings menu under "developer".
7. Run Gingerbreak and tap "root device". This shouldn't take more than a couple of minutes, although some users reported it taking hours. If it is taking very long, you might want to try inserting another SD card and repeating the attempt. When it's done, it will reboot. Now you have a rooted 2.3.2. You can check this by installing the app "root checker" from the Android Market. When you start "root checker" you will be asked by an app called "superuser" if you want to grant root access to this program. This "superuser" app was installed by Gingerbreak after rooting and manages which program has root permissions.
8. Now before doing anything, go to settings>info>software update> update now and get the new Android 2.3.3 OTA (= over the air, i.e. via WLAN or 3G). Do not do this via your PC, because you will unroot the phone. There have been a lot of problems reported with this step. If right after you tap "update now" you get the message "unable to connect" try shutting down, waiting a minute and booting up again or also try setting the date and time to the correct values, in case you have something like 01 Jan 1980. Other users said, it just took a lot of attempts before it worked and that the problem might be with the SonyEricsson servers... If after the update was downloaded you get some kind of error message like "cannot update" it might be because you did some changes to system files or possibly you used a non-original firmware in step 3.
After the update was done, check again for root access with the "root checker"
9. Restore the data you backed up in step 1 and enjoy.
Update: I managed to update to 2.3.4. Unfortunately I could not simply update OTA from my rooted 2.3.3. I kept getting an error message after downloading the update, probably because I had changed system files. So I did all the above steps again, with the difference that in step 8 I got the 2.3.4. from the SE server.
--- Guide end ---
Please click the Thanks button and/or reply to this post and write your own experience or suggestions/corrections.
A similar guide/tutorial/how-to has been posted before (Here). Perhaps not as detailed as yours but nonetheless, it's been done. And do give credit to the necessary people.
But good job on taking the time and writing this up. I'm sure a lot of Neo users will appreciate it.
Cheers!
xtacy! said:
A similar guide/tutorial/how-to has been posted before (Here). Perhaps not as detailed as yours but nonetheless, it's been done. And do give credit to the necessary people.
!
Click to expand...
Click to collapse
Actually, I did link directly to the thread you wrote, because it was one of my starting points. And to be rigorous, the steps enumerated there are from here, but with the firmware for Neo. The real credit goes to the programmers of Gingerbreak, Flashtool etc.
Like I said, I was just gathering information and detailing them, I don't take credit for anything other than taking the time to write the post.
Yup, I had actually included that initially i.e. that most of us already know these steps from the original thread but then wanted to give you credit for doing what you did.
And when I said give credit where it is due, I meant the actual people behind the programs and kistigun for his tutorial.
guys after i root my neo according to this guide the ota firmware i get will be unbranded? right?
By the way thanks for the guide, i might use it one day after i gain more knowledge about those things...
If you've flashed the generic firmware, then yes, you would be unbranded BUT you will still be locked to your network until you purchase the unlock key.
Unbranding would remove all your network specific apps (part of bloatware).
marcindpol said:
guys after i root my neo according to this guide the ota firmware i get will be unbranded? right?
By the way thanks for the guide, i might use it one day after i gain more knowledge about those things...
Click to expand...
Click to collapse
An OTA update won't remove the branding, but flashing will. It's what I describe in step 5.
I was just like you a couple of days ago, but I managed to learn all this over the weekend and did all I described here. (and a few things more ) Don't rush into it. Read everything coherent and helpful you can find first.
xtacy! said:
If you've flashed the generic firmware, then yes, you would be unbranded BUT you will still be locked to your network until you purchase the unlock key.
Click to expand...
Click to collapse
Thanks for the info. I didn't have any network locks or branding on mine, but it's good to know that for future reference.
Vorsprung said:
An OTA update won't remove the branding, but flashing will. It's what I describe in step 5.
I was just like you a couple of days ago, but I managed to learn all this over the weekend and did all I described here. (and a few things more ) Don't rush into it. Read everything coherent and helpful you can find first.
Click to expand...
Click to collapse
ok i think i understand now, but just to clarify:
if i flash generic (unbranded?) and then do the OTA or Pc Companion update, the update i get will also be unbranded?.
also will all the future updates be unbranded too?
Another question: since my neo is Irish Vodafone branded phone, which generic software i should flash in step 5?
Thanks a lot for help and please do not get annoyed by my questions as i am totally noob when it comes to those things, also sorry for my poor English...
marcindpol said:
ok i think i understand now, but just to clarify:
if i flash generic (unbranded?) and then do the OTA or Pc Companion update, the update i get will also be unbranded?.
also will all the future updates be unbranded too?
Click to expand...
Click to collapse
The answer should be yes to both questions. Once you've debranded your phone, it will not get "rebranded" (except if you flash it with a branded firmware). The generic firmware linked here is of course without any branding.
marcindpol said:
Another question: since my neo is Irish Vodafone branded phone, which generic software i should flash in step 5?
Click to expand...
Click to collapse
You could use the generic one, but you will lose the branding. I'm guessing you don't have a problem with that.
marcindpol said:
Thanks a lot for help and please do not get annoyed by my questions as i am totally noob when it comes to those things, also sorry for my poor English...
Click to expand...
Click to collapse
You're welcome! I'm not exactly experienced myself, so I don't guarantee that my answers are 100% accurate and correct...
I don't think your English is bad at all. Don't you speak English in Ireland?
Can anybody give more details on the branding issue?
Vorsprung said:
The answer should be yes to both questions. Once you've debranded your phone, it will not get "rebranded" (except if you flash it with a branded firmware). The generic firmware linked here is of course without any branding.
You could use the generic one, but you will lose the branding. I'm guessing you don't have a problem with that.
You're welcome! I'm not exactly experienced myself, so I don't guarantee that my answers are 100% accurate and correct...
I don't think your English is bad at all. Don't you speak English in Ireland?
Can anybody give more details on the branding issue?
Click to expand...
Click to collapse
Thanks a lot for the answers
hehe yes people in general speak English here in Ireland but lets not forget there are thousands of emigrants from around the world living here too, i am one of them
Can you please also write which generic firmware should i flash, UK, World or any other? (perhaps there is IE one?), and will it affect the frequency of getting future official updates from SE? (yes i want to get rid of Vodafone from my phone and stay with a 100% SE official firmware).
Thanks
Once you flash a generic firmware, future updates will all be generic updates as well.
Some of the plus points that I can see of having a generic firmware is that
a) updates are rolled out faster (as compared to branded firmware).
b) you get rid of a lot of junk that network providers seem to put in i.e. bloatware.
OK I am now on generic, unbranded Global International 1247-0875_R11C , of course 2.3.3, however I did not root my phone and used SEUS instead OTA.
Thanks a lot Vorsprung and others for help
I just flashed my Xperia Neo 2.3.2 global, applied Gingerbreak, and updated OTA to the last 2.3.3 firmware (4.0.A.2.368)
I confirm I kept root!
Kalram said:
I just flashed my Xperia Neo 2.3.2 global, applied Gingerbreak, and updated OTA to the last 2.3.3 firmware (4.0.A.2.368)
I confirm I kept root!
Click to expand...
Click to collapse
Same here
I follow this guide and got my Xperia Neo rooted! Thanks Vorsprung!!!
I wanted it root to install Google Talk with video! It works very well!
Now I want a way to unlock the bootloader, as I want to run Cyanogen mod
Ask the Admin for your own forum section about the Neo, all this OTA-root with the latest firmware just making me jealous.
flashmode
Hi guys!
well I just can follow till step 5. Opening the "X10FlashTool.exe" --> Click On flash. that's it. It tells me to enter the flash mode but how? I pressed&hold the menu button before plugging the usb cable onto my PC. Instead entering the flash mode it only starts charging my battery. Can somebody help ?
thanks a lot !
i was clicking the wrong button
I have rooted 2.3.2 (checked with rootchecker) but when I try to update OTA it says "Your phone already has the latest software".. Please help!!
Edit: Even says up to date using pc companion.
Just got my phone yday. I've scoured the Ascend Mate2 threads, and al I see are questions about re-rooting the Lollipop build. Since it looks like Huawei has rescinded their Lollipop ROM for the moment, I'm just hanging on 4.3. With a screen this HUGE, I'd love to root to be able to lower the DPI. Can anyone advise how to do that? Or am I better just waiting for Huawei to officially release Lollipop?
EDIT: so I found this -- http://forum.xda-developers.com/showpost.php?p=61682526&postcount=3. I'm confused, cuz one page of Huawei's blog says they hit pause on the 5.1 rollout, yet this 5.1 download looks like it's hosted on GetHuawei.com. I'm so confused...
adogg222 said:
Just got my phone yday. I've scoured the Ascend Mate2 threads, and al I see are questions about re-rooting the Lollipop build. Since it looks like Huawei has rescinded their Lollipop ROM for the moment, I'm just hanging on 4.3. With a screen this HUGE, I'd love to root to be able to lower the DPI. Can anyone advise how to do that? Or am I better just waiting for Huawei to officially release Lollipop?
EDIT: so I found this -- http://forum.xda-developers.com/showpost.php?p=61682526&postcount=3. I'm confused, cuz one page of Huawei's blog says they hit pause on the 5.1 rollout, yet this 5.1 download looks like it's hosted on GetHuawei.com. I'm so confused...
Click to expand...
Click to collapse
Since you just got your phone, I would say get to know it on 4.3 first. Lollipop is prettier, but you can do more root things on JB, it runs better, has better battery life, and is an all around better experience, IMO.
Lollipop doesn't have xposed either, if you planned on using that. On top of that, it is missing some core functionality like a startup manager(apps that should be running after a reboot are not!) and has a crippling audio bug.
First thing you have to do for root is email Huawei with your IMEI and SN asking for a bootloader unlock code.
[email protected]
Here is the email I sent them:
Hello, I would like a code to unlock the bootloader on my Huawei Ascend Mate 2, please.
Serial - *********
IMEI - *******
Thank you
Click to expand...
Click to collapse
I then got an unlock code within minutes, so it may or may not be somewhat automated.
TWRP for Mate2
Basically that is a zip file with everything that you need to install TWRP on the Mate2. It has:
SHM's Unified TWRP(v2.8.7.3).
Huawei drivers
ADB/Fastboot
SuperSu(v2.46)
stock 5.1 recovery(just incase)
!Readme file with step by step.
TWRP is needed to install SuperSu, which in turn gives you root.
First, make sure you leave all the files in the same folder. Extract them anywhere, like your desktop. Install the Huawei drivers if you don't already have them installed.
***Put the UPDATE-SuperSU-v2.46.zip on your phone's sdcard somewhere easy to find***
1. Turn off your phone
2. Hold Volume DOWN and Power button for a few seconds. When the screen turns on let go of the power button.
3. Now you should be on the bootloader screen, also known as fastboot.
4. Plug your phone into your PC and wait a minute to make sure any additional drivers are installed and setup.
5. Hold shift and right click an empty space in the folder you downloaded with adb.exe and fastboot.exe and select "Open command window here". A command window should open.
6. In command window type 'fastboot devices' and make sure it says there is a fastboot device. If it doesn't, that means your drivers didn't work. Try unplugging your phone and using another USB port.
7. If it showed a device, its working. Type 'fastboot flash recovery twrp.img'
8. If successful, your phone now has twrp installed
9. While still in fastboot, hold VOLUME UP and the POWER BUTTON for about 8 to 10 seconds, as soon as the screen turns off and then back on again, let both buttons go.
10. In TWRP, hit install and find your UPDATE-SuperSU-v2.46.zip and flash it.
11. Should be rooted and good to go.
12. I included the stock recovery if you ever want/need to go back. Just follow the same steps but replace "twrp.img" with "stock_recovery.img"
Click to expand...
Click to collapse
To lower DPI on our phone, a line will need to be added to the build.prop in the "root/system/" directory.
Add:
Code:
ro.sf.lcd_density=264
to the end of the text on a new line. 264 is the lowest you can go without causing multiple apps to crash.
You can go lower, but you will need Xposed and App settings to change the crashing apps to 264 or above.
Wow, thank you SO much for all of this!! So awesome of you!
adogg222 said:
Wow, thank you SO much for all of this!! So awesome of you!
Click to expand...
Click to collapse
Build prop editor on Google play store can very easily change your dpi. And makes a backup if you want to go back. Better than modding it yourself. And I agree with ark. Hold.off on L until things are fixed. Or until Tom get cm12 up and going.
Props to Ark for putting so much effort into his reply. (I would not have done the same.)
My advice to this self proclaimed "noob" is to read the threads and get more educated before just posting a question that has already been answered with it's own thread. All of the info that Ark posted is in these forums. Please don't get in the habit of asking to be spoon fed. That is certainly frowned upon on XDA.
kimtyson said:
Props to Ark for putting so much effort into his reply. (I would not have done the same.)
Click to expand...
Click to collapse
I had most of it done and copy pasted from another post I already made.
I'm glad someone finally gave simple comprehensive instruction. Unlike someone stated above, it was not that easy to find. I have had my phone for about 1 1/2 months since I returned from vacation in Europe. Ordered it online from Frys while I was there. Anyway, I have searched many times for instructions and couldn't find one thing definitive. Always comments alluding to root, and "does this keep root after update" or "how to get root back" or "this root method didn't work" etc... But never could I find instructions on how to achieve root on stock 4.3 until now. So Thank you sooo much. Now are we sure about the email link you provided above? Because I sent them (Basically copy and pasted ) your email above email twice. About a week ago, and a few days ago. And still no response! Any other suggestions? And shouldn't this be stickied since Root is the most basic of function of what we all want?
Some great information in this thread. Thanks guys. So unlocking the bootloader will wipe the device correct?
I got my unlock code and was going to unlock and make the device see itself as OEM. I was going to install L but it sure seems from the few posts here that it might not be worth it. Crippling audio bug? Can anyone elaborate on that?
Would it be better to unlock, convert my device to OEM and register with Huawei for OTA updates and simply wait for an official release? If I do the conversion, will the OS still be 4.3 at least?
Just like the thought of the updated Huawei EMUI 3 1.
I'm reading so many different confusing post. So does towelroot or kingroot work on MT2 L03 Android 4.3? I've read other places those methods work? And does anyone have the instructions on the easiest way to unlock bootloader (I hear that is necessary before we root)? I already have the unlock code. This phone has been in a box for the last 1 1/2 months waiting for me to have the time to play. Thank you.
TheIgster said:
Some great information in this thread. Thanks guys. So unlocking the bootloader will wipe the device correct?
I got my unlock code and was going to unlock and make the device see itself as OEM. I was going to install L but it sure seems from the few posts here that it might not be worth it. Crippling audio bug? Can anyone elaborate on that?
Would it be better to unlock, convert my device to OEM and register with Huawei for OTA updates and simply wait for an official release? If I do the conversion, will the OS still be 4.3 at least?
Just like the thought of the updated Huawei EMUI 3 1.
Click to expand...
Click to collapse
The audio bug is a bug that happens while listening to any audio. The audio will cut off completely. If you press the either of the volume keys, the phone will basically freeze for around 30 seconds and then usually it starts working like normal again.
It happened to me very often, like every time I listened to anything. But after installing Viper and its drivers and boosting the audio levels I haven't had this bug happen once. So that seems like a fix to me.
---------- Post added at 11:41 PM ---------- Previous post was at 11:36 PM ----------
TTJB said:
I'm reading so many different confusing post. So does towelroot or kingroot work on MT2 L03 Android 4.3? I've read other places those methods work? And does anyone have the instructions on the easiest way to unlock bootloader (I hear that is necessary before we root)? I already have the unlock code. This phone has been in a box for the last 1 1/2 months waiting for me to have the time to play. Thank you.
Click to expand...
Click to collapse
If you have the code, just boot into fastboot and use the command
Code:
fastboot oem unlock *your code, no asterisks*
ArkAngel06 said:
The audio bug is a bug that happens while listening to any audio. The audio will cut off completely. If you press the either of the volume keys, the phone will basically freeze for around 30 seconds and then usually it starts working like normal again.
It happened to me very often, like every time I listened to anything. But after installing Viper and its drivers and boosting the audio levels I haven't had this bug happen once. So that seems like a fix to me.
Click to expand...
Click to collapse
Hmmm. I have finally loaded LP, but haven't messed too much with audio playback. I'll have to listen for it. So where is this viper that I can load?
TheIgster said:
Hmmm. I have finally loaded LP, but haven't messed too much with audio playback. I'll have to listen for it. So where is this viper that I can load?
Click to expand...
Click to collapse
It's on Google Play or XDA. Try looking for it.
kimtyson said:
It's on Google Play or XDA. Try looking for it.
Click to expand...
Click to collapse
Thanks. Maybe try being less snarky next time?
Just a simple question in a forum that doesn't have a helluva lot of posts anyway.
alright so i got to the stage where i have superSU. however when i open it it says SU binary needs to be updated
i tried using twrp and installed the updated 2.4.6....and it still says i need to update the binary
any suggestions?
thanks ark for the detailed instructions tho
Callmebaus said:
alright so i got to the stage where i have superSU. however when i open it it says SU binary needs to be updated
i tried using twrp and installed the updated 2.4.6....and it still says i need to update the binary
any suggestions?
thanks ark for the detailed instructions tho
Click to expand...
Click to collapse
Just let it update itself.
Moody66 said:
Just let it update itself.
Click to expand...
Click to collapse
how? selecting normal? instead of twrp?
Callmebaus said:
how? selecting normal? instead of twrp?
Click to expand...
Click to collapse
Normal
jesus christ i remember normal fkin up my phone so i was sure not to press it then i formatted my phone using twrp
os....as well
I can't do anything
i should shoot myself.
trying to install stock again, having no luck
Callmebaus said:
jesus christ i remember normal fkin up my phone so i was sure not to press it then i formatted my phone using twrp
os....as well
I can't do anything
i should shoot myself.
trying to install stock again, having no luck
Click to expand...
Click to collapse
If you still not resolve the problem yet, try this:
http://forum.xda-developers.com/showpost.php?p=58208866&postcount=9
and remember always take backup...
xordos said:
If you still not resolve the problem yet, try this:
http://forum.xda-developers.com/showpost.php?p=58208866&postcount=9
and remember always take backup...
Click to expand...
Click to collapse
that's the exact post that I used yesterday, haha
all fixed and rooted
thank u
Hi, as said in the title, my Motorola XT910 is stuck on the logo, and will not boot, even after charging, and letting it do its thing overnight. I tried everything I could, including trying to wipe the cache via recovery mode, and I do not have access to it via adb in any ways. The only communication I can establish between it and my computer is via fastboot. The RSD Software doesn't recognize it either, though it appears on the computer as "ADB Device". Biggest problem is, I have seen threads from years ago on other forums, all over the internet with people having this issue, some had it fixed via a factory reset, some had to send it back. Obviously, I cannot send it back to motorola, as for the factory reset, I really cannot do it, since my whole objective of making this phone function again was to recover old very important videos and photos on it, which is rendered impossible due to android not starting.
I really hope someone has a solution (does anyone still even come by these threads ?).
Thanks in Advance,
Dylan.
LaMontreBelge said:
Hi, as said in the title, my Motorola XT910 is stuck on the logo, and will not boot, even after charging, and letting it do its thing overnight. I tried everything I could, including trying to wipe the cache via recovery mode, and I do not have access to it via adb in any ways. The only communication I can establish between it and my computer is via fastboot. The RSD Software doesn't recognize it either, though it appears on the computer as "ADB Device". Biggest problem is, I have seen threads from years ago on other forums, all over the internet with people having this issue, some had it fixed via a factory reset, some had to send it back. Obviously, I cannot send it back to motorola, as for the factory reset, I really cannot do it, since my whole objective of making this phone function again was to recover old very important videos and photos on it, which is rendered impossible due to android not starting.
I really hope someone has a solution (does anyone still even come by these threads ?).
Thanks in Advance,
Dylan.
Click to expand...
Click to collapse
RSD lite doesn't work with most Windows 10 machines, use Windows 7. http://forum.xda-developers.com/showpost.php?p=59348530&postcount=6
If you want to save data you need to modify the .XML file if using RSD Lite
Lots of issues can cause a boot loop, bad battery, bad app, bad hardware... even a bad charger or USB cable.
Try [Utility] - = MotoFlashPro =
Hi, thanks for replying, I took note of the software not functionning with windows 10, do you think it will work if I run 7 in VmWare and pass the phone through or do I absolutely have to use a physical 7 machine ?
Also, I really cannot make a factory cable like the one pictured in the post you linked, since none of my cables permit such a modification (the fifth pin does not have a spot to solder onto).
About the bootloop, well I'm not sure it really is one, since it doesn't loop at all, it just stays on the starting screen.
It shouldn't be a battery problem since even when giving power straight to the battery terminals, it does not boot, though the fastboot thing says "battery ok".
It shouldn't be a bad app either since last time I used the phone, like 3 years ago before I broke the screen which I replaced recently, it worked perfectly fine, and obviously I could not install an app in the meantime. The battery just ran down to 0 volts but I managed to make it work again. And what do you mean by bad charger ? Something like not powerful enough perhaps ?
LaMontreBelge said:
Hi, thanks for replying, I took note of the software not functionning with windows 10, do you think it will work if I run 7 in VmWare and pass the phone through or do I absolutely have to use a physical 7 machine ?
Also, I really cannot make a factory cable like the one pictured in the post you linked, since none of my cables permit such a modification (the fifth pin does not have a spot to solder onto).
About the bootloop, well I'm not sure it really is one, since it doesn't loop at all, it just stays on the starting screen.
It shouldn't be a battery problem since even when giving power straight to the battery terminals, it does not boot, though the fastboot thing says "battery ok".
It shouldn't be a bad app either since last time I used the phone, like 3 years ago before I broke the screen which I replaced recently, it worked perfectly fine, and obviously I could not install an app in the meantime. The battery just ran down to 0 volts but I managed to make it work again. And what do you mean by bad charger ? Something like not powerful enough perhaps ?
Click to expand...
Click to collapse
Hi again, quick update, I plugged it into my Windows Xp machine as I do not have a windows 7 computer, and it appeared. Also, could you please tell me what to change in the xml file in order to keep the data ?
Please, are you there ? I really need this help with the XML file, what do I need to edit ? I got the phone to be recognized in windows, even in rsd lite, i just need to know what to edit in the file
LaMontreBelge said:
Please, are you there ? I really need this help with the XML file, what do I need to edit ? I got the phone to be recognized in windows, even in rsd lite, i just need to know what to edit in the file
Click to expand...
Click to collapse
I've never had to use RSD Lite, and you might be better off waiting for him to respond incase I'm wrong (haven't touched this phone in a while). But I've done some digging and heard you can remove the line near the end of that XML file that goes something like
Code:
<step operation="erase" partition="userdata"/>
and it should skip the data wipe. I don't think it's necessary to remove the ones for cache and stuff. It might be a bad idea.
Smu1zel said:
I've never had to use RSD Lite, and you might be better off waiting for him to respond incase I'm wrong (haven't touched this phone in a while). But I've done some digging and heard you can remove the line near the end of that XML file that goes something like
Code:
<step operation="erase" partition="userdata"/>
and it should skip the data wipe. I don't think it's necessary to remove the ones for cache and stuff. It might be a bad idea.
Click to expand...
Click to collapse
Thanks for the info, I will indeed wait for him to reply, but i just checked in the XML file, and I do not have that line anywhere in the file. Does that mean it is incomplete or does this one just default to not erasing ? Also, this is the only file I could find that is a perfect match for my french market xt910.
LaMontreBelge said:
Thanks for the info, I will indeed wait for him to reply, but i just checked in the XML file, and I do not have that line anywhere in the file. Does that mean it is incomplete or does this one just default to not erasing ? Also, this is the only file I could find that is a perfect match for my french market xt910.
Click to expand...
Click to collapse
Also, I just checked in the other file I found, for an english-languaged model this time, it does have these lines, but is only 560mb instead of the 800 something of my french file
LaMontreBelge said:
Thanks for the info, I will indeed wait for him to reply, but i just checked in the XML file, and I do not have that line anywhere in the file. Does that mean it is incomplete or does this one just default to not erasing ? Also, this is the only file I could find that is a perfect match for my french market xt910.
Click to expand...
Click to collapse
Huh, yeah I don't really know then. The model I have is the XT912 (Verizon). I just got this info from a thread for a newer Moto. It could very well just simply not wipe, but I wouldn't go ahead and try incase you end up actually wiping it permanently. I'm not an expert at all, so I'd just wait until he gives you advice. Does this French firmware have similar lines like that for cache or other partitions? It might be in a completely different format then what I'm looking at. But I doubt it's corrupt.
Smu1zel said:
Huh, yeah I don't really know then. The model I have is the XT912 (Verizon). I just got this info from a thread for a newer Moto. It could very well just simply not wipe, but I wouldn't go ahead and try incase you end up actually wiping it permanently. I'm not an expert at all, so I'd just wait until he gives you advice. Does this French firmware have similar lines like that for cache or other partitions? It might be in a completely different format then what I'm looking at.
Click to expand...
Click to collapse
Actually I think the xt912 is pretty much identical unless I'm mistaking something. But either way, I do appreciate your cautiousness about the subject. Yes exactly I really cannot afford to lose the data that remains on the phone. Actually yes it does seem to have fairly similar lines, here have a look, on the left is the french firmware and the right the international. Now, I do not know what the files you're used to working with look like, but they may very well have similar if not identical lines.
Edit: I just re-read your question and realized I completely misunderstood what you asked. No, the french version doesn't have formatting lines at all. Deeply sorry for this misunderstanding.
LaMontreBelge said:
Actually I think the xt912 is pretty much identical unless I'm mistaking something. But either way, I do appreciate your cautiousness about the subject. Yes exactly I really cannot afford to lose the data that remains on the phone. Actually yes it does seem to have fairly similar lines, here have a look, on the left is the french firmware and the right the international. Now, I do not know what the files you're used to working with look like, but they may very well have similar if not identical lines.
Edit: I just re-read your question and realized I completely misunderstood what you asked. No, the french version doesn't have formatting lines at all. Deeply sorry for this misunderstanding.
Click to expand...
Click to collapse
I've noticed the left one is a "1FF" firmware. Which from what I've looked up, is supposed to not have the erasing lines. While the "CFC" ones are. Which is why the right one has those. But I've noticed the left firmware has what seems to be Gingerbread. I don't know if dirty flashing an older firmware will cause issues, if it's even possible. I've found an old thread on droidforums where someone tried to go back to ICS from that JB leak and ended up bricking. I don't think I can post links because I haven't posted 10 times unless they changed something.
Smu1zel said:
I've noticed the left one is a "1FF" firmware. Which from what I've looked up, is supposed to not have the erasing lines. While the "CFC" ones are. Which is why the right one has those. But I've noticed the left firmware has what seems to be Gingerbread. I don't know if dirty flashing an older firmware will cause issues, if it's even possible. I've found an old thread on droidforums where someone tried to go back to ICS from that JB leak and ended up bricking. I don't think I can post links because I haven't posted 10 times unless they changed something.
Click to expand...
Click to collapse
Actually, the phone is still on gingerbread (2.3.5) as I never found updates when it still worked, so this shouldn't be an issue (hopefully) and okay, thanks for the info, so it means my file is sound, right?
LaMontreBelge said:
Actually, the phone is still on gingerbread (2.3.5) as I never found updates when it still worked, so this shouldn't be an issue (hopefully) and okay, thanks for the info, so it means my file is sound, right?
Click to expand...
Click to collapse
I believe the file should be good unless you somehow got a bad download or something. But it seems 2.3.5 and 2.3.6 have different bootloader versions, and it looks like the firmware on the left doesn't have the "mbm" stuff. The last thing you need is a hard brick, so I'd be pretty hesitant to flash unless someone who has more knowledge tells you it's okay. I'm guessing you'd have to find a French CFC firmware and edit out that userdata wipe line (if that even works) or find a 1FF 2.3.5 firmware with an identical bootloader.
Smu1zel said:
I believe the file should be good unless you somehow got a bad download or something. But it seems 2.3.5 and 2.3.6 have different bootloader versions, and it looks like the firmware on the left doesn't have the "mbm" stuff. The last thing you need is a hard brick, so I'd be pretty hesitant to flash unless someone who has more knowledge tells you it's okay. I'm guessing you'd have to find a French CFC firmware and edit out that userdata wipe line (if that even works) or find a 1FF 2.3.5 firmware with an identical bootloader.
Click to expand...
Click to collapse
Alright, then I won't flash it, just in case. Also, do you have any way to check if the bootloader version is different ? If yes, I could check it. And alright, I'll try finding another file that happens to be on 2.3.5. Thanks again for the info sir.
LaMontreBelge said:
Alright, then I won't flash it, just in case. Also, do you have any way to check if the bootloader version is different ? If yes, I could check it. And alright, I'll try finding another file that happens to be on 2.3.5. Thanks again for the info sir.
Click to expand...
Click to collapse
I hyperlinked a link I found with some info on that. I just looked at the build number of the versions listed in that doc, looked at the bootloader version next to it, and looked at the firmware's filename. In your case, "6.5.1-167" has bootloader version "0A.6C" while 2.3.5 with the build number "6.5.1_73" has bootloader version "0A.66". My source was this Doc https://docs.google.com/document/d/1CWZU-4i7jWO26RXJ7YFJV-Ze-mJrDaTuCuVI-ZwxDBE/. I honestly don't know if the bootloader matters, but I wouldn't want to risk it in case it makes the situation worse. Hopefully shadow can help you out.
https://forum.xda-developers.com/t/index-motorola-droid-razr-2012.3023837/post-58684547
Here's a pinned thread with some firmwares if it helps any.
Smu1zel said:
I hyperlinked a link I found with some info on that. I just looked at the build number of the versions listed in that doc, looked at the bootloader version next to it, and looked at the firmware's filename. In your case, "6.5.1-167" has bootloader version "0A.6C" while 2.3.5 with the build number "6.5.1_73" has bootloader version "0A.66". My source was this Doc https://docs.google.com/document/d/1CWZU-4i7jWO26RXJ7YFJV-Ze-mJrDaTuCuVI-ZwxDBE/. I honestly don't know if the bootloader matters, but I wouldn't want to risk it in case it makes the situation worse. Hopefully shadow can help you out.
Click to expand...
Click to collapse
Okay, i just took a look at the doc linked, and I have no idea how you found it, but it is mind boggling. All the roms, listed, just like that. Thank you so much. And yes indeed the bootloader is different, and I wouldn't risk it. I'll keep looking for the 2.3.5 ROM, but for now it seems like a lost cause. Perhaps they have it over on the Motorola forums. I'll make a thread later today.
Smu1zel said:
I hyperlinked a link I found with some info on that. I just looked at the build number of the versions listed in that doc, looked at the bootloader version next to it, and looked at the firmware's filename. In your case, "6.5.1-167" has bootloader version "0A.6C" while 2.3.5 with the build number "6.5.1_73" has bootloader version "0A.66". My source was this Doc https://docs.google.com/document/d/1CWZU-4i7jWO26RXJ7YFJV-Ze-mJrDaTuCuVI-ZwxDBE/. I honestly don't know if the bootloader matters, but I wouldn't want to risk it in case it makes the situation worse. Hopefully shadow can help you out.
Click to expand...
Click to collapse
Also, in the document there is a link that leads to an archive, but no files are downloadable, do you happen to have any of them by chance ?
Smu1zel said:
https://forum.xda-developers.com/t/index-motorola-droid-razr-2012.3023837/post-58684547
Here's a pinned thread with some firmwares if it helps any.
Click to expand...
Click to collapse
This thread does indeed help a little bit, but the firmware center link does not, as it is where i got my 2.3.6 ROM from, and as far as I know, is the only french one. Honestly I do not care if it's an English one, I just want to make sure that it won't mess up the phone
LaMontreBelge said:
Also, in the document there is a link that leads to an archive, but no files are downloadable, do you happen to have any of them by chance ?
Click to expand...
Click to collapse
Yeah I think those links might be out of date. Go under "XT910" and look at some of the links. Also I found that doc under that section.
https://forum.xda-developers.com/t/index-motorola-droid-razr-2012.3023837/post-58684547
I hope I'm not leading you down a wrong path, hopefully he responds soon. Maybe the bootloader doesn't matter, I don't know.