Database Info

[Q] home to root

please dont shout, just take pitty on me.
I have been getting into the world of rooting and have used the HTC Bootloader unlock, and have installed clockwork. i then had a few issues but managed to get some roms working but Im still not fully understanding exactly what im doing.
but i can flash by:
1. Power on'ing and vol down,
2. fastboot - bootloader - loading PG58IMG
3. recovery -wipe data/factory reset - yes
4. install zip from sdcard - chose zip from sdcard - Sensation_3.32.401.5_deodexed - Yes
5. wait for: install from sdcard complete
7. go back - rebootsystem now
Ive tried a few roms, 2 didnt work but this is the 3rd (Sensation_3.32.401.5_deodexed) that has loaded up.
My issue is I dont get how to get my wireless to work. If someone could give simple instructions Id be more than helpfl as all guides i read are too full of jargon. . . . .im not afraid to hit your thanks buttons . . .
Thanks
Tim
PS
my cid is VADAP001
my MID is PG5813000

taffytim said:
please dont shout, just take pitty on me.
I have been getting intot he world of routing and have used the HTC Bootloader unlock, and have installed clockwork. i then had a few issues but managed to get some roms working but Im still not flly understanding exactly what im doing.
but i can flashing by
1. Power on'ing and vol down,
2. fastboot - bootloader - loading PG58IMG
3. recovery -wipe data/factory reset - yes
4. install zip from sdcard - chose zip from sdcard - Sensation_3.32.401.5_deodexed - Yes
5. wait for: install from sdcard complete
7. go back - rebootsystem now
Ive tried a few roms, 2 didnt work but this is the 3rd (Sensation_3.32.401.5_deodexed) that has loaded up.
My issue is I dont get how to get my wireless to work. If someone could give simple instructions Id be more than helpfl as all guides i read are too full of jargon. . . . .im not afraid to hit your thanks buttons . . .
Thanks
Tim
Click to expand...
Click to collapse
Hi,
Are you talking about wifi?
Have you got a router?

When you use HTC Dev to unlocj your bootloader it does unlock the Recovery, System, and Boot partitions to allow your device to write to those partitions and not just read rose partitions. But Terri is a catch, if you want to flash a custom recovery you have to use ABD fastoot commands to flash it. When you flash as ROM in a .zip file via Recovery, it only flashes the System partition. You then have to open the dot zip file and extract the boot.img and then use ADB fastboot commands to flash the boot.img to your boot partition. If you do not you will still have the boot.img of the ROM you was using before you flashed te New ROM.
Now let me explain the boot.img a little so you know why it is so important. The boot.img does just watt te name implies, it is what boots the Android ROM on your device. Now let me explain this a little further, the Android OS runs on top of eat is called a Lenox kernel. This means that your bootloader boots the Lenox kernel and the hardware of the device. The Lenox kernel then boots the Android OS. The kernel is also te connection between the hardware and the Android OS. So you see if the kernel is not compatible with the system that is on te system partition you will have troubles like WiFi not working or other I hardware reliant functions. So when you flash a new ROM and you are HTC Dev unlocked you will have to flash the boot.img for te ROM are you will more than likely have troubles.

Malybru, i do have a router but my wifi wont turn on so i cant connect to it.

T-Macgnolia said:
When you use HTC Dev to unlocj your bootloader it does unlock the Recovery, System, and Boot partitions to allow your device to write to those partitions and not just read rose partitions. But Terri is a catch, if you want to flash a custom recovery you have to use ABD fastoot commands to flash it. When you flash as ROM in a .zip file via Recovery, it only flashes the System partition. You then have to open the dot zip file and extract the boot.img and then use ADB fastboot commands to flash the boot.img to your boot partition. If you do not you will still have the boot.img of the ROM you was using before you flashed te New ROM.
Now let me explain the boot.img a little so you know why it is so important. The boot.img does just watt te name implies, it is what boots the Android ROM on your device. Now let me explain this a little further, the Android OS runs on top of eat is called a Lenox kernel. This means that your bootloader boots the Lenox kernel and the hardware of the device. The Lenox kernel then boots the Android OS. The kernel is also te connection between the hardware and the Android OS. So you see if the kernel is not compatible with the system that is on te system partition you will have troubles like WiFi not working or other I hardware reliant functions. So when you flash a new ROM and you are HTC Dev unlocked you will have to flash the boot.img for te ROM are you will more than likely have troubles.
Click to expand...
Click to collapse
That is very informative thanks T-Macgnolia. I understand the theorybut i cant work out the process?
How do i get to flash the boot image?
If i go into my rom folder on my pc then try to open the boot file i just get a Windows Disc Image Burner message box asking me to burn to disc.
I used to burn images using virtal drives when making dvds. Will i need to do the same again here with a virtual drive?
Can you break the process down for me?

