Related
Hi all.
I have an Spanish wifi-only Xoom (MZ604) and I'm tired of waiting for motorola's updates (still in Honeycomb 3.2!!!).
I want to test either EOS3 (Android 4.1.1) or EOS2 (Android 4.0.4) custom roms. I've read almost all tutoriales but I still have some doubts about the procedures... could anybody check this message and warn me if I'm going to do something wrong?
DOUBT 1.- Key shortcuts in Xoom
Can anybody tell me the existing key combinations in Xoom? I only know about POWER+VOL_UP key to enter bootloader mode.
DOUBT 2.- How to install CWM.
If I understand it correctly, both EOS2 and EOS3 should be installed from CWM recovery...
Is the following procedure OK?
- Some tutorials say that you have to be root first to install CWM ... is it really needed? Can't be done directly with ADB?
- Install Android SDK in the PC.
- Download eos-recovery-r6.img or eos-recovery-r6-softkeys.img
- Connect XOOM to PC with the original USB cable.
- Reboot XOOM in bootloader mode (Power + VolUp)
- Exec adb and then:
fastboot oem unlock <---- is this a requirement?
fastboot flash recovery eos-recovery-r6.img
fastboot reboot
DOUBT 3.- How to install or upgrade EOS 2 or 3 ROM?
Is the following procedure OK?
- Download ROM and gapps zip files.
- Start XOOM in recovery mode (CWM) -> How to do this?
- Do a nandroid backup.
- Wipe everything (data, cache, dalvik, etc)
- Install ROM zip.
- Install gapps zip.
- No need to do anything to root it, the rom is already rooted <-- is that right?
- Reboot
Is everything OK? Did I miss anything? Do I need to root my 3.2 install before any other step? Do I have to do the "oen unlock"?
Thanks.
All you need to do is unlock your boot loader and get into flashing eos3. Will give you details how to soon
Sent from my MZ601 using Tapatalk 2
wesamothman said:
All you need to do is unlock your boot loader and get into flashing eos3. Will give you details how to soon
Click to expand...
Click to collapse
Thanks for answering. If I'm understanding you correctly, you say that I don't need CWM and I can just flash the EOS ROM directly to my xoom without "applying" it as a zip in CWM...
I would really like to install CWM, I appreciate a lot the possibility to do "nandroid" backups to be able to go back before installing kernels, updates or so ...
NoP_Compiler said:
Thanks for answering. If I'm understanding you correctly, you say that I don't need CWM and I can just flash the EOS ROM directly to my xoom without "applying" it as a zip in CWM...
I would really like to install CWM, I appreciate a lot the possibility to do "nandroid" backups to be able to go back before installing kernels, updates or so ...
Click to expand...
Click to collapse
Since you are going to install EOS Jellybean, I don't advise you with CWM. A different recovery made by EOS team is better through which you can do nandroid backup and other stuff...
Here is what you need to do step by step...
Note: please read this procedure carefully more than once until you are fully aware of it. If you have any doubts or concerns, just ask to avoid confusion before you apply. This should be followed step by step.
To summarize:
First, download the above ROM and GAPPs and put them onto your xoom internal and external SD card. Put them under /mnt/sdcard for internal sd or somewhere accessible, and under the root of your external sd card.
To download:
• Get the Motorola USB drivers to your laptop: http://developer.motorola.com/docstools/USB_Drivers/
• Get the Android SDK to your laptop: http://developer.android.com/sdk/index.html
• Recovery Image: http://goo.im/devs/teameos/recoveries/wingray/eos-recovery-r6.img
• GAPPS: http://goo.im/devs/teameos/roms/eos3/gapps/gapps-jb-20120726-eos-signed.zip
• ROM: http://goo.im/devs/teameos/roms/eos3/nightlies/wingray/ ; get the latest one...
Steps:
1. Power off your XOOM device.
2. Press and hold the volume down button while pressing the power button at the same time. Note: Even if your xoom starts again, just keep the button pressed until you see "Starting fastboot protocol" on the screen.
3. Connect Xoom to your computer via USB.
4. Open a ‘Command Prompt’ or ‘Terminal’ window on your computer in your sdk/tools folder. This is the sdk you downloaded above.
5. unlock your xoom and flash the recovery image. The recovery image should be in your current working directory where you have command line navigated to: Type:
adb reboot bootloader
fastboot oem unlock
fastboot flash recovery eos-recovery-r6.img
fastboot reboot
adb reboot recovery
Now, you have your device unlocked and recovery installed.
Reboot your xoom by selecting the option "reboot system now" from recovery. you can navigate up and down using the volume buttons. Once an option is highlighted, press the power button to select, you will still have your old ROM.
To flash the other ROM downloaded above,
1. Boot into recovery by:
i. As soon as you hit the reboot command above, you should see a Motorola logo appear. Wait 3 seconds and tap the Volume down button and the words Android Recovery should appear on the screen. When you see that, tap the Volume up button and you’ll boot into recovery.
2. From within Recovery, perform wipe data, wipe cache, and go to advanced, wipe dalvik cache and battery stats. Don't worry, if the ROM and GAPPs are deleted, which should not be the case, you will have them on your external sd card
Note: wipe data will delete your stuff on the xoom. It would be great if you backup your files that you need to your external sd card before you start any of this procedure.
3. In recovery, navigate to install zip from sdcard > choose zip from sd card and select the EOS ROM you copied to the root of the SD card. Once the files are flashed, DO NOT reboot afterwards. Hold on.
4. Again, from Recovery, choose install zip from sdcard > choose zip from sd card and select the GAPPs you copied to the root of the SD card.
Then hit reboot system now. It will take 2 - 3 minutes for the first reboot. Setup your google account. and you are good to go.
Later reboots will be much faster (around 30 - 45 seconds). The more apps you install, the slower it boots...
That is pretty much it. Enjoy, I hope this helps you
Of course it helps! In fact, a lot.
When I was talking about CRW I really meant EOS recovery (which is based in CRW itself IIRC).
The only that I can't understand is why some tutorials ask me to root the tablet before doing all this process...
Anyway, I think I'm finally going with EOS3 + EOS recovery if nobody here advices me to flash EOS 2 instead...
Sent from my Samsung Galaxy S2 using Tapatalk Pro.
So, before flashing:
- Do you think EOS3 (JB in Xoom) is mature enough to use it, or I should go with EOS2 final (ICS)?
- Do you know of anything not working in a wifi xoom with EOS3 rel.127?
- I've downloaded eos6-recovery.img ... do you think I should flash the "soft-keys" or the rogue-recovery instead?
- I don't have Microsoft Windows in my laptop: I work under Linux, so I haven't downloaded Motorola's USB drivers... I imagine that they are not needed under Linux, and It will work just with SDK's "adb" and "fastboot", right?
- Can the device be bricked with this procedure, or there is always a "Power+VolKey" way to flash a stock image? (like galaxys2 that its almost unbrickable).
PS: Thanks for informing me in the other thread that the EOS rom comes already rooted
I will be away for couple of hours, will answer your questions all as soon as I get back...
Sent from my MZ601 using Tapatalk 2
NoP_Compiler said:
So, before flashing:
- Do you think EOS3 (JB in Xoom) is mature enough to use it, or I should go with EOS2 final (ICS)?
- Do you know of anything not working in a wifi xoom with EOS3 rel.127?
- I've downloaded eos6-recovery.img ... do you think I should flash the "soft-keys" or the rogue-recovery instead?
- I don't have Microsoft Windows in my laptop: I work under Linux, so I haven't downloaded Motorola's USB drivers... I imagine that they are not needed under Linux, and It will work just with SDK's "adb" and "fastboot", right?
- Can the device be bricked with this procedure, or there is always a "Power+VolKey" way to flash a stock image? (like galaxys2 that its almost unbrickable).
PS: Thanks for informing me in the other thread that the EOS rom comes already rooted
Click to expand...
Click to collapse
Alright, eos jelly bean is fully stable, ,such faster and smoother than ICS. You want feel the difference until you try it... however, eos ICS is stable too and has more features and addons by eos because it has been there under dev for longer time, jellybean is new, one month old only... I recommend you to go for jellybean, and try and see for yourself. At anytime you can flash ICS since your Xoom booloader is already unlooked and recovery installed, you can do that by just wiping data and flash ICS zip. That is as simple as that...
For Motorola drivers on Linux, I think it is not needed, adb is built in with Linux, but I am not sure as I haven't tried that yet.
For eos recovery, don't use the soft key version, use the normal one...
with this recovery, you will be safe, because at all times, your external SD is accessible in emergencies...
Hope that helps...
Sent from my MZ601 using Tapatalk 2
You have it down perfectly. Just to recap.
1. Set up android sdk. Download recovery image and store in sdk folder. Download rom/gapps and store on tablet.
2. Boot into fastboot (power + volume up).
3. fastboot oem unlock (required). This will wipe all data.
4. fastboot flash recovery recovery.img (whatever recovery you decide to go with, I recommend eos soft key).
5. boot into recovery, make nandroid backup, flash rom of your choice + gapps if necessary.
People tie rooting to flashing custom roms because many people have become so reliant on apps like rom manager that flash the recovery for you, an app that requires root access. I never rooted my galaxy nexus or xoom. I simply flashed recoveries in fastboot and proceeded to flash roms in recovery.
It actually bothers me how some have become so reliant on root access to flash roms. It has gotten to a point where many people genuinely don't know the difference and that, to me, says they don't really understand what it is they're doing, which will lead to issues should they ever need to troubleshoot.
You seem to have it down well though. Good luck.
Thanks a lot to both.
I'm still waiting for JDK to download for Android SDK to work (I'm on hollydays in a small house in the middle of the forest and Im connecting with GPRS via tethering...).
I'll inform about the results...
Sent from my Samsung Galaxy S2 using Tapatalk Pro.
Good luck...
Sent from my MZ601 using Tapatalk 2
Ok. EOS6-RECOVERY installed correctly. There are a couple of mistakes and some missing info in the "tutorial", so I'm going to change it to help future users:
I finally did it under Windows because almost all tutorials in Internet explain all the possible problems that you can find in Windows, and it's a "too risky" task for me to "experiment" by myself.
PART 1 .- HOW TO INSTALL EOS6 RECOVERY:
Originally quoted from wesamothman:
First, download the above ROM and GAPPs and put them onto your xoom external SD card. Put them in a folder called /sources/ of your external sd card.
- Get the Motorola USB drivers to your laptop: http://developer.motorola.com/docstools/USB_Drivers/
- Get the Android SDK to your laptop: http://developer.android.com/sdk/index.html
- GAPPS: http://goo.im/devs/teameos/roms/eos3/gapps/gapps-jb-20120726-eos-signed.zip
- ROM: http://goo.im/devs/teameos/roms/eos3/nightlies/wingray/ ; get the latest one...
And the most important:
- Recovery Image: http://goo.im/devs/teameos/recoveries/wingray/eos-recovery-r6.img
Check that the md5sum of this file is correct and matches with the one provided in the download page. This is the most important file because it will allow to install the CWM recovery system and it's CRITICAL that the file is not corrupted.
Steps:
a.- Install in your PC the lastest JavaSE JDK from Oracle's website.
b.- Install in yout PC Android SDK, open Windows' cmd, enter the android-sdk folder and run:
Code:
tools\android.bat update sdk
Now select "Android SDK Tools", "Android SDK platform-tools", and Extras/"Google USB Driver". Click on "Install packages".
c.- Enable USB debugging in the XOOM (in settings, development).
d.- Install the Motorola USB drivers for your laptop (32 or 64 bits, check it in the Windows system properties).
e.- Plug the Xoom to your laptop.
f.- Execute cmd and enter the android-sdk/platform-tools folder.
Run "adb devices", if you get an empty "List of devices attached", then you must enter the control-panel -> devices and "Fix problem with device" over the MZ60x device. After a While, Windows will fix it and "adb devices" will show a message like:
Code:
List of devices attached
037887sda897xz device
(the digits string will vary according to your device)
NO NEED TO DO THIS:
NO -> 1. Power off your XOOM device.
NO -> 2. Press and hold the volume down button while pressing the power button at the same time. Note: Even if your xoom starts again, just keep the button pressed until you see "Starting fastboot protocol" on the screen.
Because the first command show after this lines: (adb reboot bootloader) won't work while in fastboot. Only "fastboot" commands work in fastboot mode. If you try that command in fastboot mode, it will say "Error: device not found".
So just, with your xoom working under the Android OS, do:
Code:
adb reboot bootloader
With the above, you'll enter fastboot mode without needing to press any key in the startup.
Now your Xoom will show the Motorola logo and the words "Fastboot protocol...". If you need to stop now for any reason, you can abandon this mode safely and reboot the tablet with "Power+VolUP+VolDown" for a few seconds.
But let's continue.... If you now do:
Code:
fastboot devices
You should get a string like
Code:
List of devices attached
037887sda897xz fastboot
If you don't see that string (and you see and error about device not found), you have to "fix/repair" the usb drivers again in the Windows ControlPanel / Devices. Now you'll see a "FASTBOOT" device instead of the MZ60x you repaired before (that's why we have to repair/fix again the device, because WIndows see it as a different device while in fastboot mode).
After repairing it, unplug and plug the USB cable (still in fastboot mode) and repeat the command:
Code:
fastboot devices
Now it will work and you'll see the device recognized by "fastboot"
Issue the following command to unlock the Xoom (you'll void the warranty):
Code:
fastboot oem unlock
Follow the Xoom's onscreen instructions to unlock the bootloader. You have to use VolDown to move through options and VolUP to accept an option.
The xoom will reboot and your old android OS will show, but now with a factory reset. Select language, time, etc and enable again USB debugging and execute in the PC:
Code:
adb reboot bootloader
(to start again the tablet in fastboot mode)
Now copy the file eos-recovery-r6.img to the android-sdk/platform-tools/ folder and execute:
Code:
fastboot flash recovery eos-recovery-r6.img
You will see something like:
Code:
C:\Users\sromero\Desktop\android-sdk-windows\platform-tools>
fastboot flash recovery eos-recovery-r6.img
sending 'recovery' (4114 KB)...
OKAY [ 0.499s]
writing 'recovery'...
OKAY [ 1.014s]
finished. total time: 1.529s
Check in the xoom's screen that the file was correctly written and execute:
Code:
fastboot reboot
You xoom will start again in Android OS mode. Execute:
Code:
adb reboot recovery
And you'll start the nice EOS Recovery (based on Clockworld Mod) recovery system.
You can also do it manually by powering on the Xoom and when the motorola logo appears, wait 3 seconds and press VolUp.
Now, you have your device unlocked and recovery installed. Now, you are SAFE because you can do nandroid backups and restores and can put any ROM in your system and go back with a backup or flash another different rom.
PART 2 .- HOW TO USE CWM / EOS RECOVERY
Code:
Up -> VolumeUp button
Down -> VolumeDown button
Select -> POWER button
PART 3 .- HOW TO INSTALL EOS3 ROM:
Under recovery mode (abd reboot recovery), do:
- Backup/restore -> backup to external SD.
- Wipe data/factory reset
- Wipe cache
- Advanced -> Wipe Dalvik Cache
- Advanced -> Wipe Battery Stats
- Install ZIP from SDCARD -> /sources/ -> the eos3 rom .zip file.
- Install ZIP from SDCARD -> /sources/ -> the gapps .zip file.
- Reboot
- Enjoy your new rom!
Very well detailed... great...thx.
Sent from my MZ601 using Tapatalk 2
wesamothman said:
Very well detailed... great...thx.
Click to expand...
Click to collapse
No... thank you for the initial info
After restarting, I have a notification about a ROM update (128). The ROM-management app allows me to download it or apply a incremental update...
Do you know if that second option (incremental update) is safe?
Anyway, I can just always do a Nandroid and test it ... having CWM I can't loose never anything, right?
Of course it is safe, I use it a lot. Just boot into recovery now by long press on power menu, select reboot, recovery,
First download build128. It will be under /storage/sdcard0/goo manager.
From recovery, wipe cache, dalvik, flash build 128, and reboot,
FYI, this latest build has theme engine now
Sent from my MZ601 using Tapatalk 2
wesamothman said:
First download build128. It will be under /storage/sdcard0/goo manager.
From recovery, wipe cache, dalvik, flash build 128, and reboot,
FYI, this latest build has theme engine now
Click to expand...
Click to collapse
So, the incremental update has to be flashed from recovery too?
I'll try it after a few days, when people confirms that it has not any major bug...
Thanks.
NoP_Compiler said:
Thanks a lot to both.
I'm still waiting for JDK to download for Android SDK to work (I'm on hollydays in a small house in the middle of the forest and Im connecting with GPRS via tethering...).
I'll inform about the results...
Sent from my Samsung Galaxy S2 using Tapatalk Pro.
Click to expand...
Click to collapse
Worth noting that to use fastboot and stuff, you only really need to install the Android SDK Platform-tools, maybe the regular SDK tools as well, I can't remember.
You don't need to install all the other stuff.
---------- Post added at 08:02 AM ---------- Previous post was at 08:01 AM ----------
NoP_Compiler said:
So, the incremental update has to be flashed from recovery too?
I'll try it after a few days, when people confirms that it has not any major bug...
Thanks.
Click to expand...
Click to collapse
Yes, any updates/mods/gapps updates need to be flashed in recovery.
Unless specified that its necessary by devs though, you don't need to wipe anything. I've been on JB nightlies from day 1 and I haven't wiped cache or anything since the initial wipe.
Is it possible to...
a.- change the system font (too 'light' in my xoom).
b.- disable jellybean UI animations...
?
I don't know about question a, though I'm sure its possible.
As for question b, try a different launcher. Apex launcher and nova launcher are both popular Android 4.0+ launchers (check play store for them).
Eos ROM,m settings, developer options, disable animations and transitions
Sent from my MZ601 using Tapatalk 2
Found this online. *****this is not my work****** All credit goes to the author quattrodevelopment.blogspot.com
Here is a step by step with roms included for the 4.5 quattro Not the HD or 5.7 HD maybe soon.
Disclaimer: These ROMs/Recoveries are only intended for the BLU Quattro 4.5, or the K-Touch v9(which is the chinese version) These WILL NOT work on the 4.5HD or 5.7HD devices(I will release ROMs/Recoveries specifically for your device at a later time)
Drivers: https://copy.com/BUMmsS9rhLJe
English Recovery: https://copy.com/XZxTDht2lQiz
Gapps(4.2) https://copy.com/utkbZgwRpsVB
Gapps(4.1) https://copy.com/pSd8SsqU9pdI
ROMs With Less Bugs: MIUI v5 (4.1) https://copy.com/sbmcN6PHwFfi CM/AOKP Hybrid? JB (4.1) https://copy.com/VeLz1VLbkNNI Shendu ROM 4.1(Modified/Tweaked by me) https://copy.com/NwiFnlO8JAek
ROMs With More Bugs: Cyanogenmod 10.1 (4.2) https://copy.com/8kt2EAU2ll8y
1- Download the drivers from link posted above, and extract it to the folder of your desire. Now turn the phone off, and hold Vol+ (volume up button) and Power button at the same time until you see a green screen, then release both buttons immediately. You should now be in APX mode(nvflash) it will be a black screen
2- Connect phone to computer via usb cable. Now you should get a pop-up window about installing drivers, you're going to want to choose to browse computer for driver software manually. Then choose let me pick from a list of device drivers on my computer, and click have disk. Now you're going to browse to the location where you extracted the drivers to, and click on it(Ignore warning if it pops up, and choose install)
3- Assuming everything went as planned, now download the recovery and extract it to the location you desire(must be in a directory that you can issue adb commands from) inside of that folder, locate a file named recovery.bat. Double click on that file and a command prompt with a bunch of chinese pops up. Give it a second and press enter, it will go through the process and flash a recovery onto your phone
4- After everything is done, hold down the power button for about ten seconds(until the device powers off) Power the device back on normally, and download the ROM/ROMs if you haven't already and place them on the internal or external sd card(your choice) With device connected to pc, open command prompt and type in "adb reboot recovery" (without quotes) and the device will boot into recovery mode
5- Now that we have an English recovery, the translations below aren't really needed. However, I'm going to leave them up for a few days, just until everybody can transition to the English recovery. They will be deleted after that!
Recovery Main Menu: -Reboot -Install from SD card -Wipe Data/Factory Reset -Wipe Cache -Backup&Restore -Mount/Format -Advanced
Install From SD Card Menu: -Install zip from external SD -Apply update.zip -Unknown* -Install zip from internal SD
Backup&Restore Menu: -Backup -Restore -The rest are unknown*
Advanced Menu: -Reboot Recovery -Wipe Dalvik Cache -The rest are unknown*
To install ROM- In recovery mode, Factory Reset/Wipe Cache/Wipe Dalvik Cache. Then choose install zip from sd card(then choose internal or external and locate the ROM you want to install) After that you need to do the same thing to install the gapps package(you need the gapps package for google apps to function) once all is done, reboot and wait(it takes a while to boot the first time after flashing new ROMs, it has to rebuild the Dalvik cache)
NOTE: In case you aren't familiar with flashing ROMs, once you click on something( "backup" for example) a menu pops up pretty much asing you if you're sure you want to do that. It will have a bunch of lines of the same thing(which is no) and then one of the lines will have a bunch of writing beside it(which means yes). Also BEFORE you flash any ROMs, make sure you factory reset/wipe cache/and wipe dalvik cache, then you can flash the ROM and gapps package
*These will be updated regularly, as I discover what they are **More ROMs to come!
Internal Memory
The "BLU Quattro 4.5" has 4GB internal memory partitioned into 0.98GB for ROM and apps and an internal usb-memory of 1.63GB.
Is it possible to merge or resize the partitions?
I have 16GB external SD so the 1.63GB internal reserved usb-memory is useless and I still having trouble out of space in primary partition.
Thanks and sorry my english =/
TechSoft said:
Found this online. *****this is not my work****** All credit goes to the author quattrodevelopment.blogspot.com
Here is a step by step with roms included for the 4.5 quattro Not the HD or 5.7 HD maybe soon.
Disclaimer: These ROMs/Recoveries are only intended for the BLU Quattro 4.5, or the K-Touch v9(which is the chinese version) These WILL NOT work on the 4.5HD or 5.7HD devices(I will release ROMs/Recoveries specifically for your device at a later time)
Drivers: https://copy.com/BUMmsS9rhLJe
English Recovery: https://copy.com/XZxTDht2lQiz
Gapps(4.2) https://copy.com/utkbZgwRpsVB
Gapps(4.1) https://copy.com/pSd8SsqU9pdI
ROMs With Less Bugs: MIUI v5 (4.1) https://copy.com/sbmcN6PHwFfi CM/AOKP Hybrid? JB (4.1) https://copy.com/VeLz1VLbkNNI Shendu ROM 4.1(Modified/Tweaked by me) https://copy.com/NwiFnlO8JAek
ROMs With More Bugs: Cyanogenmod 10.1 (4.2) https://copy.com/8kt2EAU2ll8y
1- Download the drivers from link posted above, and extract it to the folder of your desire. Now turn the phone off, and hold Vol+ (volume up button) and Power button at the same time until you see a green screen, then release both buttons immediately. You should now be in APX mode(nvflash) it will be a black screen
2- Connect phone to computer via usb cable. Now you should get a pop-up window about installing drivers, you're going to want to choose to browse computer for driver software manually. Then choose let me pick from a list of device drivers on my computer, and click have disk. Now you're going to browse to the location where you extracted the drivers to, and click on it(Ignore warning if it pops up, and choose install)
3- Assuming everything went as planned, now download the recovery and extract it to the location you desire(must be in a directory that you can issue adb commands from) inside of that folder, locate a file named recovery.bat. Double click on that file and a command prompt with a bunch of chinese pops up. Give it a second and press enter, it will go through the process and flash a recovery onto your phone
4- After everything is done, hold down the power button for about ten seconds(until the device powers off) Power the device back on normally, and download the ROM/ROMs if you haven't already and place them on the internal or external sd card(your choice) With device connected to pc, open command prompt and type in "adb reboot recovery" (without quotes) and the device will boot into recovery mode
5- Now that we have an English recovery, the translations below aren't really needed. However, I'm going to leave them up for a few days, just until everybody can transition to the English recovery. They will be deleted after that!
Recovery Main Menu: -Reboot -Install from SD card -Wipe Data/Factory Reset -Wipe Cache -Backup&Restore -Mount/Format -Advanced
Install From SD Card Menu: -Install zip from external SD -Apply update.zip -Unknown* -Install zip from internal SD
Backup&Restore Menu: -Backup -Restore -The rest are unknown*
Advanced Menu: -Reboot Recovery -Wipe Dalvik Cache -The rest are unknown*
To install ROM- In recovery mode, Factory Reset/Wipe Cache/Wipe Dalvik Cache. Then choose install zip from sd card(then choose internal or external and locate the ROM you want to install) After that you need to do the same thing to install the gapps package(you need the gapps package for google apps to function) once all is done, reboot and wait(it takes a while to boot the first time after flashing new ROMs, it has to rebuild the Dalvik cache)
NOTE: In case you aren't familiar with flashing ROMs, once you click on something( "backup" for example) a menu pops up pretty much asing you if you're sure you want to do that. It will have a bunch of lines of the same thing(which is no) and then one of the lines will have a bunch of writing beside it(which means yes). Also BEFORE you flash any ROMs, make sure you factory reset/wipe cache/and wipe dalvik cache, then you can flash the ROM and gapps package
*These will be updated regularly, as I discover what they are **More ROMs to come!
Click to expand...
Click to collapse
Please rename this For Others Such as [GUIDE]BLU Quattro HowtoRoot/Rom list. Thanks for the awesome Guide!
alanfrank said:
The "BLU Quattro 4.5" has 4GB internal memory partitioned into 0.98GB for ROM and apps and an internal usb-memory of 1.63GB.
Is it possible to merge or resize the partitions?
I have 16GB external SD so the 1.63GB internal reserved usb-memory is useless and I still having trouble out of space in primary partition.
Thanks and sorry my english =/
Click to expand...
Click to collapse
I've found this: http://forum.xda-developers.com/showthread.php?t=1171531
Any idea if this can be used with another phone them the LG one he have used in the guide?
I cant post in the thread because Im new user here =/
problem
I have done everithing you said, and my cell freezes on boot forever, now what????
BLU Quattro 4.5 HD & 5.7
Need to know how to restore both devices to stock. Any aplication ODIN like to restore it back to stock from the download mode?
Please help me root, i try binary method but i just get boot loop.
Recovery + Root My experience
Hello... I got my BLU Quattro 4.5 (D440) a while back, didn't fuzz with it much right off. The Stock ROM was sluggish at best thought there was even an issue with the Digitizer/screen. But this thread was extremely helpful. I am now running Shendu ROM 4.1.2 one of the suggested ROM's above. I tried the other 2 first and they were mostly in Chineese and I had an especially hard time getting them switched over to English. Either way onward to the point. I have put together a few helpful tips-tricks for my experience with this phone and its phoenix transition to an awesome handset. Thats right now this is my daily driver and I love it! See below hope its helpful.
BLU Quattro 4.5 (440D) GSM Recovery+Root
These steps for this phone only!! Not responsible for any issues.
1. download ROM's, Recovery, & Driver from XDA (this thread)
http://forum.xda-developers.com/showthread.php?t=2327417
2. Enable USB Debugging! Go into Apps-Settings-DevOptions - Check box for USB Debug
3. Have original USB cord if handy! I tried with a Samsung OEM cable but no luck getting drivers to stick. Use original is best. (If you have one.)
Plug in USB Cord to PC then Phone and see if windows detects drivers. let it. It wont get the ones u need later, but what it does find is for USB storage. (you can move over your ROM's/Gapps to storage, downloads folder is a good spot).
4. Go to... http://junefabrics.com/android/downloadold.php to get pdanet software. Install it and it will give i the right drivers for ADB support. I used 4.01 to match the android version currently on my phone.
5. Extract the Driver provided from XDA. Put it in a folder with the ADB commands. Or you can get it all here... http://downloadandroidrom.com/file/GalaxyNexus/rooting/GalaxyNexusRootNew.zipn <-- I know this isn't for BLU but, if you extract this to a folder, and also add the drivers extracted to it as well this works! I've done it.
6. Extract the English Recovery to the same folder.
7. Turn off your phone. Hold down Vol up and Power button for about 5-9 seconds. Once you see a green screen let go of both. Screen may flicker then go black but the icons at the bottom will stay lit. You are now in APX mode (nvflash) mode. (as stated above in original post)
8. Check your Win 7 PC device manager. For a Phone device with ADB. If you you may need to update driver with the one that came from XDA, but the PDANet software should make it work.
8. Go to the folder and find Recovery.bat file (may have Chinese in file name. Double click and a command prompt window will pop up with a bunch of unknown characters, wait 5 sec then hit enter. The batch file should take of pushing the necessary recovery through ADB to the phone. It will error if it can't.
9. If completes OK. Push power for 7-9 seconds to power off the phone. Hit power like normal to turn it back on. It will boot up like normal (or it should).
10. USB is still connected this whole time and you can open a command prompt window. Navigate to the folder you placed the Recovery into. Something like user/username/desktop/BLU/recovery..etc)
Type ADB devices....it should show you that is is connected to your device. Then type " adb reboot recovery " and the device should reboot, give it some time.
11. Once in recovery. Best to do a backup of the original ROM & system. that way you can get back into recovery if anything goes wrong and wipe out the problem by restoring and starting again.
After you backup === you can get into recovery without the command being typed in or even being connected to your PC.... By holding Vol up + Power till you see the green screen then let go of power but keep holding Vol up till you see the BLU Products boot screen then let go ===
Clockworkmod Recovery should be on your screen.
you can reboot phone now and get back to original with no changes. Or you can venture into the world of loading ROM's (There in your downloads folder if you saved them in Step 3)
ROM 101
BACKUP-BACKUP-BACKUP 1st thing once in Recovery ...can't stress enough how much of trouble you can keep yourself out of by keeping an original backup.
As I stated before the Shendu ROM + Gapps is running smooth and all features I've been trying are working flawlessly!! Thanks to original post for getting me going. Just thought I'd add my 2 Cents.
Ok, here are the BEST 2 ROMS for this Phone:
Android 4.0.4(close to vanilla) : MEGA
Cyanogenmod 10.2 (Android 4.3.1) : (some audio and video issues, in BETA version ) MEGA
Need to merge internal partitions ? (merge memories) this one really "resize" the partitions (first one 1,7GB, another one new size is 2Mb) the flash.cfg file you need to flash:
This phone dont have notificaion led, fixed with this app: MEGA (flash the botton menu buttons)
Altomugriento said:
Ok, here are the BEST 2 ROMS for this Phone:
Android 4.0.4(close to vanilla) : MEGA
Cyanogenmod 10.2 (Android 4.3.1) : (some audio and video issues, in BETA version ) MEGA
Need to merge internal partitions ? (merge memories) this one really "resize" the partitions (first one 1,7GB, another one new size is 2Mb) the flash.cfg file you need to flash:
This phone dont have notificaion led, fixed with this app: MEGA (flash the botton menu buttons)
Click to expand...
Click to collapse
Can you explain the merge memories procedure? it will be reaaaaally needed!!
tryed from a spanish forum with no luck
thanks
dinizbruno said:
Can you explain the merge memories procedure? it will be reaaaaally needed!!
tryed from a spanish forum with no luck
thanks
Click to expand...
Click to collapse
Do you try the procedure posted in 3dgames . com . ar? ( its my work translated from the 592zn page, all the credits for the chinesse people)
Anyone tried the K-touch V9 kit kat in the BLU??
www
needrom
com/
download/
k-touch-v9-miui-v5-kk
Yes, those roms (v5) are very slow. Just use the 4.0.4 stock.
I want to try the JB stock, but i can´t find the official one anywhere.
Blu quattro 4.5 official rom to download, after you delete the bloatware and put a nice and clean theme you´ll get a nice speed.
orig D440 (quattro 4.5) rom
You can find the rom on google plus under BLU Products Development search for the model!
Hope that helps. I took your advice tonight and I am back running old school. Works ok husfar
I need phone.apk of this rom for Blu Quattro
Trozzul said:
Please rename this For Others Such as [GUIDE]BLU Quattro HowtoRoot/Rom list. Thanks for the awesome Guide!
Click to expand...
Click to collapse
I need phone.apk for blu quatro
please send me the file
[email protected]
So I installed TWRP recovery backed up my stock os and flashed cyanagen mod 11
After a week or so I went in the cyanagen mod updates and started updating, everything worked
but now when I tried to flash in to my stock rom I go to recovery and I see that I have Clockwork revovery insted of TWRP
so I was stupid and i flahsed TWRP and didnt unistall clockwork mod
When i went in the recovery i had clockworkmod and then I rebooted and went in to TWRP
Now im stuck in 2 recoverys and cant go to cyanagen
I really need help
im using the LG G2 D802
gamehero said:
So I installed TWRP recovery backed up my stock os and flashed cyanagen mod 11
After a week or so I went in the cyanagen mod updates and started updating, everything worked
but now when I tried to flash in to my stock rom I go to recovery and I see that I have Clockwork revovery insted of TWRP
so I was stupid and i flahsed TWRP and didnt unistall clockwork mod
When i went in the recovery i had clockworkmod and then I rebooted and went in to TWRP
Now im stuck in 2 recoverys and cant go to cyanagen
I really need help
im using the LG G2 D802
Click to expand...
Click to collapse
I don't know if I understood you but just to be sure; you get in recovery mode CWM and on reboot TWRP?
I don't think you will like this solution but probably you will get your phone to work again xD (you will lose your data)
First of all you need:
- Android SDK bundle (google it, you will find it) on your Computer
- And a Rom you want to sideload (In your case the Cyanogen Rom)
- Cwm
Follow this steps:
1. go to the SDK bundle folder you downloaded -> go to sdk
-> go to platformform-tools
-> copy your ROM (ZIP-file) inside that folder
-> and name it to ROM.zip (so you won't need to write down a longname in cmd afterwards)
2. go to the SDK bundle folder you downloaded -> go to sdk
-> now press [shift] + [right mouse button] on platformform-tools (folder) to open cmd
3. Reboot your device into recovery mode (use cwm)
4. Go to “Mounts & Storage” and make sure that you can see “Unmount /sdcard/” and “Unmount /system/” (If they do not show this automatically, just press each one once respectively as pressing just toggles Mount and Unmount).
5. Now connect your device to the PC.
6. Once the phone is connected to the PC type “adb devices” in the cmd. If it returns a long alphanumeric string the phone is successfully connected in ADB mode. (if not look out for a usb driver for your phone; most time the problem lies in there)
7. Now type “adb push ROM.zip /sdcard/ROM.zip” (replace the word ROM if didn't named it)
8. This may take a while so be patient.
9. Once the process is complete you’ll see a message like <12345678kb to 1234567kb> on the cmd window.
10. Now unplug the device.
11. Go to the main screen of recovery and perform factory reset, wipe cache partition and then in advance menu wipe Dalvik cache. (Now you will lose your data for sure xD)
12. Now go to install zip from sdcard and choose the zip file you just transferred.
13. Once the process is complete, reboot the device
Hope this will help you.
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
If you use TWRP there are some similar step by step guides ( maybe you should look for sideload)
GuiltyGod said:
I don't know if I understood you but just to be sure; you get in recovery mode CWM and on reboot TWRP?
I don't think you will like this solution but probably you will get your phone to work again xD (you will lose your data)
First of all you need:
- Android SDK bundle (google it, you will find it) on your Computer
- And a Rom you want to sideload (In your case the Cyanogen Rom)
- Cwm
Follow this steps:
1. go to the SDK bundle folder you downloaded -> go to sdk
-> go to platformform-tools
-> copy your ROM (ZIP-file) inside that folder
-> and name it to ROM.zip (so you won't need to write down a longname in cmd afterwards)
2. go to the SDK bundle folder you downloaded -> go to sdk
-> now press [shift] + [right mouse button] on platformform-tools (folder) to open cmd
3. Reboot your device into recovery mode (use cwm)
4. Go to “Mounts & Storage” and make sure that you can see “Unmount /sdcard/” and “Unmount /system/” (If they do not show this automatically, just press each one once respectively as pressing just toggles Mount and Unmount).
5. Now connect your device to the PC.
6. Once the phone is connected to the PC type “adb devices” in the cmd. If it returns a long alphanumeric string the phone is successfully connected in ADB mode. (if not look out for a usb driver for your phone; most time the problem lies in there)
7. Now type “adb push ROM.zip /sdcard/ROM.zip” (replace the word ROM if didn't named it)
8. This may take a while so be patient.
9. Once the process is complete you’ll see a message like <12345678kb to 1234567kb> on the cmd window.
10. Now unplug the device.
11. Go to the main screen of recovery and perform factory reset, wipe cache partition and then in advance menu wipe Dalvik cache. (Now you will lose your data for sure xD)
12. Now go to install zip from sdcard and choose the zip file you just transferred.
13. Once the process is complete, reboot the device
Hope this will help you.
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
If you use TWRP there are some similar step by step guides ( maybe you should look for sideload)
Click to expand...
Click to collapse
So I got to step 4 and I see the mount system but I don't see umount sdcard
Then mount system or skip this part
5,6 and 7 are the most important part.
Can you push the Rom on your phone?
GuiltyGod said:
Then mount system :S
5,6 and 7 are the most important part.
Can you push the Rom on your phone?
Click to expand...
Click to collapse
adb push ROM.zip /sdcard/ROM.zip if I dont have the sdcard umonted will this still work?
I know I am repeating myself more or less (because I always edit my posts xD)
Well as long as you can push your file there shouldn't be sny problem
GuiltyGod said:
I know I am repeating myself more or less (because I always edit my posts xD)
Well as long as you can push your file there shouldn't be sny problem
Click to expand...
Click to collapse
so I wrote the command and it sad "5143kb/s «241840314 bytes in 45.912s»"
then i went install the zip and I can't find it
ok i went and mounted the data , pushed the file and installed it, thank you so much
But now i need to install the stock backup that I did with TWRP
That's pretty weird xD Because you get the message for a successful transfer but can't find the Zipfile.
You could try to push the Zipfile again and don't wipe anything at all (because you already wiped everything) and try to find the Zip file again to flash it.
Btw what does CWM gives you as options if you click install Zip files?
GuiltyGod said:
That's pretty weird xD Because you get the message for a successful transfer but can't find the Zipfile.
You could try to push the Zipfile again and don't wipe anything at all (because you already wiped everything) and try to find the Zip file again to flash it.
Btw what does CWM gives you as options if you click install Zip files?
Click to expand...
Click to collapse
it's all good now but now i have CWM and i need TWRP to install my stock backup
Watch this video (shows you how to change recovery in general):
http://m.youtube.com/watch?v=jnESTcH2ioA
And read this instructions if you still have some doubts and want to go for sure (recovery for LG2 D802):
http://forum.xda-developers.com/showthread.php?t=2472223
Sry I am a bit lazy right now xD Came back from work
i changed the permission of system folder to rw--r--r--
now, my phone is stuck on logo not even bootanimation
is there any method to recover my phone
(i have stock recovery )
dont just laugh please help me
pranavraut033 said:
i changed the permission of system folder to rw--r--r--
now, my phone is stuck on logo not even bootanimation
is there any method to recover my phone
(i have stock recovery )
dont just laugh please help me
Click to expand...
Click to collapse
You need the 'x' (executable) permission for a directory for being able to access its contents.
You can't do anything with stock recovery. Factory Reset will not help I guess.
The only way is booting or flashing a custom recovery and making things right.
Search and Download a custom recovery for your phone. Rename it to recovery.img and place in D: drive (your wish)
Install Minimal ADB and Fastboot in PC (Google it)
Switch off the mobile.
Hold any button combination like Power + Volume Up (or whatever, it's specific to phone) which will take you to a boot menu.
Connect phone to PC.
Select fastboot option in that menu from phone.
Now open Minimal ADB and Fastboot desktop icon and type the following:
Code:
fastboot boot recovery D:\recovery.img
Download and flash this zip from that recovery: Aroma File Manager
Now, you'll see different root directories of the phone.
Hold 'system' and select 'Change Permission'
Set Permission rwx r-x r-x
Now reboot. Your phone should work
GokulNC said:
You need the 'x' (executable) permission for a directory for being able to access its contents.
You can't do anything with stock recovery. Factory Reset will not help I guess.
The only way is booting or flashing a custom recovery and making things right.
Search and Download a custom recovery for your phone. Rename it to recovery.img and place in D: drive (your wish)
Install Minimal ADB and Fastboot in PC (Google it)
Switch off the mobile.
Hold any button combination like Power + Volume Up (or whatever, it's specific to phone) which will take you to a boot menu.
Connect phone to PC.
Select fastboot option in that menu from phone.
Now open Minimal ADB and Fastboot desktop icon and type the following:
Code:
fastboot boot recovery D:\recovery.img
Download and flash this zip from that recovery: Aroma File Manager
Now, you'll see different root directories of the phone.
Hold 'system' and select 'Change Permission'
Set Permission rwx r-x r-x
Now reboot. Your phone should work
Click to expand...
Click to collapse
bro i tried but it seem my phone dont support custom recovery
it shows
partition dont support flash
what to do
go to shop for that?
pranavraut033 said:
i changed the permission of system folder to rw--r--r--
now, my phone is stuck on logo not even bootanimation
is there any method to recover my phone
(i have stock recovery )
dont just laugh please help me
Click to expand...
Click to collapse
Device model???
Newyork! said:
Device model???
Click to expand...
Click to collapse
datawind pocketsurfer 3g5
pranavraut033 said:
datawind pocketsurfer 3g5
Click to expand...
Click to collapse
Here's the stock ROM link:
http://xdafirmware.com/datawind-ps3g5
Choose the correct version there and flash it from latest SP flash tool. (v.5.15something)
Select system partition first and flash it.
See if phone boots and works.
If it doesn't, flash the whole stock ROM.
I think you have messed the BIOS... If the permission of system partition is changed to incorrect values the flashing of ROM im is impossible...try to resolve by service centre ✌ I hope ur phone get fixed asap
Sent from my HM NOTE 1LTE using XDA Free mobile app
Today I will teach you how I change my rom from miui china to miui eu rom. I am having problems regarding the tutorials on youtube because as of now there is still no English tutorials on it. But first let me give you some idea on how I did it. I am only using windows 7 professional and so I did tried to download the following:
1. platform tools
2. adb set up
3. adb folder
4. Disable_Dm-Verity_ForceEncrypt_02.04.2019
5. Patched_fstab+vbmeta+thermal
6. TWRP-3.2.3-TwrpBuilder-violet-2019-03-22_20-44.img
7. Latest EU Rom on your redmi note 7 pro
The following guides that I use is from Technobuzz "https://www.youtube.com/watch?v=uDcrO61AnZg" Its not me who made this but only modified some methods to make it work on mine.
But to no avail the platform tools doesnt work because of missing dll issues so possible its because I use an older model of windows. I tried to use adb folder but encountered some problems that in no luck i cant format the userdata till i got messed up my device and so Im having this error on recovery saying that system doesnt work anymore and need to press powerbutton in order for me to shut down my phone. and thus I brick my phone.
Ok fast forward, so I did brick my phone then and I go the recovery due to system has been corrupted and so I tried to go to download "violet_images_V10.2.5.0.PFHCNXM_20190316.0000.00_9.0_cn_8e2009cdc7.tgz" in order to reflash my phone using miflash. Btw I came from miui 10.3.5.0 China stable rom so this means I downgraded my phone. Its okay for me cause I can root or install custom recovery more efficiently.
Instructions:
1. Install the adb set up
2. Make sure you unlock your bootloader already.
3. Put the TWRP-3.2.3-TwrpBuilder-violet-2019-03-22_20-44.img and rename it to recovery.img
4. Put the Disable_Dm-Verity_ForceEncrypt_02.04.2019 and Patched_fstab+vbmeta+thermal on your memory card and your latest eu rom zip file.
5. Downgrade your phone to miui 10.2.5.0 china rom to ensure a good installation of your twrp
6. Go to adb folder open cmd from there(right click and click open command window here)
7. Switch off your phone then hold volume down then power button to enter fastboot mode
8. Connect your phone to the computer via USB
9. Type: fastboot devices(It will list down the devices attach with the number to be able to make sure that your device is attached)
10. Type: fastboot erase userdata and press enter(It will run wait for it to end)11. Type: fastboot flash recovery (It will run wait for it to end)
9. Disconnect your phone then hold volume up then click power button to enter recovery mode
10. Go to wipe section then format type yes( It will run wait for it to end)
11. Go to Installation click select storage then choose memory card
12. Install Patched_fstab+vbmeta+thermal and Disable_Dm-Verity_ForceEncrypt_02.04.2019
13. Go to wipe section then Advance wipe wipe the ff: dalvik cache, cache, system and data just ignore the vendor then swipe to wipe.
14. Install your latest eu rom on your sd card.
15. Install Disable_Dm-Verity_ForceEncrypt_02.04.2019 for assurance
16. Install Magisk optional
17. Reboot your phone
and thats it. Pls do credits to the developer not mine thank you. Technobuzz