Related
Chapter 1: The Foolishness of the User
Hi, I have the korean version of the optimus one(KU3700). It was on gingerbread(2.3.4) stock. I was trying to root it by downgrading it. I entered "adb reboot recovery" and I'm stuck. I tried to reflash it by going to emergency mode with the button combinations using the KDZ updater with this
"csmg. lgmobile. com:9002/swdata/WEBSW/LGKU3700/AKTFBK/KU370040_00/KU370040_00.kdz"
and it worked without any errors but when it when it came up it was still on recovery mode. Is there any way I can change the phone mode to the regular mode
Chapter 2: Journey to Salvation
For anyone who has this korean optimus one, after days of searching, I've found a web site that gave me hints to solve the problem. I just needed a different kdz file and I got it here:
h t t p://sirospace.tistory.com/category/Android%E2%97%86
popped it in google translate because I'm Filipino and can't read korean.
Downloaded the froyo kdz and flashed. I hope this can help other people stupid enough to play with their phones by typing random commands without knowing what it does, like me, LOL...so happy, now it's time to root
Chapter 3: False Hope
OK so I have successfully unbricked and rooted my KU3700, now The problem I have is installing a custom recovery on this phone, none of the images I try work.
Recovery images I have tried are as follows:
recovery-RA-GNM-thunderg-1.1.0.img
recovery-RA-GNM-thunderg-2.2.1.img
recovery-RA-GNM-thunderg-3.0.6.img
Every time it finishes and reboots, it gets stuck at the LG logo.
Chapter 4: Wisdom Within
Found the problem. The images above are for the P500.Even if the KU3700 hardware is similar to the P500, flashing firmwares made for the other model will result in errors. The same holds true for custom recoveries.
Chapter 5: The Plea to the Gods
I've contacted drellisdee and submitted the files needed for custom recovery creation for the KU3700.
Just waiting for the flash image now. Thank you everyone
Chapter 6: The Forgotten
It seems drellisdee is busy right now. I'm a windows user and knows nothing about programing. So if anybody can help I'm sure the KU3700 community would be greatful. I've attached the files I think are needed to make a custom recovery.
Chapter 7: Quest for the Custom Recovery
I got tired of waiting. So as a windows user with no experience in programming, I did a lot of copying and pasting, I managed to port clockwork mod using virtualbox following this website:
h t t p://www.koushikdutta.com/2010/10/porting-clockwork-recovery-to-new.html
So I have got a bootable and flashable custom recovery but nothing works yet. I still need to configure it according to the device.
I have uploaded the image and the build files. Please help me configure it and tell me what's wrong. I really don't know that I'm doing
PS: you can try flashing the custom recovery by doing "fastboot flash recovery /Path to/recovery.img and you can go to recovery by using android terminal and type "boot recovery". It will boot, but that's that LOL. Take out the battery to boot to normal mode.
Chapter 8: The Holy Grail
LOL, I found the answer again. I was so frustrated that I kept squishing the phone in recovery and found out that it was just a button configuration problem. A bit of research and I found out that I can toggle it by pressing volume up and volume down at the same time. WOOHOO!!! Custom Recovery at last
Chapter 9: Invasion of the ROMS
And here at last, the user is retired. But the adventure is far from over. It is foretold that the creation of the Custom Recovery will begin a new era. The key to open the gate has been found. So our hero will await the invasion of the ROMS<background music...> END
you can see at
tinhte.vn/threads/908874
Thank you for the reply but as I said, I can flash fine without errors it's getting back to regular mode I have a problem with. Rebooting and reflashing does not take me out of the recovery screen(it's just a opened box with an orange arrow and the android logo).
vidgen13 said:
Thank you for the reply but as I said, I can flash fine without errors it's getting back to regular mode I have a problem with. Rebooting and reflashing does not take me out of the recovery screen(it's just a opened box with an orange arrow and the android logo).
Click to expand...
Click to collapse
yes i see.but i'm newer android.i only send you link to fix
i hope have a pro android to fix your brick
This is just a shot in the dark because i didn't understand what you did entirely : have you used the combination to actually recover the stock rom after you flashed with KDZ ? (Home+VolDown+Power)
Yes already did. The computer can see the phone whenever I connect it except that I can't access adb. I may have to take this back to the store
vidgen13 said:
Yes already did. The computer can see the phone whenever I connect it except that I can't access adb. I may have to take this back to the store
Click to expand...
Click to collapse
Are you sure you flashed the right rom for your phone? There's an application that downloads the required rom for your phone according to your IMEI/SN, but i don't know if it works with the korean version.
Yes it's the KDZ file, unfortunately it's the only KDZ file out there for ku3700. Shouldn't have settled for this korean version
why you wanna downgrade the latest version?
Dude I have the same Korean edition as you.
Actually why you wanna downgrade the latest version.?
My phone had 2.2.2 and I did upgrade it into 2.3.4 I did it officially and I can tell you How to re-install 2.3.4 if you want.
asmOne said:
Dude I have the same Korean edition as you.
Actually why you wanna downgrade the latest version.?
My phone had 2.2.2 and I did upgrade it into 2.3.4 I did it officially and I can tell you How to re-install 2.3.4 if you want.
Click to expand...
Click to collapse
Thanks for the reply. I wanted to downgrade it to root it. And now I'm rooted. My only problem now is installing a custom recovery. I've already tried several custom recoveries:
recovery-RA-GNM-thunderg-1.1.0.img
recovery-RA-GNM-thunderg-2.2.1.img
recovery-RA-GNM-thunderg-3.0.6.img
but I get stuck at the LG logo when it reboots. I think it's because it's for the p500. So if you have a custom recovery for the ku3700 please help
I dont get it ,p504,p505,p506 are versions of p500??? And why some of our roms work on those phones?? So by logic this stock work on p500???
Sent from my LG-P500 using XDA Premium App
vidgen13 said:
Thanks for the reply. I wanted to downgrade it to root it. And now I'm rooted. My only problem now is installing a custom recovery. I've already tried several custom recoveries:
recovery-RA-GNM-thunderg-1.1.0.img
recovery-RA-GNM-thunderg-2.2.1.img
recovery-RA-GNM-thunderg-3.0.6.img
but I get stuck at the LG logo when it reboots. I think it's because it's for the p500. So if you have a custom recovery for the ku3700 please help
Click to expand...
Click to collapse
this method worked for my working KU3700 when I'm using my 1st KU3700 I also was struck as you and finely I realized there are No custom roms for Optimus one Korean edition (KU3700/SU370) and I had to connect my phone to an Octopus box (lg softwere box) via software box installed the official firmware. if this method not working you have to connect to a software box.
connect to the internet your PC and 1st install Driver and 2nd install the LG update tool. after installation connect your phone to computer and wait a five seconds for comport installation. after install your phone Run LG Update application.
it is connect to the server automatically indicating red line and after search for latest firmware.
if you can Update your phone it is shows Update butten.
Driver
http://www.4shared.com/file/C3BSNx9P/lgunitedmobiledriver_s4981man3.html
LG Update Tool
http://www.softpedia.com/get/Mobile-Phone-Tools/Others/LGMobile-Support-Tool.shtml
Thank you all for the quick answers, but I already have a rooted ku3700. All I need now is a working custom recovery. If someone has the same phone, please tell me which image is compatible
you can appear the emergency mood with android logo.
it means you have an Empty phone. your Os was been erased. You have to connect your phone to Octopus software box and box server has you original Os for your IMEI. this is the only solution. if you will able to solve this problem without a Software box please inform me. we can open a New Thread for Korean edition.
(ku3700/su370)
I already got out of the emergency mode without an octobus box. It's really simple, you just need to use a different kdz file. The hard part was looking for the kdz file. I have 3 kdz files. KU370017(froyo), KU370033(gingerbread-rootable), KU370040(latest one from LG, gingerbread-unable to root). Just flash with the KDZ updater. I'm on the second firmware because I can't root the latest firmware. To root it, I used super one click(latest version, use zerg rush option). Now I'm just waiting for a custom recovery from drellisdee so I can use custom roms. When I get it, I'll ask him if I can post it so we all can have uber phones LOL
Updated the thread. Can somebody help?
vidgen13 said:
Updated the thread. Can somebody help?
Click to expand...
Click to collapse
If you have flashed a working clockworkmod you can enter into clockworkmod via ROMManager (search in google play aka market). In ROMManager you have "reboot to recovery" option in case you want to go to recovery to flash something. Also you can try to flash from ROMManager a custom recovery (5.0.2.0 for oldBB or 5.0.2.7 for newBB), try to choose to phone model LGP500 oldBB, try and test if it's working. Wish you luck.
Thanks but I already have a working recovery. I just need some ROM makers now
vidgen13 said:
Thanks but I already have a working recovery. I just need some ROM makers now
Click to expand...
Click to collapse
Have you tried CM7.2? if your phone is very similar with Optimus One i doubt it isn't compatible with your phone.
If your phone use 2.6.35.10 or 2.6.35.14 kernel you can give a shot to try CM7.2 on your phone, but before try this make a backup first.
Check this thread Post Your CyanogenMod 7.2.0-RC1 Nightly Questions HERE!! for CM7 custom rom.
yep, it doesn't work. Is there a tutorial for building cyanogen for unsupported devices? All I can find are tutorials for supported devices. I've already got the source code from LG. The problem is just incorporating it in the cyanogen mod. I wish this phone had more users LOL
So guys, I'm new to this and thought I would jump in at the deep end.
I unlocked my HTC One X+ easily and set about rooting.
I've got TWRP installed but it keeps telling me it needs to install superuser before it can root.
I have totally wiped the phone, how come if Im not rooted?
How do I get an OS and indeed the kernel or ROM onto the phone?
Its and International OX+, I've got the right kernel... what do I need to do?
It was locked to O2 if that makes a difference
I followed the instruction in Hasson but then wiped the OS
I know its a simple procedure but can someone walk me through it please
So I've downloaded Kernel 3.1.10-ge7581e4
I have no idea what to do next, come on guys I know its not difficult for you guys.
eskimosound said:
So I've downloaded Kernel 3.1.10-ge7581e4
I have no idea what to do next, come on guys I know its not difficult for you guys.
Click to expand...
Click to collapse
If you wiped as you said, you need to push with adb a rom of your choice to the internal memory of the phone and then install it within twrp.
Please read instructions 2 or 3 times before attempting anything, seems like you rushed and now you're temporarily without phone till you flash a rom on it again. I doubt any root guide tells you to wipe the phone, your own fault on this.
To sum it up:
Put a rom's zip of your choice in the internal memory with adb push
flash the rom within the twrp recovery (install option)
flash the kernel for the specific rom with fastboot (each rom has a guide and download for it)
You can now search about it more easily, plenty of posts and info about this.
dan_alexandre said:
If you wiped as you said, you need to push with adb a rom of your choice to the internal memory of the phone and then install it within twrp.
Please read instructions 2 or 3 times before attempting anything, seems like you rushed and now you're temporarily without phone till you flash a rom on it again. I doubt any root guide tells you to wipe the phone, your own fault on this.
To sum it up:
Put a rom's zip of your choice in the internal memory with adb push
flash the rom within the twrp recovery (install option)
flash the kernel for the specific rom with fastboot (each rom has a guide and download for it)
You can now search about it more easily, plenty of posts and info about this.
Click to expand...
Click to collapse
Thanks, I did indeed rush into it but I have been meaning to do it for a year and just thought go for it, I know its all salvageable..ish!
So yep, I've got the ROM I want but don't understand the kernel, I see no guide to download it, all I know is I took a note of the Kernel before I wiped my phone and I have managed to find the exact kernel.
The ROM or RUU as it is, is an O2 UK version, I figure it must be the one I want as it was an O2 phone in the UK.
I still don't know what folders to put things in, TWRP can't see a boot.img that I have on the phone when installing, it can only see it through file explorer.
And then, every time I power down the phone TWRP asks to install Superuser, its cant, theres nothing to install it to, so it just keeps asking.
This is all because I hated the Sense 5 update, indeed Im till looking for the Sense 4 ROM fo HOX+
eskimosound said:
Thanks, I did indeed rush into it but I have been meaning to do it for a year and just thought go for it, I know its all salvageable..ish!
So yep, I've got the ROM I want but don't understand the kernel, I see no guide to download it, all I know is I took a note of the Kernel before I wiped my phone and I have managed to find the exact kernel.
The ROM or RUU as it is, is an O2 UK version, I figure it must be the one I want as it was an O2 phone in the UK.
I still don't know what folders to put things in, TWRP can't see a boot.img that I have on the phone when installing, it can only see it through file explorer.
And then, every time I power down the phone TWRP asks to install Superuser, its cant, theres nothing to install it to, so it just keeps asking.
This is all because I hated the Sense 5 update, indeed Im till looking for the Sense 4 ROM fo HOX+
Click to expand...
Click to collapse
Sigh, if you had read carefully you'd know that boot.img need to be flashed through fastboot and not from recovery. Every rom has this info or a batch file for this.
So what exactly are you trying to do? Root the stock rom that came originally with the phone or installing a custom rom?
dan_alexandre said:
Sigh, if you had read carefully you'd know that boot.img need to be flashed through fastboot and not from recovery. Every rom has this info or a batch file for this.
So what exactly are you trying to do? Root the stock rom that came originally with the phone or installing a custom rom?
Click to expand...
Click to collapse
Lols, thanks dan, I hope you don't hate me!
Root the stock ROM
For starters..
The boot.img is the Android Revolution HD
The RUU is O2 UK
I do realise they are two different ways of installing an OS, I would just like one of them to work!
So think install RUU, then kernel
But put them where and how
I bought the Android Hackers book, but theres nothing about HOX+ in it, and seeing as that's the only phone, I've got to practise on I thought I would ask you specifically.
eskimosound said:
Lols, thanks dan, I hope you don't hate me!
Root the stock ROM
For starters..
The boot.img is the Android Revolution HD
The RUU is O2 UK
I do realise they are two different ways of installing an OS, I would just like one of them to work!
So think install RUU, then kernel
But put them where and how
I bought the Android Hackers book, but theres nothing about HOX+ in it, and seeing as that's the only phone, I've got to practise on I thought I would ask you specifically.
Click to expand...
Click to collapse
I see, the easiest ways would be to use a custom rom now. For example, the one you already got the kernel from(android revolution hd)
To root you dont need to install a kernel... just to flash the supersu zip. Using a custom rom's kernel with stock rom might not be a good idea.
Another simple way would be to restore stock rom back to start and try rooting again, this time reading everything carefully
So the two easiest ways i think:
1) flash a custom rom following the instructions they provide in the initial posts for that rom
2) run the o2 correspondent RUU to restore stock rom (you'd need to relock the bootloader), also reading carefully posts in the forum about restoring to stock
Without getting into too much detail, these are the simplest options.
All the info required to do these are on these forums
Aaarrghhh, its driving me insane as I knew it would, just like XP, Vista Seven and Eight!!!
So Im back to being up all night learning..
Well have installed SDK correctly but device is not seen, no serial, nothing.
I can get it to fastboot though, however I don't know any commands so I cant get it to work
Windows 7 keeps moaning about an mpt file which I downloaded and dont know where to extract it to
All I need to do is copy a few files to the phones sd card and install them right?
Whys that so difficult?
I don't know the difference between a rom an ruu and a boot image, in that I don't know where they should all be placed.
Why cant twrp copy and paste from pc...
So Hassooon works sort of but still none the wiser.
Am following tutorial but fastboot commands are not working
Still cant find right driver.....
So CMD lines not working 100%
So am downloading drivers in sdk manager
And how do I flash the supersu zip?
Still no luck with driver, im on windows 7 32bit
OK I cant push using adb it cant find the file or directory,
Hassooon cant detect the phone as cant windroid universal
I dont think the phone is rooted even though i have twrp on it.
Thus can I have wiped the os?
If not can i restore it?
No I didnt make a backup rom..
mmm a zip on the phone doesnt load in bootloader, count that be my os?
Guys, im stranded in the water here...
On boot im getting...
Failed to open usb master mode
[Preload] Failed to open usb master mode
loading PM35IMG.zip image...
Failed to open usb master mode
please plug off usb
Whats PM35IMG.zip?
Is that the OS?
Am I saved?
Is it easy to get that file to unzip and load?
Can anyone help?
So now I need the right RUU.....
2.17.206.3
Is there anyone out there that can help please?
So have managed to install superuser and root my phone, all instructions for doing this were wrong including Hassoon, had to have the phone in System screen to do it, not bootloader or recovery.
Now cant get adb to push file to sdcard...
Man alive, how to make something very easy, sound very difficult.
Would any of you experts care to help?
Just trying to install a ROM.zip to Root and place the boot img in right place.
Well, the instructions are dire but after 10 days of persistance have installed Android Revolution HD 8, finally my phone is up and running better than the bloated os that came with the phone so, you can call this thread resolved.
Hi guys,
I was wondering if anyone would be kind enough to point me to a link for a Hisense U980 Stock Recovery and scatter file. Mine has unfortunately become corrupted and i currently have the MLS recovery (Chinese) version on my device. I've basically followed the guide I've found on XDA forums to root and install the custom ROM but i'm having the following issues:
After flashing the custom, my SIM management option is greyed out under settings. Therefore, it's not detecting either of the SIM card's installed (dual SIM phone).
Running the new MIUI OS, my devices soft keys (Home, Back buttons etc.) are no longer functional making it difficult to navigate menu options.
I've tried following the tutorial to create a stock recovery but MTK Droid Tools is not detecting my device.
I've downloaded the stock ROM from needrom but am unable to flash it with the current recovery.
My feeling is, if i can revert to the stock recovery, i'll be able to flash the stock ROM.
I've posted some images as well.
Any help will greatly appreciated.
Thanks,
Graham
This worked for me
graham_1 said:
Hi guys,
I was wondering if anyone would be kind enough to point me to a link for a Hisense U980 Stock Recovery and scatter file. Mine has unfortunately become corrupted and i currently have the MLS recovery (Chinese) version on my device. I've basically followed the guide I've found on XDA forums to root and install the custom ROM but i'm having the following issues:
After flashing the custom, my SIM management option is greyed out under settings. Therefore, it's not detecting either of the SIM card's installed (dual SIM phone).
Running the new MIUI OS, my devices soft keys (Home, Back buttons etc.) are no longer functional making it difficult to navigate menu options.
I've tried following the tutorial to create a stock recovery but MTK Droid Tools is not detecting my device.
I've downloaded the stock ROM from needrom but am unable to flash it with the current recovery.
My feeling is, if i can revert to the stock recovery, i'll be able to flash the stock ROM.
I've posted some images as well.
Any help will greatly appreciated.
Thanks,
Graham
Click to expand...
Click to collapse
Phone must be rooted (IRoot works)
1. Install any root explorer or browser and then check if root permissions are enabled (Security App>Permission>Root Permission).
2. Modifying Build.prop
2.1 Open root browser/explorer and navigate to system folder.
2.2 Open build.prop with the text editor (root browser comes with it)
2.3 Add this line on last line of the text then save. Select allow to all permission prompts.
qemu.hw.mainkeys=0
If the keyboard is missing download a keyboard APK like swiftkey and install it the through the file explorer.
Hi guys...
I have a question and a suggestion
For the stock ROM I found where I can download it its covered in the official forum for the hisense but its in Chinese I think I can't post the links.. Also I used the frameroit apk to root my phone its simple... My question is ... Have anyone got this to work I have the links for the miui for u980 but its my only device now n I don't want to risk ... If so can anyone post a screen shot for it n is it worthy I always was a fan for slimroms... Didn't like miui but its the only option now ... Also I found a link to twrp recovery for it... My main concern is not bricking the device as I always used to flash Samsung devices n this is my 1st time with hisense... But I like the device n the hardware is good enough for me... Do u think miui will make a difference..
Thx
graham_1 said:
Hi guys,
I was wondering if anyone would be kind enough to point me to a link for a Hisense U980 Stock Recovery and scatter file. Mine has unfortunately become corrupted and i currently have the MLS recovery (Chinese) version on my device. I've basically followed the guide I've found on XDA forums to root and install the custom ROM but i'm having the following issues:
After flashing the custom, my SIM management option is greyed out under settings. Therefore, it's not detecting either of the SIM card's installed (dual SIM phone).
Running the new MIUI OS, my devices soft keys (Home, Back buttons etc.) are no longer functional making it difficult to navigate menu options.
I've tried following the tutorial to create a stock recovery but MTK Droid Tools is not detecting my device.
I've downloaded the stock ROM from needrom but am unable to flash it with the current recovery.
My feeling is, if i can revert to the stock recovery, i'll be able to flash the stock ROM.
I've posted some images as well.
Any help will greatly appreciated.
Thanks,
Graham
Click to expand...
Click to collapse
Hello Graham and everyone, you guys are struggling so much.
I'm gonna try to backup my rom and post it for all of you my friends.
But gonna have to clean it first, so be patient. Have a good day.
Ok, i finished uploading my ROM, I don't know if the stock recovery is included in it.
I would like to help you and backup or copy/paste my stock recovery files. I will search online and if you have an idea you can help me too.
I can't use a PC because currently my phone's USB is broken and no one has a similar one here. So, I'm ordering one online.
That's why i backed my ROM using "Online nandroid backup".
Here is the link for the ROM:
http://forum.xda-developers.com/android/development/rom-hisense-hs-u980-t3147968
Hello guys,
I have a problem with my OnePlus X, and it would be lovely if I could get some help or advice from you guys.
> To provide some slight background, I purchased this off of eBay to complete my OnePlus collection. Most listings were above what OnePlus originally sold the phone for, but I found one for $125 in good condition by a seller with a good rating. It was advertised as soft-bricked, with Fastboot in working order. I thought "no problem, I'll just reflash it and be on my merry way."
Now onto the issue. I received it, charged it up, and attempted flashing the official recovery provided by OnePlus, but something is not working. I've been tinkering with Android for a number of years now, so I troubleshooted as much as I could, but to no avail.
1. Starting with device unplugged and powered off, boot into fastboot
2. Plugged into the computer, and ran `fastboot devices` to ensure it's recognized. After that, I flashed the recovery.img that was on my desktop with `fastboot flash recovery recovery.img` (yes I was in the correct directory). It looked successful. Picture of cmd response text at the following imgur album: /a/25DEQ (sorry I cannot post full links yet, had to create a new xda profile, forgot my old one :/
3. Unplugged the phone, powered off, Volume Down + Power to attempt boot into recovery. Failure. It just turns on with the 1+ logo, and quickly flashes the 'android' logo at the bottom. It stays like this until I manually power off.
I'm a bit stumped I have to admit. I would greatly appreciate any input you folks have. Thank you.
AndriyEtch said:
Hello guys,
I have a problem with my OnePlus X, and it would be lovely if I could get some help or advice from you guys.
> To provide some slight background, I purchased this off of eBay to complete my OnePlus collection. Most listings were above what OnePlus originally sold the phone for, but I found one for $125 in good condition by a seller with a good rating. It was advertised as soft-bricked, with Fastboot in working order. I thought "no problem, I'll just reflash it and be on my merry way."
Now onto the issue. I received it, charged it up, and attempted flashing the official recovery provided by OnePlus, but something is not working. I've been tinkering with Android for a number of years now, so I troubleshooted as much as I could, but to no avail.
1. Starting with device unplugged and powered off, boot into fastboot
2. Plugged into the computer, and ran `fastboot devices` to ensure it's recognized. After that, I flashed the recovery.img that was on my desktop with `fastboot flash recovery recovery.img` (yes I was in the correct directory). It looked successful. Picture of cmd response text at the following imgur album: /a/25DEQ (sorry I cannot post full links yet, had to create a new xda profile, forgot my old one :/
3. Unplugged the phone, powered off, Volume Down + Power to attempt boot into recovery. Failure. It just turns on with the 1+ logo, and quickly flashes the 'android' logo at the bottom. It stays like this until I manually power off.
I'm a bit stumped I have to admit. I would greatly appreciate any input you folks have. Thank you.
Click to expand...
Click to collapse
Which recovery u tried? Did u knOw the previous os version details?
And try this after flashing recovery in fastboot, boot into it directly by giving a cmd "fastboot boot recovery.img"
cva_kabil said:
Which recovery u tried? Did u knOw the previous os version details?
And try this after flashing recovery in fastboot, boot into it directly by giving a cmd "fastboot boot recovery.img"
Click to expand...
Click to collapse
Hi! Thank you for your reply
I posted this same question on the /r/oneplus subreddit, and received a quick and helpful walkthrough. Turns out part of the problem was that the micro-usb port on the phone itself is a bit unreliable. I haven't investigated too deeply, but it took a while to find a position for the wire to maintain a stable connection. I suspect this may be why the device was bricked in the first place (disconnect when flashing rom/kernel/etc.)
Anyways, for some reason flashing the stock recovery to the phone was just not working. The guy on reddit recommended trying TWRP, and that worked immediately. However, at that point, I had no idea what the history of the phone was or what OS was on it before, what firmware it had. I tried installing the official CM13 and then Sultan's CM13 with no luck. What *did* work was Oxygen OS 2.2.6.
At this point I'm stuck yet again though... The Marshmallow OTA (3.1.3) in the OS shows as available for download, but when I try to install the download only gets to 22% and then stops. Flashing the 3.1.3 OTA.zip available on OnePlus' support site doesn't work in TWRP, and when I try to flash stock recovery, it doesn't work.. don't know what else to try.
AndriyEtch said:
Hi! Thank you for your reply
I posted this same question on the /r/oneplus subreddit, and received a quick and helpful walkthrough. Turns out part of the problem was that the micro-usb port on the phone itself is a bit unreliable. I haven't investigated too deeply, but it took a while to find a position for the wire to maintain a stable connection. I suspect this may be why the device was bricked in the first place (disconnect when flashing rom/kernel/etc.)
Anyways, for some reason flashing the stock recovery to the phone was just not working. The guy on reddit recommended trying TWRP, and that worked immediately. However, at that point, I had no idea what the history of the phone was or what OS was on it before, what firmware it had. I tried installing the official CM13 and then Sultan's CM13 with no luck. What *did* work was Oxygen OS 2.2.6.
At this point I'm stuck yet again though... The Marshmallow OTA (3.1.3) in the OS shows as available for download, but when I try to install the download only gets to 22% and then stops. Flashing the 3.1.3 OTA.zip available on OnePlus' support site doesn't work in TWRP, and when I try to flash stock recovery, it doesn't work.. don't know what else to try.
Click to expand...
Click to collapse
Root your device using twrp or kingoroot method then install flashify and try to flash stock recovery using flashify. .. Tht may work.
Flashing 3.1.3 via official twrp ll not work... Cos ur bootloader version, U can do it only with stock recovery or u need to edit meta data file. Or u can flash stock recovery img file by twrp
cva_kabil said:
Root your device using twrp or kingoroot method then install flashify and try to flash stock recovery using flashify. .. Tht may work.
Flashing 3.1.3 via official twrp ll not work... Cos ur bootloader version, U can do it only with stock recovery or u need to edit meta data file. Or u can flash stock recovery img file by twrp
Click to expand...
Click to collapse
Thanks I'll give those a shot once I'm home from work! Quick question about editing the META INF. I've heard that doing so risks hard-bricking the device. Is that true?
AndriyEtch said:
Thanks I'll give those a shot once I'm home from work! Quick question about editing the META INF. I've heard that doing so risks hard-bricking the device. Is that true?
Click to expand...
Click to collapse
I dont think so... I hv not tried... But as of i know if u edit it wrongly, u will not be able to flash that file. . Try others methods first... Hope it works
AndriyEtch said:
Thanks I'll give those a shot once I'm home from work! Quick question about editing the META INF. I've heard that doing so risks hard-bricking the device. Is that true?
Click to expand...
Click to collapse
Hi OP, sorry for joining late to the party
So the thing is the OnePlus X is at opposites now since the official MM release on 29th September. The thing is if you are running the old bootloader (OxygenOS 2.x.x) or any ROM based on it, then the New TWRP will not boot, neither will the Stock Recovery that is hosted on the OnePlus download section for the X, which is where i assume you download the stock recovery from, right ? Also note that the official recovery hosted on the TWRP website is also yet to be updated, we're working on that.
So you are on the old Bootloader. Simple stuff. I have posted my guide a lot of time around the forums, its gained a lot of merit. You could follow it for your update process. I'll leave a link below. In case you wanna verify that the old bootloader is causing the issue my Index Thread pinned in the general section has a link for the Stock recovery for Old bootloader, try flashing that via fastboot, if it successfully boots then you're set.
Comprehensive guide to Update to Marshmallow Bootloader
The above guide is centered to the thread i have posted it on but the process is 99% the same. In the end, you could just stay with Oxygen OS 3.1.3, or flash any custom ROM based on the new Bootloader.
Now regarding your query about editing the META of the ROM, well Yes to an extent it IS risky if you ain't careful because my guide guides you to delete the one single line that removes the device check, so as long as you use the modified zip on OnePlus X only, there will be no issues.
Let me know for any further clarifications, also you're welcome to join our support group on Telegram, all of our developers are active there. Ping me (@ mellogang_unite) for an invite
There isn't much development done on this phone and there aren't any updates for stock ROM due to come out. So I've decided to try and port LineageOS from another phone with the same chipset. Problem is that when I follow any guide I can seem to find on here, nothing ever is as the guide states. The copy and paste method doesn't work because the names of the files don't match when I extract the boot.img's. Not to mention that I can't even get the system.img to extract whatsoever. I've tried various tools and have only ever had one tell me about the system.img, and that took hours. It still wouldn't extract it either though. I'm not brand new to Android, it's just been several years since I've really decided to play with them. Currently I have TWRP 3.2.1 installed with the stock ROM rooted with Magisk 24. Even simple modifications on the stock ROM, such as debloating, will cause every app on the phone to not work anymore after a reboot. Ultimately causing me to reflash the stock ROM and going through the root process all over again. Can someone please point me in the proper direction to get rid of this terrible stock ROM and begin building my own port? Thank you ahead of time.