taffytim said:
That is very informative thanks T-Macgnolia. I understand the theorybut i cant work out the process?
How do i get to flash the boot image?
If i go into my rom folder on my pc then try to open the boot file i just get a Windows Disc Image Burner message box asking me to burn to disc.
I used to burn images using virtal drives when making dvds. Will i need to do the same again here with a virtual drive?
Can you break the process down for me?
Click to expand...
Click to collapse
First you have to download and install the Android SDK. Here is a video by Elite Recognized Developer Adam Outler that shows you how to install the Android SDK. After you have the SDK installed and all the packages are downloaded and installed. Take the boot.img and copy it to the same folder in ADB that has fastboot in it. Now while you are in the folder with fastboot in it hold down the shift key and right click anywhere on the screen and select "open command promt here". This will open a command promt with you already on the right directory. Now boot your Sensation into Hboot by holding the volume down button down while booting your Sensation. when in Hboot select fastboot and connect your Sensation to your computer with your USB cable. Now type the following into the command promt.
Code:
fastboot flash boot boot.img
That is all it is to it. Also the boot.img is a iso file that is why you get that message when you try to open it. You have to use a Android kitchen or another program that can decompile the file if you want to open it and look around.

T-Macgnolia said:
First you have to download and install the Android SDK. Here is a video by Elite Recognized Developer Adam Outler that shows you how to install the Android SDK. After you have the SDK installed and all the packages are downloaded and installed. Take the boot.img and copy it to the same folder in ADB that has fastboot in it. Now while you are in the folder with fastboot in it hold down the shift key and right click anywhere on the screen and select "open command promt here". This will open a command promt with you already on the right directory. Now boot your Sensation into Hboot by holding the volume down button down while booting your Sensation. when in Hboot select fastboot and connect your Sensation to your computer with your USB cable. Now type the following into the command promt.
Code:
fastboot flash boot boot.img
That is all it is to it. Also the boot.img is a iso file that is why you get that message when you try to open it. You have to use a Android kitchen or another program that can decompile the file if you want to open it and look around.
Click to expand...
Click to collapse
You sir deserve a big pint of something great. Point by point I:
1. I already had sdk installed so didnt need to install this.
2. I cleared the phone back to factory with Recovery (Power on with holding -Vol, RECOVERY, Wipe data/Factory Reset, Power Off)
3. I went into HBOOT (by powering on holding down -vol)
4. Opened FASTBOOT and connected phone to computer via USB
5. Opened up command prompt on PC (start menu, typed cmd in the search box)
6. I then Typed the following:
7. "cd c:\Android" (to get me into the folder where my files are)
8. "fastboot flash boot boot.img"
9. this then loaded my boot file and bosh, Im done.
I then restarted the phone and bobs your mothers brother Im using wiresless again. Its such an easy process but on the first go it seems like rocket science.
You cant appreciate how greatful i am for your help. Thank you more than a lot.
If i chose a different ROM at what point is it best to do this stage? Are you able to do this to the boot image before you use recovery to 'insatll zip from sd card'? Or do you have to install then come back to it like i did?

