Related
Hey Everyone,
Im new to android, and having a small issue, I am attempting to root my wifi xoom, I get up to the part where its time to select android recovery so that I can select the root zip, however when I use the volume down key to scroll the options the only 3 available are NVflash, RSD and Fastboot, theres no android recovery option I have searched the forums and googled it, but I seem to be the only one with this issue, my xoom is running 3.1 and bought in Aus, dont know if this makes a difference? any help would be greatly appreciated, I have got an OTG cable and would like to mount my external HDD so I need to get it rooted. Should probably mention I have unlocked it too.
Cheers
ha i just posted a thread with exactly the same issue. Hopefully one of us will get an answer!
djleez82 said:
ha i just posted a thread with exactly the same issue. Hopefully one of us will get an answer!
Click to expand...
Click to collapse
Your post was already answered in the General section. No need to post twice.
The answer did not fix my problem however. Still stuck at the same place as before just like terreboo. Possibly theres an issue with this type of xoom? I bought mine in australia as well. According to my about tablet info it says this:
Firmware Configuration Version: GAS_ASIA_UCAHUBLWFRTIRD_P006 so im assuming this is an asian tab? Just wondering terreboo what does yours say under firmware configuration?
yeah sorry didnt mean to post it in the general section, I alerted it to the mods to delete they just havent got around to it yet, yeah mate I have the same version as you, although I doubt this is the reason, we cant be the only two in Aus trying to root them? I think the problem probably lies else where, it has been suggested I'm getting the timing wrong, so I'll try again and post back my progress or lack of.
---------- Post added at 10:01 PM ---------- Previous post was at 09:45 PM ----------
I have tried it 10+ times now, I'm confident its not the timing of pressing the down key on reboot having varied the length of time everytime I tried, possibly its because of the firmware version? Im at a loss, I have followed the instructions of the root guide to the letter and seem to be one of the only ones with this problem!
this is the guide im using
http://forum.xda-developers.com/showthread.php?t=1078019
Same problem here!
I have the same problem guys.. Any solution?? The developers some help??
Im using the same guide btw....
I've freaked out im trying this for 8 hours now and no results....
im having a similar problem that my factory reset is corrupt or something because it doesnt actually DO anything.
I did the long root method as opposed to the supposedly easier method and thank heavens I got through it unharmed. I was ****ting my pants the whole way through. I wish I were more savvy with this so I can offer help. If I were u guys I would PM the devs from TIAMAT. They are probably the most knowledgeable ppl here to ask.
solution
OK guys i have a solution a guy from #xoom channel told me to write in windows command line
abd recovery reboot
And it worked!
I'm currently posting this from my costum rommed xoom
DrGreem said:
OK guys i have a solution a guy from #xoom channel told me to write in windows command line
abd recovery reboot
And it worked!
I'm currently posting this from my costum rommed xoom
Click to expand...
Click to collapse
Would that be adb recovery reboot? Can you give more information?
assuming you have adb setup on your computer already. Plug your xoom into your comp and make sure its in debug mode. Settings-applications-development. Open a command prompt and type in "adb reboot recovery" without quotes. Your device will then reboot into recovery mode.
I will say I'm having the same issue. I flash the new recovery and I don't see it in the menu. I'm running a US wifi xoom.
okantomi said:
Would that be adb recovery reboot? Can you give more information?
Click to expand...
Click to collapse
Yes that's right. I followed the guide and i waited 3 seconds but i never had the option 'android recovery so i turned on the device and this guy told me to run this command from cmd.
So after that xoom rebooted into clockwork recovery state and i flashed thecostum rom.
According to the guide that were using, if you allow the xoom to boot fully into honeycomb it reinstalls the stock recovery, and you need to redo the process all over. Also, you need to be in honeycomb to use the ADB command, if your in fastboot it won't detect the xoom. This did not work for me. Anyone else try it?
no luck for me here either. I can flash recovery successfully (according to the prompt) no problems there. I just have the exact same trouble booting into it as above.
Vol Down key combo doesn't work and if you leave the OS to boot straight after install, CWM is replaced by stock recovery. No fun at all.
Any further news or suggestions on this?
autodc5 said:
im having a similar problem that my factory reset is corrupt or something because it doesnt actually DO anything.
Click to expand...
Click to collapse
Same as my Xoom, opened a thread just for it, but no one can help
much easier... download rom manager and click boot to recovery haha ...
If not rooted,
adb reboot recovery via a cmdline window works a treat _
fkofilee said:
much easier... download rom manager and click boot to recovery haha ...
If not rooted,
adb reboot recovery via a cmdline window works a treat _
Click to expand...
Click to collapse
Just make sure that Rom Manager doesn't trick you into flashing a non-compatible updated recovery version.
In my experience it doesn't play well with the Xoom.
If all you want is a non manual way to boot into recovery from the OS, download Quick Boot (if rooted) or if you're already on the Tiamat Moray Rom, it's something you can choose when you press the power button on the back.
the problem is that for me and others with this issue, you can't use adb to boot recovery. If you install recovery from fastboot then boot into the regular OS without booting to recovery and rooting, the OS replaces CWM with the stock recovery. This means if you use adb or another app to reboot into recovery, you just get stock recovery which is totally useless. I can't load recovery or root using anay of the universal methods I have come accross. We need a way to boot into recovery without having it replaced with stock or another rooting method or something. Any other ideas?
aussiechris said:
the problem is that for me and others with this issue, you can't use adb to boot recovery. If you install recovery from fastboot then boot into the regular OS without booting to recovery and rooting, the OS replaces CWM with the stock recovery. This means if you use adb or another app to reboot into recovery, you just get stock recovery which is totally useless. I can't load recovery or root using anay of the universal methods I have come accross. We need a way to boot into recovery without having it replaced with stock or another rooting method or something. Any other ideas?
Click to expand...
Click to collapse
Look, this is how I had to flash CWM image file- through adb,/fastboot just like you. No matter what you say, it comes down to a question of timing.
I'm not sure about everyone else with the no recovery option, but timing just isnt the issue for me. Without a lie i've tried to enter recovery over 50 times at various points, 95% of those attempts were at the 3 second mark that is stated in the xda guide we've been using. I'm aware of one other person here whos tried it MUCH more than me with exactly the same result.
However theres one thing that we could narrow it down with. Thus far the people having this issue are using the asian firmware xoom's. Could everyone else having this problem on this thread say whether or not theyre using the asian firmware too? Maybe the asian firmware can't be rooted this way?
Here is a quick Guide to Rooting your Samsung Conquer 4G
1. Download Super One Click Root 2.3.1(below)
2. Extract the rar to any location you choice
3. On your phone click Menu, Settings, Application, Development and check USB Debugging.
4. Open SuperOneClick
5. Plug your phone in to the USB
6. Click Root and watch it do its thing
When it is done it should have installed SuperUsers and you should now be rooted.
At this time there is no Roms or Recoverys so the only thing we benifit from this is some Apps
Links
SuperOneClick 2.3.1
http://www.multiupload.com/VGCN3ZTFM8
Samsung Conquer 4G Drivers
http://www.mediafire.com/?s6nn3rph14xfl41
Hi I'm trying it I get a window says missing driver
Samsung android usb device, acm, CDC acm data
what's that mean?
you are missing the drivers you need to install to get debugging mode to work. What i did was manually install the drivers.
But instead try installing these drivers from the link below. before you install this make sure you unplug your phone first, then install the drivers, then plug your phone back in.
If that works just run SuperOneClick like the guide i posted above
Samsung Conquer 4G Drivers Download Link
http://www.mediafire.com/?s6nn3rph14xfl41
Thank you I'm trying to download the file from the link but it's not work says failed do u have another link thanks again
The link is failed could you provide another one please?
you can try downloading it directly from samsung just click the disk with the txt EXE icon on the right and agree to the terms and the file should download
http://www.samsung.com/us/support/downloads/sprint/SPH-D600ZKASPR
lmk if you have any other issues
Ty but the link is not working also.
in the superoneclick folder there is a drivers folder try to manually install the drivers for your phone using the drivers in that folder if you are still having issues after trying this please PM me there is one more thing we can try.
thanks drayjr
Thank you I did what you qsaid and it worked like a charm thanks again for all your help I really. Appreciate thank you and happy holidays
no I hope you enjoy your new phone. I just hope a Dev makes a recovery for are phone soon. but we will see what happens
thanks
drayjr
Sent from my SPH-D600 using Tapatalk
New to rootin
Think ive been reading for about three weeks now. Ever sinced I learned about this thang called rooting. Yes im a noob to the whole smart phone era, but I catching up. I know my way around the computer but, here I go im going to make tha big leap and givr it a try. I would just like to say thank you dray.jr cause I looked every where for a step by step rooting guide for mu conquer. I had it sincr it came out when I heard that you can even make this phone do more than it already does I was down foe it so......ill let you know how it goes if I need any help.THANKZ AGAIN.
---------- Post added at 11:45 AM ---------- Previous post was at 11:26 AM ----------
Is that all you have to do to root a Samsung Conquer 2.3.4. Is the bootloader unlocked already or...........Let me know cause I'm new to this. I did alot of reading but there's really no kind of info on if theres a lock or not.
Thanks for getting this up. I hope to root my wifes phone but nobody seems to be working on it. Thanks again.
yea i noticed i have uploaded all the files needed to make a custom recovery for are phone but i dont have any idea how to do it so i am hoping a dev see's the post and will give it a shot for us. but if not then im going to have to sell me phone and grab a phone that i can tweak. lol i cant have a phone i cant change and play with.
i have found a so called recovery for this phone just need a place to host it or you can follow this link and check it out you self....
Hello,
This is a flashable recovery image of ClockworkMod Recovery 5.0.2.7 for the SPHD600
go to google and search for sphd600 recovery and you will find this so called one i have tested it and it allows me to enter recovery mode on my Conquer
i have flashed it metro and just awaiting for metro to allow my esn/meid no word as of when this might happen
mike
Hi dray_jr thanks for your help before but now im stuck once again , my phone updated and i have to reroot im doing the same steps as before now it get stuck a step 7 waiting for device. I waited for over 10 mins and nothing please help
dray_jr said:
Here is a quick Guide to Rooting your Samsung Conquer 4G
1. Download Super One Click Root 2.3.1(below)
2. Extract the rar to any location you choice
3. On your phone click Menu, Settings, Application, Development and check USB Debugging.
4. Open SuperOneClick
5. Plug your phone in to the USB
6. Click Root and watch it do its thing
When it is done it should have installed SuperUsers and you should now be rooted.
At this time there is no Roms or Recoverys so the only thing we benifit from this is some Apps
Links
SuperOneClick 2.3.1
http://www.multiupload.com/VGCN3ZTFM8
Samsung Conquer 4G Drivers
http://www.mediafire.com/?s6nn3rph14xfl41
Click to expand...
Click to collapse
The link to the superoneclick app doesnt work. I was able to download it with this link...
http://ul.to/mutl348p
I am stuck in a strange problem. I have LG P500 which i have rooted with superoneclick and it is rooted now. I have 2.3.3 V20d (India) which i upgraded a year back.
Now the problem is that according to everyone mine is a new baseband but when i use Rom Manger to install custom recovery it shows my phone but in brackets it says 'old BB'..There were just two options,one was my phone and the other to click the box down if my device is not shown in the above list. I am stuck as can't find any solution and i am a newbie.I did ask some senior members and contributors/devs and waiting for the help,so i thought i will post it here also in case someone has faced this problem before.
Screen capture attached as well.....Just do not know where to go from here.Thanks a lot
MORE INFO: I just downloaded XDA ASSISTANT app to check and in software section it mentions about baseband also. The reading is: V07u-000-000 (MAR-23-2009). Can't say if it is of any help
kitu34 said:
I am stuck in a strange problem. I have LG P500 which i have rooted with superoneclick and it is rooted now. I have 2.3.3 V20d (India) which i upgraded a year back.
Now the problem is that according to everyone mine is a new baseband but when i use Rom Manger to install custom recovery it shows my phone but in brackets it says 'old BB'..There were just two options,one was my phone and the other to click the box down if my device is not shown in the above list. I am stuck as can't find any solution and i am a newbie.I did ask some senior members and contributors/devs and waiting for the help,so i thought i will post it here also in case someone has faced this problem before.
Screen capture attached as well.....Just do not know where to go from here.Thanks a lot
Click to expand...
Click to collapse
and yes that is your phone lg p500 old bb, it doesn't matter, RomManager doesn't discover your phone, it is just a list that you have to choose
from
Are you sure?
grigtm said:
and yes that is your phone lg p500 old bb, it doesn't matter, RomManager doesn't discover your phone, it is just a list that you have to choose
from
Click to expand...
Click to collapse
Are you sure it doesn't matter? But why would Rom Manager mention that? That means it is misleading the user and the user can think esp a newbie that his is a old baseband therefore he will not go with the new baseband and land in trouble.
More Info In Case It Is Helpful
I just downloaded XDA ASSISTANT app to check and in software section it mentions about baseband also. The reading is: V07u-000-000 (MAR-23-2009). Can't say if it is of any help
My advice: don't use Rom Manager to install a custom recovery (or even a Rom); there have been many reports of people bricking their devices that way. A safer way of installing a recovery would be to use LGMDP or adb/fastboot -- instructions should be in a sticky somewhere; I can't search for it at the moment since I'm on mobile. Anyway, good luck.
Edit: Corrected typo -- it's LGMDP.
____________________
Sent from the moon.
Thanks a lot! So kind of you
Syd_M said:
My advice: don't use Rom Manager to install a custom recovery (or even a Rom); there have been many reports of people bricking their devices that way. A safer way of installing a recovery would be to use LGDMP or adb/fastboot -- instructions should be in a sticky somewhere; I can't search for it at the moment since I'm on mobile. Anyway, good luck.
____________________
Sent from the moon.
Click to expand...
Click to collapse
OMG now i have to start all over again,and being a newbie it is not easy at all.Does rooting etc means spending half the time in the forum?Since yesterday my eyes and back are paining just coz of this hehehee
Ok i will check that brother,thanks a lot seriously.
On what basis you say that?
grigtm said:
and yes that is your phone lg p500 old bb, it doesn't matter, RomManager doesn't discover your phone, it is just a list that you have to choose
from
Click to expand...
Click to collapse
I mean you have encountered that or something yourself or any body else? We have to be sure otherwise the phone will be bricked or ruined and i am not a rich person,therefore god is great hehehe
kitu34 said:
OMG now i have to start all over again,and being a newbie it is not easy at all.Does rooting etc means spending half the time in the forum?Since yesterday my eyes and back are paining just coz of this hehehee
Ok i will check that brother,thanks a lot seriously.
Click to expand...
Click to collapse
Well, I know that I spent a few days reading the sticky threads before I rooted my phone, but even then I managed to softbrick it for a couple of days (though it was sort of my fault, since I was using Linux at the time and all the instructions were for Windows, so I had to improvise). You shouldn't need to read every thread, though -- just the stickies should do.
Anyway, regarding Rom Manager, there's a warning in this thread (post #2) not to use it to install a recovery since the CWM version isn't compatible with our devices. As for a recovery you should use, I strongly recommend AmonRa 3.0.6 for a stable and bugfree recovery.
Edit: Just FYI, I installed my recovery using ADB and fastboot. It was quick and easy, the hardest part was installing the LG drivers and ADB (via installing the Android SDK).
____________________
Sent from the moon.
kitu34 said:
I mean you have encountered that or something yourself or any body else? We have to be sure otherwise the phone will be bricked or ruined and i am not a rich person,therefore god is great hehehe
Click to expand...
Click to collapse
I installed my first time recovery by RomManager on O1 3 years ago, I cannot realy remember how was it but it worked, but first go to settings, apps development(or something, you are on GB) and check ANDROID DEBUGGING, now use this tool from here http://forum.xda-developers.com/showthread.php?t=1827723 all credits to shinobisoft
you can find recovery's here http://forum.xda-developers.com/showthread.php?t=1523050 this are flashable zips
or search Optimus One android develepment and original android development threads
I personaly use CWM 5.0.2.7 but my favourite is TWRP (after I'll change rom I'll go back to TWRP)
---------- Post added at 09:54 PM ---------- Previous post was at 09:35 PM ----------
RomManager doesn't suport anymore old phones like O1, that's why it appears with old bb, anyway, allot of ppl flash first time recovery with RomManager, and because it is first time, there must be some fails, not all made it first time, and RomManager is to blame ?? no, worked for me, worked for milions and for a few thousants didn't, and it depends by allot of things but in most cases the people are to blame
grigtm said:
I installed my first time recovery by RomManager on O1 3 years ago, I cannot realy remember how was it but it worked, but first go to settings, apps development(or something, you are on GB) and check ANDROID DEBUGGING, now use this tool from here http://forum.xda-developers.com/showthread.php?t=1827723 all credits to shinobisoft
you can find recovery's here http://forum.xda-developers.com/showthread.php?t=1523050 this are flashable zips
or search Optimus One android develepment and original android development threads
I personaly use CWM 5.0.2.7 but my favourite is TWRP (after I'll change rom I'll go back to TWRP)
---------- Post added at 09:54 PM ---------- Previous post was at 09:35 PM ----------
RomManager doesn't suport anymore old phones like O1, that's why it appears with old bb, anyway, allot of ppl flash first time recovery with RomManager, and because it is first time, there must be some fails, not all made it first time, and RomManager is to blame ?? no, worked for me, worked for milions and for a few thousants didn't, and it depends by allot of things but in most cases the people are to blame
Click to expand...
Click to collapse
Thanks,but what am i suppose to do with this tool? What about rom manager?Shall i go with it?I am sorry i am a newbie so you can lose patience hehehe
kitu34 said:
Thanks,but what am i suppose to do with this tool? What about rom manager?Shall i go with it?I am sorry i am a newbie so you can lose patience hehehe
Click to expand...
Click to collapse
No, don't use ROM Manager. 3 years ago when @grigtm used it, it was fine. These days, however, the CWM version in ROM Manager is incompatible with our device. You will risk bricking your phone if you use ROM Manager. Personally, I advise against it.
As for the Android Flash Recovery program that was linked earlier, I haven't used it personally, but it seems easy enough to use. Just
1. Download Android Flash Recovery
2. Install the LG drivers (it's packaged with the program in a subfolder called "USB")
3. Enable USB debugging on your phone (Settings > Applications > Development > check USB debugging)
4. Start your phone in Fastboot Mode.
5. Connect your phone to the PC.
6. Start Android Flash Recovery and follow the instructions.
Confused
Syd_M said:
No, don't use ROM Manager. 3 years ago when @grigtm used it, it was fine. These days, however, the CWM version in ROM Manager is incompatible with our device. You will risk bricking your phone if you use ROM Manager. Personally, I advise against it.
As for the Android Flash Recovery program that was linked earlier, I haven't used it personally, but it seems easy enough to use. Just
1. Download Android Flash Recovery
2. Install the LG drivers (it's packaged with the program in a subfolder called "USB")
3. Enable USB debugging on your phone (Settings > Applications > Development > check USB debugging)
4. Start your phone in Fastboot Mode.
5. Connect your phone to the PC.
6. Start Android Flash Recovery and follow the instructions.
Click to expand...
Click to collapse
This is the first step after rooting.Ok
Fastboot mode is Home + Power i just have to do that? Like in rom manager we could do backup of stock can we do all that also with this?
Actually i read at two places how to go step by step,when to backup,going into recovery and wiping & reset the phone then again into recovery and navigate to the zip file of the rom and extract.But i do not know if it is same with Android flash recovery.
New Words For Me...........OMG why i came here hehehe
Syd_M said:
Well, I know that I spent a few days reading the sticky threads before I rooted my phone, but even then I managed to softbrick it for a couple of days (though it was sort of my fault, since I was using Linux at the time and all the instructions were for Windows, so I had to improvise). You shouldn't need to read every thread, though -- just the stickies should do.
Anyway, regarding Rom Manager, there's a warning in this thread (post #2) not to use it to install a recovery since the CWM version isn't compatible with our devices. As for a recovery you should use, I strongly recommend AmonRa 3.0.6 for a stable and bugfree recovery.
Edit: Just FYI, I installed my recovery using ADB and fastboot. It was quick and easy, the hardest part was installing the LG drivers and ADB (via installing the Android SDK).
____________________
Sent from the moon.
Click to expand...
Click to collapse
Dear you mentioned 'FYI', 'ADB' & 'Fastboot'..... i just heard about them once twice but don't know what are they. I am sorry this can be irritating for you and for me as well heheehe.Only lucky people can go through this smoothly otherwise i do not think i will recommend this to anyone at least before 7 years lol. But seriously i am confused
One more important thing
Syd_M said:
No, don't use ROM Manager. 3 years ago when @grigtm used it, it was fine. These days, however, the CWM version in ROM Manager is incompatible with our device. You will risk bricking your phone if you use ROM Manager. Personally, I advise against it.
As for the Android Flash Recovery program that was linked earlier, I haven't used it personally, but it seems easy enough to use. Just
1. Download Android Flash Recovery
2. Install the LG drivers (it's packaged with the program in a subfolder called "USB")
3. Enable USB debugging on your phone (Settings > Applications > Development > check USB debugging)
4. Start your phone in Fastboot Mode.
5. Connect your phone to the PC.
6. Start Android Flash Recovery and follow the instructions.
Click to expand...
Click to collapse
I have LG United Mobile driver already installed,that is enough?
kitu34 said:
Dear you mentioned 'FYI', 'ADB' & 'Fastboot'..... i just heard about them once twice but don't know what are they. I am sorry this can be irritating for you and for me as well heheehe.Only lucky people can go through this smoothly otherwise i do not think i will recommend this to anyone at least before 7 years lol. But seriously i am confused
Click to expand...
Click to collapse
There is absolutely no need to learn all of the language, especially when you're just starting out. It's enough in the beginning to just follow instructions, and only go into the details of the Android environment later as you gain more experience. No one becomes an expert overnight, after all.
As for the terms I used... FYI simply means "for your information", nothing to do with Android at all. ADB is the Android Debug Bridge, and like the name implies, it's like the "bridge" that connects your PC to your phone. Any desktop-based program or tweaking tool that communicates with your phone most likely uses ADB (such as SuperOneClick, which you used previously). Fastboot is one of the debugging modes available on the P500. There's no need to concern yourself with exactly what it does (and explaining it in detail is beyond the scope of this post); you simply need to know how to enter that mode when the instructions call for it. Basically, what I'm saying is that you don't need to understand things in detail, you just need to follow instructions. All the instructions you need are in the stickies; for now, ignore anything else that's not there (it'll only confuse you).
The LG Mobile United driver should work. If it doesn't simply install the other drivers.
Thanks alot for the concern
Syd_M said:
There is absolutely no need to learn all of the language, especially when you're just starting out. It's enough in the beginning to just follow instructions, and only go into the details of the Android environment later as you gain more experience. No one becomes an expert overnight, after all.
As for the terms I used... FYI simply means "for your information", nothing to do with Android at all. ADB is the Android Debug Bridge, and like the name implies, it's like the "bridge" that connects your PC to your phone. Any desktop-based program or tweaking tool that communicates with your phone most likely uses ADB (such as SuperOneClick, which you used previously). Fastboot is one of the debugging modes available on the P500. There's no need to concern yourself with exactly what it does (and explaining it in detail is beyond the scope of this post); you simply need to know how to enter that mode when the instructions call for it. Basically, what I'm saying is that you don't need to understand things in detail, you just need to follow instructions. All the instructions you need are in the stickies; for now, ignore anything else that's not there (it'll only confuse you).
The LG Mobile United driver should work. If it doesn't simply install the other drivers.
Click to expand...
Click to collapse
I really appreciate your concern for the safety of my phone.Thanks a lot.
Actually i was to read and follow the instruction as you told but since yesterday i was having headache coz of this and it was severe this morning and still can't open one eye heheehe Anyway i went with the Rom Manager coz of this even though it showed my phone as old BB.It was flashed in less than a minute.Then i switchd off the phone to enter into recovery by holding down Home Button + Volume Down + Power Button(button to switch off) but phone just reboots normally,no recovery set up. The thread i am following for instructions at XDA's How to's says i should not boot into recovery from thr rom manager and use only the buttons combination. But it is not happening,can you help in this?
Thanks again
kitu34 said:
I really appreciate your concern for the safety of my phone.Thanks a lot.
Actually i was to read and follow the instruction as you told but since yesterday i was having headache coz of this and it was severe this morning and still can't open one eye heheehe Anyway i went with the Rom Manager coz of this even though it showed my phone as old BB.It was flashed in less than a minute.Then i switchd off the phone to enter into recovery by holding down Home Button + Volume Down + Power Button(button to switch off) but phone just reboots normally,no recovery set up. The thread i am following for instructions at XDA's How to's says i should not boot into recovery from thr rom manager and use only the buttons combination. But it is not happening,can you help in this?
Thanks again
Click to expand...
Click to collapse
open RomManager and it should detect if you have or no recovery, it says under flashing recovery, if not use that tool I was directing you to and flash recovery, it is a safe tested tool
---------- Post added at 12:09 PM ---------- Previous post was at 12:08 PM ----------
and do not ever boot into recovery from RomManager, actually after you flashed recovery, uninstall RomManager
---------- Post added at 12:11 PM ---------- Previous post was at 12:09 PM ----------
maybe you did not pushed corectly the buttons, keep pressed home+vol down+power, after LG logo appears release power button
Stuck in fastboot mode
grigtm said:
open RomManager and it should detect if you have or no recovery, it says under flashing recovery, if not use that tool I was directing you to and flash recovery, it is a safe tested tool
---------- Post added at 12:09 PM ---------- Previous post was at 12:08 PM ----------
and do not ever boot into recovery from RomManager, actually after you flashed recovery, uninstall RomManager
Click to expand...
Click to collapse
I pressed the buttons this time after the lg logo and it went in fastboot mode.What to do now?
kitu34 said:
I pressed the buttons this time after the lg logo and it went in fastboot mode.What to do now?
Click to expand...
Click to collapse
power off, boot into rom, and verify if recovery was flashed, if not do it again and not from RomManager
I just followed the instructions at XDA
grigtm said:
open RomManager and it should detect if you have or no recovery, it says under flashing recovery, if not use that tool I was directing you to and flash recovery, it is a safe tested tool
---------- Post added at 12:09 PM ---------- Previous post was at 12:08 PM ----------
and do not ever boot into recovery from RomManager, actually after you flashed recovery, uninstall RomManager
---------- Post added at 12:11 PM ---------- Previous post was at 12:09 PM ----------
maybe you did not pushed corectly the buttons, keep pressed home+vol down+power, after LG logo appears release power button
Click to expand...
Click to collapse
Instructions said to hold these buttons that's it.Now i read somewhere here to do it after LG logo. Fastboot mode started, udc_start()
I just bought the LYF Wind 1 Smartphone and couldn't find a proper way to root it, so I made up my weird way, which works perfectly fine and I'm sharing it with you guys..
Steps :-
Download Wind1Root.zip (mod edit: Please use the blue download button and not the green one.)
Extract it
Enable USB Debugging and connect the phone
Run unlock.bat
Enable USB Debugging again after reset
Run root.bat
UPDATE - Recovery replaced. Touch works now. Using Redmi 2 Recovery.
For any help, watch this video
or read the noob friendly guide at - http://www.ugeeky.com/how-to-root-lyf-wind-1/
i have unlocked bootloader.....and when i execute root.bat my lyf wind 1 shows twrp but in cmd it shows no device error....i have installed fastboot and adb
If anybody know how to replace Kinguser with SuperSU...
I tried installing Supersu-me and Superuser from playstore but none worked.
Supersu doesnt open. It stucks giving a black screen.
Its happening in my LYF wind 4.
If any custom recovery working, please do reply.
This worked well on my Lyf Wind 1 well. Not it is rooted with SU, But when i boot into recovery mode the TWRP has a bug and it shows only a blur screen after swipe to unlock. I need to power of and on again...
Bro can you please provide a root method for LYF flame 1 ? It will help me a lot !!
Need stock ROM and flasher for my Wind 1
What if something goes wrong when trying something new & attractive but UNSAFE?
If it's not available, then how to backup whole stock OS present in the phone right now?
Namashkaar ,
Thanks Harkunwar for sharing with us your brilliant work.
Can you be kind enough to confirm that
Build number and Base Band LYF_LS-5010_01_05_15
Kernel ver 3.10.49-perf [email protected] #1 sun may 15 00:51:15 cst 206
Android security patch 2016-05-01
is fit and qualifies for your script cause it seems that nothing happens on my device, can you plz help me in identifying in what I might be doing wrong ?
ibm_chandan said:
Namashkaar ,
Thanks Harkunwar for sharing with us your brilliant work.
Can you be kind enough to confirm that
Build number and Base Band LYF_LS-5010_01_05_15
Kernel ver 3.10.49-perf [email protected] #1 sun may 15 00:51:15 cst 206
Android security patch 2016-05-01
is fit and qualifies for your script cause it seems that nothing happens on my device, can you plz help me in identifying in what I might be doing wrong ?
Click to expand...
Click to collapse
That thing is working on that build number, I can personally confirm that, and as far as I know, it doesn't depend on that either. Check that fastboot is working properly
---------- Post added at 08:09 PM ---------- Previous post was at 08:06 PM ----------
Harkunwar said:
I just bought the LYF Wind 1 Smartphone and couldn't find a proper way to root it, so I made up my weird way, which works perfectly fine and I'm sharing it with you guys..
Steps :-
Download Wind1Root.zip
Extract it
Enable USB Debugging and connect the phone
Run unlock.bat
Enable USB Debugging again after reset
Run root.bat
For any help, watch this video
or read the noob friendly guide at - http://www.ugeeky.com/how-to-root-lyf-wind-1/
Click to expand...
Click to collapse
Which phone's recovery did you use? I want to port the rom for wind 1
@ Akash : Thanks for your input. Would you kind enough to post a link to fastboot , as ugeeky hosting sever is down. and I dont think the fastboot that I have is working properly. My Laptop is running Windows 10 Insider Preview 10.0.14393 64 bit . I hope it is not a problem .
Thanks again.
this is not working when i start root.bat it stucks up with a blur black screen and nothing happens I had to power off the device and power it back on. but the root did not happen, pls inform me what is the problem.
LeHarkunwar, A Big Thank You for coming up with the Root !! Have got rid of a lot of crap ware and unwanted stuff.
However, the points raised by "Java Baba" and "davinashgandi" deserve some attention. There has to be a tutorial/instructions for flashing stock firmware and stock recovery in the event that things go a little awry. A link to stock firmware and stock recovery with instructions for flashing the same is necessary and would decorate this wonderful work of yours.
Secondly, the twrp recovery is not at all functional when booted into. In such a case, applying incremental updates ( This Morning there is a new 37 MB update available) can soft brick the device.
The Wind 1 community will really appreciate if you can do something about this.
Again, Many Thanks for your superb work !!!
ibm_chandan said:
@ Akash : Thanks for your input. Would you kind enough to post a link to fastboot , as ugeeky hosting sever is down. and I dont think the fastboot that I have is working properly. My Laptop is running Windows 10 Insider Preview 10.0.14393 64 bit . I hope it is not a problem .
Thanks again.
Click to expand...
Click to collapse
you can visit this thread for downloading fastboot and adb drivers:
http://forum.xda-developers.com/showthread.php?p=48915118#post48915118
---------- Post added at 03:02 PM ---------- Previous post was at 02:56 PM ----------
siddharth14 said:
LeHarkunwar, A Big Thank You for coming up with the Root !! Have got rid of a lot of crap ware and unwanted stuff.
However, the points raised by "Java Baba" and "davinashgandi" deserve some attention. There has to be a tutorial/instructions for flashing stock firmware and stock recovery in the event that things go a little awry. A link to stock firmware and stock recovery with instructions for flashing the same is necessary and would decorate this wonderful work of yours.
Secondly, the twrp recovery is not at all functional when booted into. In such a case, applying incremental updates ( This Morning there is a new 37 MB update available) can soft brick the device.
The Wind 1 community will really appreciate if you can do something about this.
Again, Many Thanks for your superb work !!!
Click to expand...
Click to collapse
Stock firmware is not modified by this method, and there's no way to backup the stock recovery until we get the factory firmware, for installing any zips to the system, you can always replace the update.zip with the file you want to flash( remember to rename the file you want to flash as update.zip) in the files folder and then run the root.bat file.
Thanks Aakash. Yes, I'm aware that this method doesn't modify stock firmware. The suggestion was made so that people with soft bricked device would be able to revert to stock firmware if anything went wrong.
As for recovery, I managed to download the stock firmware and extracted the stock recovery. I also successfully flashed the stock recovery over twrp. However, the 37 Mb update was aborted due to some mismatch. No idea how to get around this with stock recovery. Yes, it's possible over twrp like you said but I would prefer to apply it through stock recovery.
If only we had a functional custom recovery, things would be even better.
On a side note, has anybody been able to figure the rebranded model and company of Wind 1 ?
---------- Post added at 01:28 PM ---------- Previous post was at 01:15 PM ----------
Ok. I have tried flashing the downloaded update.zip via stock recovery and twrp but no success. I guess the only option left now is via sideload method. And if i'm not wrong then i would lose root if i installed it via adb sideload.
Slightly off topic, the voice Volume of Wind 1 appears low and somewhat muffled. It's not clear and loud like its in my MOTO G. Can fellow users please confirm this. I have also tried the *#4636#* code which opens the testing menu but it's of no use. Need some application or code to access the engineering menu via which we could increase the voice volume.
Hey bro,i am same version of Android on my Lyf wind 1,n I'm glad to have a solution that you came with, I want to upgrade my mobile to marshmallow(stock version), can you please instruct me how can I do that, I'll waiting 4 ur response, thank you
I humble request to help me in rooting lyf flame 2/!,
,plz plz just begging
Sent from my LS-4004 using Tapatalk
I m using windows 10 ...and when I try to open unload.bat file my Lyf wind 1 is rebooting and show android icon and stuck at there.... And cmd show's that waiting for device .....I have to open the bettry and re connect it for start my Lyf wind 1 and ... nothing happens
please can someone give me flashing tutorial for lyf wind 1 , my set is dead , its not powering on now ,
@harshad
Please ensure that you have properly installed drivers for LYF Wind 1. To check this, enable USB-Debugging and connect your LYF Wind 1 to PC. You will also get a message on your phone regarding granting authorization to your computer. Click on Yes. If you don't click on yes then you are bound to get the device not found or device offline errors !
While flashing, i got the device not found error a couple of times and i noticed that i hadn't granted authorization to my computer for USB debugging. The authorization window had popped on my mobile and i was too busy looking at my computer screen.
Now, open Device manager on your computer. Click on Scan for Hardware changes. If the drivers are not installed properly then you will see Yellow exclamation marks against your Android phone. Please install the USB drivers for LYF Wind 1. ( Google if you don't have the drivers)
You need to have;
1) ADB and Fastboot installed as Administrator
2) USB drivers for LYF Wind 1 installed
3) Allow OEM Unlocking , enabled via developer options.
4) Enable USB debugging , enabled via developer options.
If all the above things are in order then you shouldn't have any problems rooting LYF Wind 1 with Le Harkunwar's excellent tutorial.
---------- Post added at 04:19 PM ---------- Previous post was at 04:13 PM ----------
Amit2310 said:
please can someone give me flashing tutorial for lyf wind 1 , my set is dead , its not powering on now ,
Click to expand...
Click to collapse
Try a battery pull. Take out the battery and wait for 5-10 seconds. Insert the battery and now try powering up the device.
found this for stock rom installation incase something goes wrong http://giveawaytricks.in/install-stock-rom-on-lyf-wind-1-lyf-ls-5010/
Amit2310 said:
please can someone give me flashing tutorial for lyf wind 1 , my set is dead , its not powering on now ,
Click to expand...
Click to collapse
you need to download stock rom and flash that to make your phone work again. I found this site, zeon22 has also listed a site, but i found this to be more user friendly in downloading files.
http://repairmymobile.in/flash/lyf-wind-1-ls-5010-stock-rom/
---------- Post added at 04:36 AM ---------- Previous post was at 04:26 AM ----------
siddharth14 said:
Thanks Aakash. Yes, I'm aware that this method doesn't modify stock firmware. The suggestion was made so that people with soft bricked device would be able to revert to stock firmware if anything went wrong.
As for recovery, I managed to download the stock firmware and extracted the stock recovery. I also successfully flashed the stock recovery over twrp. However, the 37 Mb update was aborted due to some mismatch. No idea how to get around this with stock recovery. Yes, it's possible over twrp like you said but I would prefer to apply it through stock recovery.
If only we had a functional custom recovery, things would be even better.
On a side note, has anybody been able to figure the rebranded model and company of Wind 1 ?
---------- Post added at 01:28 PM ---------- Previous post was at 01:15 PM ----------
Ok. I have tried flashing the downloaded update.zip via stock recovery and twrp but no success. I guess the only option left now is via sideload method. And if i'm not wrong then i would lose root if i installed it via adb sideload.
Slightly off topic, the voice Volume of Wind 1 appears low and somewhat muffled. It's not clear and loud like its in my MOTO G. Can fellow users please confirm this. I have also tried the *#4636#* code which opens the testing menu but it's of no use. Need some application or code to access the engineering menu via which we could increase the voice volume.
Click to expand...
Click to collapse
I also received the update but I'm not interested in updating since my phone is running fine just now, I don't want to loose root or brick my phone while updating which will most probably be more bloatware(few more apps from reliance jio). I will wait if marshmallow arrives for flashing stock rom if it arrives (although chances are pretty slim). Meanwhile I'm working on a port of cyanogenmod for this device form Yu Yunique, the device from which harkunwar got this twrp from, but I'm still not able to resolve touchscreen driver issue. Info on this device is really limited, and i don't know anything except that this device is from zte.
Hello team. I need to edit build.prop file on my J3 but I cannot root.
My understanding is that this is possible using custom recovery, just mount the system partition and push and pull the file file with adb. The problem is my handset (SM-J330FN) is running Android 8, and I think only custom recovery exists for Android 7. I tried installing the TWRP I found for Android 7, but the phone just boot loops, get stuck at Samsung logo and reboot. Don't think I can use this Android 7 TWRP with Android 8.
So next plan, I tried to wipe and install Android 7 firmware instead, but Odin said no. I take UK BTU firmware from updato.com the same way I do with Android 8 but it gets to the first stage and Odin says FAIL!
Can anyone provide a suggestion for how I can edit build.prop without root? I don't care how - maybe I can find a custom recovery for Android 8, maybe someone can help with why I can't install the Android 7 firmware, maybe someone knows of a way I can do a 1 time boot to recovery image (have used "fastboot reboot recovery.img" in the past but am aware that Samsung bootloader does not support fastboot). Maybe I can do it with root and remove the root after? Root needs to be not detected so I can use certain tools.
Any advice hugely appreciated
marshedpotato said:
Hello team. I need to edit build.prop file on my J3 but I cannot root.
My understanding is that this is possible using custom recovery, just mount the system partition and push and pull the file file with adb. The problem is my handset (SM-J330FN) is running Android 8, and I think only custom recovery exists for Android 7. I tried installing the TWRP I found for Android 7, but the phone just boot loops, get stuck at Samsung logo and reboot. Don't think I can use this Android 7 TWRP with Android 8.
So next plan, I tried to wipe and install Android 7 firmware instead, but Odin said no. I take UK BTU firmware from updato.com the same way I do with Android 8 but it gets to the first stage and Odin says FAIL!
Can anyone provide a suggestion for how I can edit build.prop without root? I don't care how - maybe I can find a custom recovery for Android 8, maybe someone can help with why I can't install the Android 7 firmware, maybe someone knows of a way I can do a 1 time boot to recovery image (have used "fastboot reboot recovery.img" in the past but am aware that Samsung bootloader does not support fastboot). Maybe I can do it with root and remove the root after? Root needs to be not detected so I can use certain tools.
Any advice hugely appreciated
Click to expand...
Click to collapse
You obviously ignored my reply I gave you yesterday.
As I already stated TWRP fully supports your device on Oreo.
Your issue is not reading the thread properly.
All you need to do is explained in the TWRP OP.
https://forum.xda-developers.com/ga...overy-twrp-3-1-1-1-samsung-galaxy-j3-t3709056
ashyx said:
You obviously ignored my reply I gave you yesterday.
As I already stated TWRP fully supports your device on Oreo.
Your issue is not reading the thread properly.
All you need to do is explained in the TWRP OP.
https://forum.xda-developers.com/ga...overy-twrp-3-1-1-1-samsung-galaxy-j3-t3709056
Click to expand...
Click to collapse
Hello, if you look at the times you will see that i made this post before I commented on yours!
I did not ignore your message, I just had not seen it yet.
As it turns out, you were right - I just tried again, taking extra care to follow instructions exactly and this time it works.
Leaves me with mixed feelings, because I am really grateful for the great development work you have done to help people like me, but also the way you are speaking to me above was a bit rude and I do not deserve that just for a small mistake. I was polite.
Thank you regardless.
marshedpotato said:
Hello, if you look at the times you will see that i made this post before I commented on yours!
I did not ignore your message, I just had not seen it yet.
As it turns out, you were right - I just tried again, taking extra care to follow instructions exactly and this time it works.
Leaves me with mixed feelings, because I am really grateful for the great development work you have done to help people like me, but also the way you are speaking to me above was a bit rude and I do not deserve that just for a small mistake. I was polite.
Thank you regardless.
Click to expand...
Click to collapse
There's a difference between being rude and being direct.
I am the latter.
Nothing personal was included in my reply nor was it intended to be.
You're upset, but I also get upset when people cannot seem to take the time to read the descriptive instructions I've included in my posts.
Trust me, it takes far longer for me to create this stuff than for yourself or anyone else to read and apply the instructions.
Don't be offended it's just frustration from my end manifesting itself in my posts.