For every custom rom you install you need to follow the same procedure.
1. First flash/install the rom via recovery
2. Get the boot.img and flash it via fastboot (some rom's have more than one kernel then choose the best you want)
As long as you stay in HTC unlocked bootloader the above steps are necessary to flash the rom completely to prevent bootloops and wifi errors
sent from my blazing fast pyramid through sonic waves

ta gane shp, this is a good place with good people

Thanks this post helped me a lot!
I got Android Revolution fully working, but I'm trying to flash the newest OC Kernel of SebastianFM over it. But his zip doesn't have a "boot.img", it does however contain the following: mkbootimg, mkbootimg.sh and unpackbootimg. Is it any of those I need to flash, if not, which "boot.img" do I flash then?

Asskicker2 said:
Thanks this post helped me a lot!
I got Android Revolution fully working, but I'm trying to flash the newest OC Kernel of SebastianFM over it. But his zip doesn't have a "boot.img", it does however contain the following: mkbootimg, mkbootimg.sh and unpackbootimg. Is it any of those I need to flash, if not, which "boot.img" do I flash then?
Click to expand...
Click to collapse
Hi,
I believe the boot.img refers to the ROM you are flashing.
This is a kernel.
So,make a nandroid backup,
wipe cache and dalvik,
and flash the kernel from the root of the sd card,choosing install zip from sd card in recovery.

malybru said:
Hi,
I believe the boot.img refers to the ROM you are flashing.
This is a kernel.
So,make a nandroid backup,
wipe cache and dalvik,
and flash the kernel from the root of the sd card,choosing install zip from sd card in recovery.
Click to expand...
Click to collapse
Yeah, that isn't working.
Wifi ain't working now.

Asskicker2 said:
Yeah, that isn't working.
Wifi ain't working now.
Click to expand...
Click to collapse
Hi,
Just restore the nandroid backup you made.

malybru said:
Hi,
Just restore the nandroid backup you made.
Click to expand...
Click to collapse
Yeah, but I wanted to update to newest kernel. Thanks though

Doesn't work with me.
taffytim said:
You sir deserve a big pint of something great. Point by point I:
1. I already had sdk installed so didnt need to install this.
2. I cleared the phone back to factory with Recovery (Power on with holding -Vol, RECOVERY, Wipe data/Factory Reset, Power Off)
3. I went into HBOOT (by powering on holding down -vol)
4. Opened FASTBOOT and connected phone to computer via USB
5. Opened up command prompt on PC (start menu, typed cmd in the search box)
6. I then Typed the following:
7. "cd c:\Android" (to get me into the folder where my files are)
8. "fastboot flash boot boot.img"
9. this then loaded my boot file and bosh, Im done.
I then restarted the phone and bobs your mothers brother Im using wiresless again. Its such an easy process but on the first go it seems like rocket science.
You cant appreciate how greatful i am for your help. Thank you more than a lot.
If i chose a different ROM at what point is it best to do this stage? Are you able to do this to the boot image before you use recovery to 'insatll zip from sd card'? Or do you have to install then come back to it like i did?
Click to expand...
Click to collapse
I tried this with OrDroid and ViperS laterst versions and the wifi still doesnot work with my device.
It does nor even turn on from the settings, someone please help!

Wi-Fi Issues
theumairahmad said:
I tried this with OrDroid and ViperS laterst versions and the wifi still doesnot work with my device.
It does nor even turn on from the settings, someone please help!
Click to expand...
Click to collapse
Post 3 in this thread explains exactly where the problem is. But ........you will never unlock that boot partition if ur phone is S-ON. The trick with the wire works...it took me couple of times to do it but it worked. Then.....the lates ViperS version does it for you. You do not have to use ADB or whatever that program was to flash the boot.img It is all in the ROM. I even flashed the newest bricked 1.4 kernel on top.....but that 3rd comment is the key to all problems with Wi-Fi and other kernel issues:fingers-crossed::fingers-crossed::fingers-crossed::fingers-crossed:

[Q] bad flash

Hi i have rooted and flashed the phone it got stuck on the htc screen so i tried factory reset bad idea now my phone will just go into the bootlader menu i can enable fastboot usb but it dont show up on computer but the computer makes a noise to say ive connected it i cant enable usb debugging because the phone wont come on i have tried to flash another boot img through fastboot with no luck im hoping its not bricked
please any help would be appreciated thanks

pl4yb0y78 said:
Hi i have rooted and flashed the phone it got stuck on the htc screen so i tried factory reset bad idea now my phone will just go into the bootlader menu i can enable fastboot usb but it dont show up on computer but the computer makes a noise to say ive connected it i cant enable usb debugging because the phone wont come on i have tried to flash another boot img through fastboot with no luck im hoping its not bricked
please any help would be appreciated thanks
Click to expand...
Click to collapse
Hmm. so you probably need to flash a recovery first.
then you will be able to use the recovery to mount usb and put a new rom on your "sd card"
Then you can flash the rom on your new recovery and don't forget to fastboot flash the boot.img.
edit: the all in one toolkit is great for things like this. It will put a new recovery on your phone with just a click of the button.
http://forum.xda-developers.com/showthread.php?t=1604677

tivofool said:
Hmm. so you probably need to flash a recovery first.
then you will be able to use the recovery to mount usb and put a new rom on your "sd card"
Then you can flash the rom on your new recovery and don't forget to fastboot flash the boot.img.
Click to expand...
Click to collapse
Thanks for the reply but i dont know how to do this ?
could you please explain it ?

pl4yb0y78 said:
Thanks for the reply but i dont know how to do this ?
could you please explain it ?
Click to expand...
Click to collapse
I just edited my original post. just in case you didn't know how. I guess I was a little slow.
Also I can't remember if a bootloader factory reset relocked your phone but you might want to check that too. up on top it would say locked or relocked. If it still says unlocked you don't have to do that step again. Like you did when you first rooted the phone.
(all in one tool kit is great for unlocking and relocking too) just put a copy of that bin file in all in one tool kit (data file i believe, but it says what to do in that thread)

tivofool said:
I just edited my original post. just in case you didn't know how. I guess I was a little slow.
Also I can't remember if a bootloader factory reset relocked your phone but you might want to check that too. up on top it would say locked or relocked. If it still says unlocked you don't have to do that step again. Like you did when you first rooted the phone.
(all in one tool kit is great for unlocking and relocking too) just put a copy of that bin file in all in one tool kit (data file i believe, but it says what to do in that thread)
Click to expand...
Click to collapse
hi i have got the tool kit run twrp s3 now i have a black htc logo screen on what next

pl4yb0y78 said:
hi i have got the tool kit run twrp s3 now i have a black htc logo screen on what next
Click to expand...
Click to collapse
Your phone is an s3?
My phone is an S4 as are I would guess the majority of users. I think the s3 is the international version. If you are on T mobile then it's a s4.
Ok,,,
so .... if your phone is an s3 version then you will have to check that the Rom you download is specific for your phone as most of the Roms on this site are for the s4 version.
you need to go to your recovery. press the volume down button and hold it. Then press the power button (don't hold it). That will get you to recovery.
when in twrp recovery you will see a mounts button. hit that then the next screen will have mount usb. then you will be able to move a rom you downloaded on your computer to your phone.
then you can install the rom zip in twrp.
then from your computer, I assume you know how to flash a boot.img
put a boot.img in your fastboot folder, open up a comand prompt.
fastboot flash boot boot.img
if you wanted a different recovery than you are using, find the download the recovery. *I would rename the recovery to recovery.img
fastboot flash recovery recovery.img
(I only mention a different recovery because in some of the Rom threads you might read that you can only install a particular rom with an older version of twrp.)
I'm not sure of your skill or experience with all of this. If you are very new to it (then you are probably really frustrated) have no fear there is a little bit to learn but not that much. Just keep reading the development thread and the guides in it.

tivofool said:
Your phone is an s3?
My phone is an S4 as are I would guess the majority of users. I think the s3 is the international version. If you are on T mobile then it's a s4.
Ok,,,
so .... if your phone is an s3 version then you will have to check that the Rom you download is specific for your phone as most of the Roms on this site are for the s4 version.
you need to go to your recovery. press the volume down button and hold it. Then press the power button (don't hold it). That will get you to recovery.
when in twrp recovery you will see a mounts button. hit that then the next screen will have mount usb. then you will be able to move a rom you downloaded on your computer to your phone.
then you can install the rom zip in twrp.
then from your computer, I assume you know how to flash a boot.img
put a boot.img in your fastboot folder, open up a comand prompt.
fastboot flash boot boot.img
if you wanted a different recovery than you are using, find the download the recovery. *I would rename the recovery to recovery.img
fastboot flash recovery recovery.img
(I only mention a different recovery because in some of the Rom threads you might read that you can only install a particular rom with an older version of twrp.)
I'm not sure of your skill or experience with all of this. If you are very new to it (then you are probably really frustrated) have no fear there is a little bit to learn but not that much. Just keep reading the development thread and the guides in it.
Click to expand...
Click to collapse
Thank you for the reply yes i am getting stressed at this and i am new had a break before i smashed the phone now ive just got to find out what my phone is s3 or s4 ? google will help

when i connect my phone to the computer in recovery or flashboot it does not let me see it so i can not put rom on the hdd
(tried restart phone no luck tried restart comy no luck, cant get it to show phone ) all drivers installed
can i use the tool kit to flash recovery ?
phone on orange uk ,is it a s4 ?
thanks for the help guys with your knowledge i will get it working i pray!

pl4yb0y78 said:
when i connect my phone to the computer in recovery or flashboot it does not let me see it so i can not put rom on the hdd
(tried restart phone no luck tried restart comy no luck, cant get it to show phone ) all drivers installed
can i use the tool kit to flash recovery ?
phone on orange uk ,is it a s4 ?
thanks for the help guys with your knowledge i will get it working i pray!
Click to expand...
Click to collapse
do you have your box the phone came in?
Z520e is S4
Z560e is S3
So were you able to put twrp on your phone? when you are in boot loader and click on the recovery does it take you to twrp? Yes the all in one toolkit will flash a recovery for you. but you have your boot loader unlocked first.

tivofool said:
do you have your box the phone came in?
Z520e is S4
Z560e is S3
So were you able to put twrp on your phone? when you are in boot loader and click on the recovery does it take you to twrp? Yes the all in one toolkit will flash a recovery for you. but you have your boot loader unlocked first.
Click to expand...
Click to collapse
yes i now have the twrp in recovery it says enter password and cancel i tried both it was the s4 one that worked so im guessing its an s4
what will the next step be? (if i need anything please could you leave a link)
thanks for all the help starting to feel i might win lol

in twrp when you press "mounts" then press "mount usb", does your computer finally see your phone?
I was looking at your first post, you say that you rooted and flashed your phone. What do you mean by that? Did you download a ROM and attempt to flash it? Or did you "fastboot flash boot boot.img"?
If you are able to access your phone via computer it is as simple as downloading a rom on your computer moving it to your phone then in twrp "install from zip". Then fastboot flash the boot.img.
http://forum.xda-developers.com/showthread.php?t=1583427
how to flash fastboot
http://forum.xda-developers.com/showthread.php?t=1752270
if you are just fed up and want your phone back to stock then you will need to run an RUU.
http://forum.xda-developers.com/showthread.php?t=2094414
To run a RUU you would need to relock your bootloader.
in console type "fastboot lock oem" or use your all in one toolkit to relock it.
if that fails you will need to put your stock recovery back. (you need to have boot loader unlocked to do this)
on the clockworkmod recovery page the stock recovery is the second download link.
http://www.modaco.com/topic/353006-...ch-recovery-for-the-htc-one-s-stock-download/

Ok i am now really confused nothing works downloaded recovery roms they wont install always says failed tried to adb sideload it after google it failed again tried 3 recovery roms all fail what is going wrong icant get it to work
so far ive put twrp on it pressed mount so i can put rom on phone worked
pressed install pressed zip failed
pressed adb sideload then start on comy sent rom 100% install failed
reeboot phone still no os
tried this 3 times different roms all failed
please help

pl4yb0y78 said:
Ok i am now really confused nothing works downloaded recovery roms they wont install always says failed tried to adb sideload it after google it failed again tried 3 recovery roms all fail what is going wrong icant get it to work
so far ive put twrp on it pressed mount so i can put rom on phone worked
pressed install pressed zip failed
pressed adb sideload then start on comy sent rom 100% install failed
reeboot phone still no os
tried this 3 times different roms all failed
please help
Click to expand...
Click to collapse
Do you know how to FASTBOOT FLASH boot.img which is present inside the ROM.ZIP?
Try wiping data, cache, dalvik. Then reinstall.
Sent from my Nexus 7 using Tapatalk HD

khan.orak said:
Do you know how to FASTBOOT FLASH boot.img which is present inside the ROM.ZIP?
Try wiping data, cache, dalvik. Then reinstall.
Sent from my Nexus 7 using Tapatalk HD
Click to expand...
Click to collapse
thanks and yes i can do that i will try and get back to you

C:\adt-bundle-windows-x86_64-20130522\sdk\platform-tools>fastboot boot boot.img
creating boot image...
creating boot image - 16779264 bytes
downloading 'boot.img'...
OKAY [ 1.890s]
booting...
FAILED (remote: reproduce boot image with on-flash ramdisk error)
finished. total time: 1.926s
this is what i get when i try tried 3 imgs

pl4yb0y78 said:
C:\adt-bundle-windows-x86_64-20130522\sdk\platform-tools>fastboot boot boot.img
creating boot image...
creating boot image - 16779264 bytes
downloading 'boot.img'...
OKAY [ 1.890s]
booting...
FAILED (remote: reproduce boot image with on-flash ramdisk error)
finished. total time: 1.926s
this is what i get when i try tried 3 imgs
Click to expand...
Click to collapse
The command is:
Code:
fastboot flash boot boot.img

khan.orak said:
The command is:
Code:
fastboot flash boot boot.img
Click to expand...
Click to collapse
ok i try this i am only learning but getting there lol

[Discontinued][Recovery][Stock] XOLO Play T1000

In case you ever want to claim warranty.
Instructions:
Download ADB and recovery.zip.
Extract both to same folder.
Power down device.
Reboot into fastboot by pressing the 'Volume up + Power' buttons.
Connect phone to PC using USB cable
Open Command Prompt and CD to the ADB directory.
Type the command below
Code:
fastboot flash recovery recovery.img
Code:
fastboot reboot
Downloads:
ADB and Fastboot courtesy @ankur850 from here https://docs.google.com/file/d/0B1S0LCuXCnnmSWh6NGJmSE1BUWc/edit
Stock recovery from here: http://www.mediafire.com/download/j7h4u4x2nfnm676/recovery.zip
Hit Thanks :good: if this thread is helpful.
Refer this link for commonly asked questions before posting your doubts.

stuck at waiting for device
hi , i am trying to restore my xolo play to stock odexed rom provided at http://forum.xda-developers.com/showthread.php?p=44264063
. when i connected my phone , its saying waiting for the device. I know i am missing some drivers . Can you explain the procedure to install the drivers.
Thanks.
deepaktom said:
In case you ever want to claim warranty.
Instructions:
Download ADB and recovery.zip.
Extract both to same folder.
Power down device.
Reboot into fastboot by pressing the 'Volume up + Power' buttons.
Connect phone to PC using USB cable
Open Command Prompt and CD to the ADB directory.
Type the command below
Code:
fastboot flash recovery recovery.img
Code:
fastboot reboot
Downloads:
ADB and Fastboot courtesy @ankur850 from here https://docs.google.com/file/d/0B1S0LCuXCnnmSWh6NGJmSE1BUWc/edit
Stock recovery from here: http://www.mediafire.com/download/j7h4u4x2nfnm676/recovery.zip
Hit Thanks :good: if this thread is helpful.
Click to expand...
Click to collapse

sreekar said:
hi , i am trying to restore my xolo play to stock odexed rom provided at http://forum.xda-developers.com/showthread.php?p=44264063
. when i connected my phone , its saying waiting for the device. I know i am missing some drivers . Can you explain the procedure to install the drivers.
Thanks.
Click to expand...
Click to collapse
Try this
http://forum.xda-developers.com/showthread.php?p=43981028

installed drivers: but returns Failed
Hi i was able to install drivers. after lot of searching.
now when i sent command "astboot oem get_identifier_token" it is aying Failed.
when i searched , i found out that bootloader needs to be unlocked. can you explain in steps how to do this? and will i loose warrenty if i do this?
currently :
i did an ota update. its resulting in improper video playback. so i want to flash recovery rom.
thanks.
deepaktom said:
Try this
http://forum.xda-developers.com/showthread.php?p=43981028
Click to expand...
Click to collapse

sreekar said:
Hi i was able to install drivers. after lot of searching.
now when i sent command "astboot oem get_identifier_token" it is aying Failed.
when i searched , i found out that bootloader needs to be unlocked. can you explain in steps how to do this? and will i loose warrenty if i do this?
currently :
i did an ota update. its resulting in improper video playback. so i want to flash recovery rom.
thanks.
Click to expand...
Click to collapse
This one is not like other phones man. Boot loader is already unlocked
Sent from my XOLO Play using Tapatalk 2

sreekar said:
Hi i was able to install drivers. after lot of searching.
now when i sent command "astboot oem get_identifier_token" it is aying Failed.
when i searched , i found out that bootloader needs to be unlocked. can you explain in steps how to do this? and will i loose warrenty if i do this?
currently :
i did an ota update. its resulting in improper video playback. so i want to flash recovery rom.
thanks.
Click to expand...
Click to collapse
The bootloader is already unlocked & to flash recovery ,use instruction given by deepak or use app flashify from play store

Flashing with a custom rom.
har****181 said:
The bootloader is already unlocked & to flash recovery ,use instruction given by deepak or use app flashify from play store
Click to expand...
Click to collapse
hi,
from the link,
http://forum.xda-developers.com/wiki/index.php?title=Flashing_Guide_-_Android
i don't have custom recovery installed.
and i don't have a memory card.
what i need to do if i want to install odexed rom install.
does custom recovery installation involves rooting phone?
is it not possible to flash unrooted phones?
update:
i did
fastboot flash boot boot.img
from the boot.img file from odexed rom zip.
Is my warranty still intact?
what i did by flashing the boot partition?
boot.img is only 8 MB what is the other content present in the rom zip file and how its used?
thanks,
sreekar

sreekar said:
hi,
from the link,
http://forum.xda-developers.com/wiki/index.php?title=Flashing_Guide_-_Android
i don't have custom recovery installed.
and i don't have a memory card.
what i need to do if i want to install odexed rom install.
does custom recovery installation involves rooting phone?
is it not possible to flash unrooted phones?
update:
i did
fastboot flash boot boot.img
from the boot.img file from odexed rom zip.
Is my warranty still intact?
what i did by flashing the boot partition?
boot.img is only 8 MB what is the other content present in the rom zip file and how its used?
thanks,
sreekar
Click to expand...
Click to collapse
OK I'll spend some time here so you can understand. Warranty can be checked in most phones with locked bootloaders . ours is not locked. Bootloader locked means no change can be made unofficially by us.
The only way they can find warranty on our phone is if you use official root method.
For this purpose we have unofficial root method.
Now about partitions. /boot is the kernel. Its like drivers for your hardware.
/system is the os. It is either rooted or unrooted like in windows having admin account or normal account.
You can either use an OS which has already admin account by using a rooted ROM or you can use a limited unrooted ROM and then root it thereby making it an admin account.
Now recovery is a mini OS which will help you to recover your OS in case something is wrong. Stock recovery has limited options and allows only official updates. Custom recovery has more options and allows unofficial updates like our prerooted already admin OS/ROM.
Finally fast boot is like your Intel BIOS. Whatever happens as long as it is working you're saved. All other things like recovery, boot, system can be modified from here.
Now you flashed boot.img using fast boot and if you got a success message you're good. Use a recovery image in one of the xolo play threads and flash it using the instructions provided there.
This is required for you to install ROM.
Finally, don't worry about warranty. In case you ever need warranty, follow instructions in my ROM post about warranty. Where you can flash the ROM and recovery that came with the phone. So no worries and good luck.
Edit: for you, since you're so worried, simply install cwm recovery, then install stock odexed ROM, install build.prop.zip then reinstall stock recovery and you're like how u purchased the phone.
Sent from my XOLO Play using Tapatalk 4

i m having this problem .. after typing command it keeps displaying waiting for device .. nothing happens after that .. wat am i doing wrong . ( i tired instaling drivers but it says -windows has determined software is up to date) what shud i do .. cant install ny rom too

mkr17 said:
i m having this problem .. after typing command it keeps displaying waiting for device .. nothing happens after that .. wat am i doing wrong . ( i tired instaling drivers but it says -windows has determined software is up to date) what shud i do .. cant install ny rom too
Click to expand...
Click to collapse
right click the device under device manager and select uninstall. then replug device and browse and select the driver

http://support.moulnisky.com/index.php?dir=Xolo/Xolo Play/
Here factory firmware and instructions
BR
Alex

http://forum.xda-developers.com/showpost.php?p=47122148&postcount=881
Posted the same here
btw, There is an S018 fw out too. Those linked above are outdated.

Free Radical said:
http://forum.xda-developers.com/showpost.php?p=47122148&postcount=881
Posted the same here
btw, There is an S018 fw out too. Those linked above are outdated.
Click to expand...
Click to collapse
Yes,
Already added it in the support area
BR
Alex

mr moulinsky i have karbonn A8 device i flash software but now device is show fizzy and white display with china sound no karbonn logo please help me how to flash karbonn A8 with right flash files
Sent from my Micromax A76 using XDA Premium 4 mobile app

HELP!!
kkbs4u said:
mr moulinsky i have karbonn a8 device i flash software but now device is show fizzy and white display with china sound no karbonn logo please help me how to flash karbonn a8 with right flash files
sent from my micromax a76 using xda premium 4 mobile app
Click to expand...
Click to collapse
my xolo play t1000 is locked due to too many pattern locks. Now it is asking for gmail id & password but my data is off. Now i got struck as my xolo secure is on i cannot wipe data/factory reset the phone. What should i do to unlock also i dont want to loose my warranty.i also cannot visit the service center as it will cost me a flight fare of 6000 bucks. Help me!!!!
Thanks in advance..

morning.revz08 said:
my xolo play t1000 is locked due to too many pattern locks. Now it is asking for gmail id & password but my data is off. Now i got struck as my xolo secure is on i cannot wipe data/factory reset the phone. What should i do to unlock also i dont want to loose my warranty.i also cannot visit the service center as it will cost me a flight fare of 6000 bucks. Help me!!!!
Thanks in advance..
Click to expand...
Click to collapse
try booting into recovery and factory resetting the device...press vol down+power button to boot into recovery and then wipe data/factory reset

How do I root my MT7-L09 B571 on Arch Linux

Hallo there,
at first sorry for the nearly 10th post about this topic, but as you can see I'm in a different position than the most of you. I'm on Arch Linux here and I don't rly want to root my phone with a windows box.
I got adb and fastboot installed, but I can't find a general guide how to flash recovery and root with them, because there are always these click-click-shiny-shiny gui .exes for windows, which take some tasks.
I did root my Droid 3, but this was years ago, and I did never get into this stuff so deep it would help me now. I am a lil exhausted from the day, and don't rly want to puzzle my way through the google search results, which as described above lead to a .exe with a gui at some point.
Anyone here, who knows the basics and is willing to give me a hand here?
As I said I'm a Linux aka a terminal user so you don't need to be soft on this, I just need it compact but complete.
Thanks in advance
p.s. What I think will be relevant at some point, based on the search results so far:
http://forum.xda-developers.com/mat...overy-twrp-2-8-7-0-mate7-android-5-1-t3156779
http://forum.xda-developers.com/showpost.php?p=66546853&postcount=53

Flash recovery image in fastboot (terminal)?
Be need I have an .img of twrp somewhere but should be on forum.
You could also consider using a VM for the .exe.

Mother_Teresa said:
Flash recovery image in fastboot (terminal)?
Be need I have an .img of twrp somewhere but should be on forum.
You could also consider using a VM for the .exe.
Click to expand...
Click to collapse
aka I just follow this guide and change the mobopx part to this:
Code:
fastboot flash recovery twrp_3.0.2_mate7_6.0.img
as stated in the the download entry I linked above?
And there is another question. The part after
NOW LETS GET XPOSED AND LUCKY PATCHER WORKING
Click to expand...
Click to collapse
is not necessary if I use a different launcher than EMUI, or is it?
EDIT: A VM is not an option, would be the same for me than using a physical windows box.

quote: aka I just follow this guide and change the mobopx part to this:
Code:
fastboot flash recovery twrp_3.0.2_mate7_6.0.img
as stated in the the download entry I linked above?
sounds good to me, so now it is twrp and not cwm?
And there is another question. The part after "NOW LETS GET XPOSED AND LUCKY PATCHER WORKING" is not necessary if I use a different launcher than EMUI, or is it?
it allows customizing advanced settings and is implemented in boot. not necessary
EDIT: A VM is not an option, would be the same for me than using a physical windows box.
if you have recovery etc just flash supersu for root

Okay, good was just checking, if it's the way I puzzled it together. Don't want to wipe me phone.
Mother_Teresa said:
sounds good to me, so now it is twrp and not cwm?
if you have recovery etc just flash supersu for root
Click to expand...
Click to collapse
What's the difference between twrp and cwm?
Mother_Teresa said:
it allows customizing advanced settings and is implemented in boot. not necessary
Click to expand...
Click to collapse
Okay, nice.
Mother_Teresa said:
if you have recovery etc just flash supersu for root
Click to expand...
Click to collapse
Just like in the guide i guess. Thx.

This is the tldr:
I have rooted my Mate 7 now like this:
1. got my unlockcode here
2. installed the recovery
Code:
adb reboot bootloader
fastboot oem unlock (insert code)
fastboot flash recovery twrp_3.0.2_mate7_6.0.img
fastboot reboot
3. moved supersu to my sd card
4. booted into recovery (by shutdown and power on with power+volUP+volDOWN pressed)
5. backup system (just for safety)
6. install -> chose supersu.zip
DONE
EDIT: HOW DO I MARK THIS AS SOLVED?

pepper-jk said:
This is the tldr:
I have rooted my Mate 7 now like this:
1. got my unlockcode here
2. installed the recovery
Code:
adb reboot bootloader
fastboot oem unlock (insert code)
fastboot flash recovery twrp_3.0.2_mate7_6.0.img
fastboot reboot
3. moved supersu to my sd card
4. booted into recovery (by shutdown and power on with power+volUP+volDOWN pressed)
5. backup system (just for safety)
6. install -> chose supersu.zip
DONE
EDIT: HOW DO I MARK THIS AS SOLVED?
Click to expand...
Click to collapse
Yay well done and also on posting the solution. I reread what I typed and couldn't make sense to why I mentioned cwm and twrp (same stuff, diff developers or so) so maybe I mixed up bits of another topic

[Solved][PX5 GS] Can not use custom recovery

I would like to flash custom recovery -> in order to use custom ROM -> in order to gain split screen in my 7" device (ehhh)
I have root, adb, access to bootloader (everything what I need..) but it does not work in default way.. - I mean flashing just by fastboot flash recovery TWRP.img
I have checked those TWRP builds
https://twrpbuilder.github.io/downloads/twrp/ (type px5)
Flashing worked fine (no error, success message)
But after rebooting to recovery I still have original recovery. Note: I have to reboot to system, and then to recovery by adb command. There is no reset button on my device, I can only enter bootloader by long pressing volume button while booting.
I saw `backup` partition in my device. Is it possible that system is reverting recovery partition? How to fix that so I can use TWRP

SZAMAN92 said:
I would like to flash custom recovery -> in order to use custom ROM -> in order to gain split screen in my 7" device (ehhh)
I have root, adb, access to bootloader (everything what I need..) but it does not work in default way.. - I mean flashing just by fastboot flash recovery TWRP.img
I have checked those TWRP builds
https://twrpbuilder.github.io/downloads/twrp/ (type px5)
Flashing worked fine (no error, success message)
But after rebooting to recovery I still have original recovery. Note: I have to reboot to system, and then to recovery by adb command. There is no reset button on my device, I can only enter bootloader by long pressing volume button while booting.
I saw `backup` partition in my device. Is it possible that system is reverting recovery partition? How to fix that so I can use TWRP
Click to expand...
Click to collapse
That TWRP don't work in PX5. I'm trying to get it work

Good luck!
Please inform me if you will succeed.

Have you first tried to boot TWRP without flashing? I'd most certianly want to try that before flashing something.
Did that work?
This might sound super silly, but did you also unlock the bootloader first? (Sorry, I'm not familiar with your specific device so this may or may not apply in your situation)

stokedcrf said:
Have you first tried to boot TWRP without flashing? I'd most certianly want to try that before flashing something.
Did that work?
This might sound super silly, but did you also unlock the bootloader first? (Sorry, I'm not familiar with your specific device so this may or may not apply in your situation)
Click to expand...
Click to collapse
Any advice is welcome thanks
But without unlocking bootloader I would not be able to go to bootloader and use fastboot tool right? So I concluded it is already unlocked.
I tried
fastboot boot TWRP.img
Image was downloaded and booted (success message was printed in console), I lost connection with device so it went in some other mode then bootloader, but after 30 seconds of black screen I have switch power off and back on to restart.

SZAMAN92 said:
Any advice is welcome thanks
But without unlocking bootloader I would not be able to go to bootloader and use fastboot tool right? So I concluded it is already unlocked.
I tried
fastboot boot TWRP.img
Image was downloaded and booted (success message was printed in console), I lost connection with device so it went in some other mode then bootloader, but after 30 seconds of black screen I have switch power off and back on to restart.
Click to expand...
Click to collapse
What android version you have ? 8 ?

tuga_z said:
What android version you have ? 8 ?
Click to expand...
Click to collapse
9
Build nr: rk3368-userdebug 9 PQ2A 190305
Kernel v: 4.4.167
MCU: MTCE_GS_V3.07_3
It is that build:
https://yadi.sk/d/umCvHqCDzHccr/RockChip PX5 Android 9/HA/HA_px5_9.0_ota(20190528)升级包.7z
I tried using A8 roms but I can not flash it with original recovery.. It requires device name be PX5 (I have rk3368). If I remove checking from rom updater script, signature verification fails.

I have tried recovery from Malaysk pack (extracted from update.zip), tried RecoveryInstaller from malaysk, lot of TWRP which I have found in web.
Nothing worked.
However as a last chance I used bootable SD from Malaysk - recovery (for android 8) successfully installed, Malyask rom installed. Im happy now
BTW. If you want you system to not revert recovery - you need to remove "/system/recovery-from-boot.p"

SZAMAN92 said:
I have tried recovery from Malaysk pack (extracted from update.zip), tried RecoveryInstaller from malaysk, lot of TWRP which I have found in web.
Nothing worked.
However as a last chance I used bootable SD from Malaysk - recovery (for android 8) successfully installed, Malyask rom installed. Im happy now
BTW. If you want you system to not revert recovery - you need to remove "/system/recovery-from-boot.p"
Click to expand...
Click to collapse
By this you mean that you no longer need TWRP for android 8 ?

tuga_z said:
By this you mean that you no longer need TWRP for android 8 ?
Click to expand...
Click to collapse
I mean I already have Recovery v8. So I was been able to flash custom A8 ROM.
However if you would implement TWRP please message me It is always better.

SZAMAN92 said:
I mean I already have
However if you would implement TWRP please message me It is always better.
Click to expand...
Click to collapse
Except if you ever want to update your unit or MCU, then it's pretty much useless.

marchnz said:
Except if you ever want to update your unit or MCU, then it's pretty much useless.
Click to expand...
Click to collapse
Maybe you are right. But at least it is easier to backup / restore whole device with TWRP.