Well before we kick off you should atleast if nothing is working be able to get into fastboot.
Disclaimer:I'm not responsible if your device flies off your hand or melts and gets into the sea....Just Be responsible before using this!!
OK
#This should be when you can't boot up into any thing and you don't have any rom on your SDcard.(when the only thing you see is the oppo logo)
-Plug your device to a charger and allow it get charged if it doesn't have charge.
-Download this recovery package which comes with fastboot and ADB drivers.
-Download these roms CM10.1 or stock ( or any other one of your choice).
-Download Cwm recovery too.
-Make sure you have the device drivers installed.
-Boot into fastboot mode ie hold vol up+pwr button when ur device is off.
-Unzip the 1st recovery zip file to a folder and place your rom and cwm recovery img(rename to recovery.img before pasting) in there.
-Hold shift then right click in this folder and choose "open command window here".
-In this command prompt write "fastboot flash recovery recovery.img.(don't close after its use)
-When this is done boot into recovery by turning off the device and holding the pwr+vol down button until you see the recovery menu.
-Erase cache,factory reset and wipe dalvik cache to be sure.
-Return to command window and write adb[]push[]"name of rom"[]/sdcard/ ('name of rom' should have the exact rom name+ .zip )[] means space.
-Now install rom from sdcard and choose rom and you should be good to go.
-Rom boots yay!!Brick fixed!!
hit thanks if this helped!!
hI,
thanks for good explanation. I was able to to download all files except recovery with drivers from your first link. Any possibility to upload somewhere else? Thanks. :good:
strale.zivic said:
hI,
thanks for good explanation. I was able to to download all files except recovery with drivers from your first link. Any possibility to upload somewhere else? Thanks. :good:
Click to expand...
Click to collapse
You may have to signup b4 you can d/l a file.
I had no problem getting the file.
strale.zivic said:
hI,
thanks for good explanation. I was able to to download all files except recovery with drivers from your first link. Any possibility to upload somewhere else? Thanks. :good:
Click to expand...
Click to collapse
changed!!
You saved my day. THX.
Verstuurd van mijn X909 met Tapatalk
When in fast boot what is it supposed to say? Because mine is only showing some "Chinese characters and fastboot...."
izbrian said:
When in fast boot what is it supposed to say? Because mine is only showing some "Chinese characters and fastboot...."
Click to expand...
Click to collapse
yep
-Return to command window and write adb[]push[]"name of rom"[]/sdcard ('name of rom' should have the exact rom name+ .zip extension)[] means space.
That's mean i must extract the rom (of course with zip) or just zip only at the same folder?
---------- Post added at 04:58 PM ---------- Previous post was at 04:57 PM ----------
[/COLOR]
OldClass said:
-Return to command window and write adb[]push[]"name of rom"[]/sdcard ('name of rom' should have the exact rom name+ .zip extension)[] means space.
That's mean i must extract the rom (of course with zip) or just zip only at the same folder?
Click to expand...
Click to collapse
just put the rom.zip into the same folder where you extracted adb and fastboot files
Can you upload the "recovery" file from your first post somewhere else, cant download.
And thanks for your efforts,OP?
xenkato said:
Can you upload the "recovery" file from your first post somewhere else, cant download.
And thanks for your efforts,OP?
Click to expand...
Click to collapse
Check it out now and BTW hit thanks instead of saying it !
-Erase cache,factory reset and wipe dalvik cache to be sure.
Affter this step , do i need turn off and chang to Fastboot mode by +Vloum and power buton . Or stay in recovery mode , and do below step .
When i stay in recvery mode , my computer can not reconigze the device . can't not find driver for find 5
-Return to command window and write adb[]push[]"name of rom"[]/sdcard/ ('name of rom' should have the exact rom name+ .zip extension)[] means space.
---------- Post added at 04:16 PM ---------- Previous post was at 03:34 PM ----------
I downloaded driver from here http://www.oppoforums.com/threads/usb-drivers-for-find-5.746/
But when i turn in to recovery mode , my computer can not update driver for find 5 ( Window 7)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
thongdtk3 said:
-Erase cache,factory reset and wipe dalvik cache to be sure.
Affter this step , do i need turn off and chang to Fastboot mode by +Vloum and power buton . Or stay in recovery mode , and do below step .
When i stay in recvery mode , my computer can not reconigze the device . can't not find driver for find 5
-Return to command window and write adb[].......
Click to expand...
Click to collapse
If you can't even install drivers on windows 7 sorry I can't help.Youtube has thousands of videos on this.If you can't install the drivers forget.The guide won't work.
hackarchive said:
If you can't even install drivers on windows 7 sorry I can't help.Youtube has thousands of videos on this.If you can't install the drivers forget.The guide won't work.
Click to expand...
Click to collapse
I have already Flash recovery successful but the final step :
-Return to command window and write adb[]push[]"name of rom"[]/sdcard/ ('name of rom' should have the exact rom name+ .zip extension)[] means space.
I could not do it .
thongdtk3 said:
I have already Flash recovery successful but the final step :
-Return to command window and write adb[]push[]"name of rom"[]/sdcard/ ('name of rom' should have the exact rom name+ .zip extension)[] means space.
I could not do it .
Click to expand...
Click to collapse
[] means space like "adb push maxwenAOKP/sdcard....."Like that without the quotes.It should work if ur in recovery and have ur phone plugged in.Also it takes time.Roms are 100mb+ so give it 5 mins even if you see nothing on the command screen.If there's an error repeat!
hackarchive said:
[] means space like "adb push maxwenAOKP/sdcard....."Like that without the quotes.It should work if ur in recovery and have ur phone plugged in.Also it takes time.Roms are 100mb+ so give it 5 mins even if you see nothing on the command screen.If there's an error repeat!
Click to expand...
Click to collapse
My phone in recovery mode and connect cable . I use PDAnet ( http://www.droidiser.com/2012/11/how-to-install-drivers-for-any-android.html ) and install driver , the result as below pic :
But when i try copy room to SDcard , the fail as below , Pls give me comment for my work ,thanks alot
dont put extension and fullstop.They r not needed. adb push X909EROM_12_130828_Beta_full.zip /sdcard/X909EROM_12_130828_Beta_full.zip
Next time don't do this mistake.Always have a rom on you device.
hackarchive said:
dont put extension and fullstop.They r not needed. adb push X909EROM_12_130828_Beta_full.zip /sdcard/X909EROM_12_130828_Beta_full.zip
Next time don't do this mistake.Always have a rom on you device.
Click to expand...
Click to collapse
Sory cause borther you many time ...Bro . So I connect my phone to laptop Some time I Put command but it's show Error : Device offline .
I unplug and plug the cable again and continue put adb command and the result as below .
But when I install from Zip file , have no Room in Sdcard .... So any one have any comment for my work ? thanks
Any one have answer for me , Thank you so much
thongdtk3 said:
Any one have answer for me , Thank you so much
Click to expand...
Click to collapse
The above means it worked reboot in recovery and try to install the rom. It's in your sdcard. Device offline means no device. Remove and reconnect.
Sent from my GT-N8010 using XDA Premium 4 mobile app
Related
Credits/Disclaimer
Code:
[U][B]
This is not my guide, you dont have to thank me for this.
Thanks to Ocnbrze over at AndroidForums for this.
we are not responsible if your device(s) cause(s) a nuclear war[/B][/U]
This will show you how to FULLY unroot your evo to stock. S-ON *****(LOCKED OOW)*****
THIS ONLY WORKS IF YOU USED HTCDEV METHOD!!!!!
Please read thru this guide once or twice before actually taking steps !
Your phone MUST be on a stock sense rom so go get that installed now !
Download these files if you do not have them
ADB.exe http://d-h.st/Vsv
FastBoot.exe http://d-h.st/KB3
AdbWinApi.dll http://d-h.st/MJn
flash_image.zip http://themikmik.com/attachment.php?attachmentid=5377&stc=1&d=1327588554
mtd_eng.zip http://themikmik.com/attachment.php?attachmentid=5378&stc=1&d=1327588554
PC36IMG_SuperSonic_GB_Sprint_WWE_4.67.651.3 http://d-h.st/n1U
Before you do anything else, your phone MUST be on a stock sense rom !
step #1 downgrading the misc partition
1.download the first three files and create a folder and call it android then move the downloaded files to the android folder.(you should have already have this setup when you rooted with HTCdev)
2.download and install (do not run) htc sync: http://www.mediafire.com/?cdcjs0ue8tne4cy
3.connect your phone to the pc via usb cable
4.we need to extract and then move the flash_image and the mtd-eng files on to the sd card. make sure that you do not put the extracted files in any folders. they need to be on the root of the card (very top level)
5.change the setting from disk to charge only, make sure that usb debugging is turned on, settings>apps>development>check usb debugging, and lastly make sure that fastboot is disabled, settings>apps>uncheck fastboot.
6.on your pc hold shift while right clicking on the android folder. select open command window here option.
7. in the command window type:
Code:
[B][I]adb shell
ok you should get # in the command window if not then something went wrong.
if you do get # then type:
Code:
cat /sdcard/flash_image > /data/flash_image
then:
Code:
chmod 755 /data/flash_image
and last:
Code:
/data/flash_image misc /sdcard/mtd-eng.img
the command screen should look like this when all the commands are entered:[/I][/B]
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
download the 4.67 PC36IMG file and rename it by deleting everything but the PC36IMG part in the name. make sure not to add an extra zip as windows hides extensions.
move it to the root of the sd card that means on the top level of the card and not in any folders.
power off then press and hold power+vol down. this will take you to the bootloader. if you named the file right and it is on the root of the card then it will ask you to update. select yes.
before you reboot your phone double check your bootloader screen. at the top it should say locked and your hboot should be 2.18 with s-on. if that is what you see then congrats!!!!!!!!!! you are now unrooted!!!!!!!!!!!!
XenonV said:
First things first- Not my guide, You are fully responsible for whatever happens. It is not XDA's fault, its not my fault, its all on you.
This will show you how to FULLY unroot your evo to stock. S-ON *****(LOCKED OOW)*****
THIS ONLY WORKS IF YOU USED HTCDEV METHOD!!!!!
Download these files if you do not have them
ADB.exe http://d-h.st/Vsv
FastBoot.exe http://d-h.st/KB3
AdbWinApi.dll http://d-h.st/MJn
flash_image.zip http://themikmik.com/attachment.php?attachmentid=5377&stc=1&d=1327588554
mtd_eng.zip http://themikmik.com/attachment.php?attachmentid=5378&stc=1&d=1327588554
PC36IMG_SuperSonic_GB_Sprint_WWE_4.67.651.3 http://d-h.st/n1U
Now lets begin
step #1 downgrading the misc partition
1.download the first three files and create a folder and call it android then move the downloaded files to the android folder.(you should have already have this setup when you rooted with HTCdev)
2.download and install (do not run) htc sync: http://www.mediafire.com/?cdcjs0ue8tne4cy
3.connect your phone to the pc via usb cable
4.we need to extract and then move the flash_image and the mtd-eng files on to the sd card. make sure that you do not put the extracted files in any folders. they need to be on the root of the card (very top level)
5.change the setting from disk to charge only, make sure that usb debugging is turned on, settings>apps>development>check usb debugging, and lastly make sure that fastboot is disabled, settings>apps>uncheck fastboot.
6.on your pc hold shift while right clicking on the android folder. select open command window here option.
7. in the command window type:
Code:
[B][I]adb shell
ok you should get # in the command window if not then something went wrong.
if you do get # then type:
Code:
cat /sdcard/flash_image > /data/flash_image
then:
Code:
chmod 755 /data/flash_image
and last:
Code:
/data/flash_image misc /sdcard/mtd-eng.img
the command screen should look like this when all the commands are entered:[/I][/B]
download the 4.67 PC36IMG file and rename it by deleting everything but the PC36IMG part in the name. make sure not to add an extra zip as windows hides extensions.
move it to the root of the sd card that means on the top level of the card and not in any folders.
power off then press and hold power+vol down. this will take you to the bootloader. if you named the file right and it is on the root of the card then it will ask you to update. select yes.
before you reboot your phone double check your bootloader screen. at the top it should say locked and your hboot should be 2.18 with s-on. if that is what you see then congrats!!!!!!!!!! you are now unrooted!!!!!!!!!!!!
Click to expand...
Click to collapse
I've actually been dealing with this most of the day trying to unroot and go back 100% stock and have had no success. It was suggested elsewhere that I need to be on a stock rom? I'm dl'ing one now to try as I am currently on an ics rom.
yes you do need to be on a stock sense rom so download a stock sense rom, and then follow the guide
XenonV said:
yes you do need to be on a stock sense rom so download a stock sense rom, and then follow the guide
Click to expand...
Click to collapse
Perhaps a good bit of info to add to the op
Relentless D said:
Perhaps a good bit of info to add to the op
Click to expand...
Click to collapse
already on it, thanks
So I noticed you said this isn't your guide, but I see no credits in your post for where the guide originated, or who originally wrote the info? I'm sure this will help a lot of people though.
Captain_Throwback said:
So I noticed you said this isn't your guide, but I see no credits in your post for where the guide originated, or who originally wrote the info? I'm sure this will help a lot of people though.
Click to expand...
Click to collapse
i dont know who the original writer is, which is why. if i know then i always list that info :good:
XenonV said:
i dont know who the original writer is, which is why. if i know then i always list that info :good:
Click to expand...
Click to collapse
Where did you get it from, then?
It looks strikingly similar to this guide:
http://androidforums.com/evo-4g-all-things-root/526575-guide-unrooting-gingerbread-2-3-5-a.html
In fact, the inordinate number of exclamation points and the use of my command prompt screenshot makes me think it originated over there.
Captain_Throwback said:
Where did you get it from, then?
Click to expand...
Click to collapse
somebody PM'd me the guide on another website (the tech game) , just the text, no link
XenonV said:
somebody PM'd me the guide on another website (the tech game) , just the text, no link
Click to expand...
Click to collapse
http://androidforums.com/evo-4g-all...-rooting-gingerbread-2-3-5-dummies-guide.html
If this is where it originated (as it seems to have) it was written by user oznbrze at androidforums.com
Relentless D said:
http://androidforums.com/evo-4g-all...-rooting-gingerbread-2-3-5-dummies-guide.html
If this is where it originated (as it seems to have) it was written by user oznbrze at androidforums.com
Click to expand...
Click to collapse
problem solved thanks :good:
and yes this is my guide. however, you do not need to be on stock sense, just not on ics roms for this to work. just throwing that out there.
I tired this and when I put the first command in the window I get a $ sign not the # sign can some one help please..
bgsl1ck said:
I tired this and when I put the first command in the window I get a $ sign not the # sign can some one help please..
Click to expand...
Click to collapse
make sure you are running command prompt as admin. or logged in to an admin account. and all the files are in correct directories
bgsl1ck said:
I tired this and when I put the first command in the window I get a $ sign not the # sign can some one help please..
Click to expand...
Click to collapse
Are you running a rooted ROM? You need to have root access for this to work. Try typing "su" at the prompt and see if it changed to a #.
thanks
Can this be done using a Mac?
XenonV said:
make sure you are running command prompt as admin. or logged in to an admin account. and all the files are in correct directories
Click to expand...
Click to collapse
i have tried that and it still doesnt work, any help!?
im running a brand new computer like seriously out of the box, windows 7 ultimate and it wont give the #
Chirpout said:
Can this be done using a Mac?
Click to expand...
Click to collapse
yes, i believe the guide states something about that..not exactly sure, you can also use google for more help
Hi, I know this is really out of date, but I have to send my phone back because the screen is cracked (inner touch screen) and I wanted the phone to be completely stock. I never rooted the phone. I only unlocked the bootloader. I found this thread hoping I could relock the bootloader to make it look like I never unlocked it in the first place. Of course once I reached Step 7, I don't get the # sign. I get the $ sign and I don't know what to do :/
Tool Aces Present..
Universal PA Porter
About the tool:
This tool can be used to port the great Paranoid Android ROMs from any device. It's based on the guide of adityalahiri13. Thank him too.
How to use:
Make sure you that both the ROMs(Base and PA) have the same resolution. I recommend taking CM as base. Also make sure that the android versions of base and PA ROM matches. Try to use port from a device of same manufacturer, though it may not matter much.
Steps-
1. Place base ROM zip in CM folder.
2. Place PA ROM zip in PA folder.
3. Now click on Main.bat the tool will do some steps.
4. After this it will ask for your device resolution. Choose one among 5.
5. Then it will open build.prop and another file. Copy the lines from another text file to the build.prop below ro.modversion= and write the PA version you are porting infront of ro.pa.version=
6. Save and exit.
7. Now it will open updater-script and another file. Copy the line from another file and paste it to your updater-script below this line:
Code:
set_perm(1000, 1000, 0644, "/system/etc/paranoid/properties.conf");
8. Then it will ask for your android version. Choose ICS or JB, then it will zip the ROM, select name as desired and find your ROM in /PORT folder.
Congrats on your newly ported ROM.
Downloads:
Download the tool from here.
Screenshot:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
FAQs:
Q. Well I ported this accordingly but it's stuck in bootloop. How to solve it?
A. In some cases this happens. Simply run bootloop.bat and see if it works. If it still doesn't works then run bootloop2.bat. Make sure to check if the ROM boots after running bootloop.bat, if still stuck on bootloop then only run bootloop2.bat
Q. Why you recommend porting from same manufaturer?
A. Well you can port from others also but in some of them you might need some framework modding and also need to do some modding in kernel. But in most cases even from other manufacturers the ROM should work.
Q. How can I help?
A. Pressing THANKS button would be enough.
Click to expand...
Click to collapse
Credits:
1.adityalahiri13- For such a great guide. Thank him too
2. Paranoid Android Team- For such great efforts on such great ROM.
Reserved
Sent from my ST21i2 using xda premium
wow it will try this, if heped i ll press thanks
This is a great idea,but when i run this as a regular user,it extracts everything ok and asks if i want to replace all the term.nfo files,then it finishes and closes,so i tried running it as admin and same thing.it extracts the roms,but thats about it for me,im on windows 7 professional.I read the OP,am i missing something?I have everything i need installed.
Diablo67 said:
This is a great idea,but when i run this as a regular user,it extracts everything ok and asks if i want to replace all the term.nfo files,then it finishes and closes,so i tried running it as admin and same thing.it extracts the roms,but thats about it for me,im on windows 7 professional.I read the OP,am i missing something?I have everything i need installed.
Click to expand...
Click to collapse
Sorry can't get ur error properly can u send some screens? Also I've tested it and it works ok.. but still I'll try my best to help u out
Press THANKS if I helped,
Best Regards,
AJ
alokbina is now Abhinav2
Greetings, i have just tried your tool, after extract of CM and PA roms when i'm asked to press any key i get some error and cmd closes by itself, i cannot see the error, since it closes after 0.1sec when the error appears
Try hypercam to record or press prnt scrn fast...I do the same..
Press THANKS if I helped,
Best Regards,
AJ
alokbina is now Abhinav2
If the tool isn't running at all for you guys, you are either trying to run the .bat file from within the zip, or you extracted the zip file wrong.
Extract the zip with Winrar.
Just right click the file and select "Extract Files..." than click OK.
I haven't tried porting this yet but the tool itself works just fine.
m4nu4l said:
Greetings, i have just tried your tool, after extract of CM and PA roms when i'm asked to press any key i get some error and cmd closes by itself, i cannot see the error, since it closes after 0.1sec when the error appears
Click to expand...
Click to collapse
Extract files to just to short path, for example to "c:\porting\" or "d:\porting\".
This problem shows when .bat is deep in folder.
I am really excited for this tool. THANKS
I extracted the files and attempted to run the tool, but it closes after CM and PA are extracted. Is there something I am doing wrong. I have a Maguro (GSM Galaxy Nexus). Base ROM = CM10.1 (4/22) and Port ROM = PA 3.16 (4/16). After ROMS are extracted, the tool closes. Tool is located in G: Porter
aiinjylls said:
I am really excited for this tool. THANKS
I extracted the files and attempted to run the tool, but it closes after CM and PA are extracted. Is there something I am doing wrong. I have a Maguro (GSM Galaxy Nexus). Base ROM = CM10.1 (4/22) and Port ROM = PA 3.16 (4/16). After ROMS are extracted, the tool closes. Tool is located in G: Porter
Click to expand...
Click to collapse
Now after so many reports I think there's some fault with the tool...though I checked it..still if u can try to get the error it's best..anyways I'll try to fix this today itself
Best Regards,
AJ
alokbina is now Abhinav2
Is this still alive? Just curious, thx.
Sent from my Smooth(ROM) Kindle Fire
Diablo67 said:
This is a great idea,but when i run this as a regular user,it extracts everything ok and asks if i want to replace all the term.nfo files,then it finishes and closes,so i tried running it as admin and same thing.it extracts the roms,but thats about it for me,im on windows 7 professional.I read the OP,am i missing something?I have everything i need installed.
Click to expand...
Click to collapse
m4nu4l said:
Greetings, i have just tried your tool, after extract of CM and PA roms when i'm asked to press any key i get some error and cmd closes by itself, i cannot see the error, since it closes after 0.1sec when the error appears
Click to expand...
Click to collapse
aiinjylls said:
I am really excited for this tool. THANKS
I extracted the files and attempted to run the tool, but it closes after CM and PA are extracted. Is there something I am doing wrong. I have a Maguro (GSM Galaxy Nexus). Base ROM = CM10.1 (4/22) and Port ROM = PA 3.16 (4/16). After ROMS are extracted, the tool closes. Tool is located in G: Porter
Click to expand...
Click to collapse
I'm really sorry guyz it was my mistake....fixed the tool now Please forgive me if possible guyz....Enjoy :good:
Cheers,
AJ
Do we redownload?
I took a look at main.bat ( noticed a spelling error in command goto del *it said delco* )
I think Bootloop2.bat may have errors. I get system cannot find specified file
Sent from my Galaxy Nexus using xda premium
Getting SOrry error porting.Please Check you have done everything properly
aiinjylls said:
Do we redownload?
I took a look at main.bat ( noticed a spelling error in command goto del *it said delco* )
I think Bootloop2.bat may have errors. I get system cannot find specified file
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Yes I fixed the errors and now it will work
nlygamz said:
Getting SOrry error porting.Please Check you have done everything properly
Click to expand...
Click to collapse
I've checked it thrice man...just tell me in detail wat all happens....
Cheers,
AJ
stuck in bootloop....damn man.....the PA logo just goes on and on
I redownloaded and it runs through completely without errors
- it skips the build.prop prompt though
The Bootloop.bat runs smoothly
The Bootloop2.bat always gives me "file not found"
I have not successfully booted a ROM, but its working for me
Sent from my Galaxy Nexus using xda premium
nlygamz said:
stuck in bootloop....damn man.....the PA logo just goes on and on
Click to expand...
Click to collapse
Please run the bootloop batch scripts and then try to do a logcat.
Cheers,
AJ
ran bootloop and bootloop2 ....it runs fine now....just need to do some manual handwork in it! Thanx man! Appreciate your help
---------- Post added at 09:37 AM ---------- Previous post was at 09:18 AM ----------
http://postimg.com/image/138000/paport-137438.jpg <<< Check this out @Abhinav2
WARNING: IF YOU ARE NOT GOING TO START FROM STEP 1 AND FOLLOW EACH STEP EXACTLY HOW I HAVE WROTE IT THEN YOU WILL FAIL. THIS METHOD WORKS IF YOU CAN FOLLOW THE DIRECTIONS.
IF YOU DID NOT RESTORE YOUR PHONE AND FOLLOW EACH STEP EXACTLY HOW I LISTED BELOW THEN DO NOT SAY THIS DOESN'T WORK FOR YOU.
Step 1. Follow @evilpotatoman 's guide below to restore your phone to MJ5 FIRST
Guide:
1) Download and install Heimdall from here for windows. You'll need this and this to avoid missing .dll file errors
2) Download the following files:
MI9_fix.img.ext4
sec_csc.zip
2400258.zip
Put sec_csc.zip and 2400258.zip on your external SD card
3) Download and install the MJ5 partitions. Use Odin to flash these files (match the file names with the different upload slots)AP_N900AUCUBMJ5.zipBL_N900AUCUBMJ5.zipCP_N900AUCUBMJ5.zipHLTE_USA_ATT_32G.pit
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
4) Now is the time to use Heimdall.
Reboot into Download Mode once Odin finishes.
Install the vcredist packages downloaded from step 1.
unzip the heimdall .zip file to c:/
go to c:/Heimdall Suite/Drivers and click on zadig.exe
click the middle menu button to select "Show All Devices"
from the dropdown, select MSM8960
click the "install driver" button.
you should see a success message
5) Navigate on your computer to c:/Heimdall Suite/ and open heimdall-frontend.exe.
IMPORTANT -- Go to the Utilities tab and click the "Detect" button
Go to the Flash tab on Heimdall, click Browse and select the HLTE_USA_ATT_32G.pit file downloaded from step 3
Click the 'add' button, then next to 'partition name' select system from the dropdown.
click the Browse button underneath the dropdown, and select the MI9_fix.img.ext4 image you downloaded from step 2.
6) Click Start. ***I usually check the 'No Reboot' box to prepare for booting into recovery
7) Heimdall and your Note will report a bad flash at around 95% -- but don't worry -- your system.img got uploaded Reboot directly into recovery mode.
8) Once in recovery, select "Choose update from external" in the recovery, and select the sec_csc.zip you downloaded earlier (did you remember to put that file on your external SD card?). This will install the CSC files and run the preload checkin so you don't FC all over the place
9) IMPORTANT--After flashing the sec_csc, the Note will reboot.
Try to catch it in time to reboot BACK into recovery
Once in recovery, select "Choose update from external" in the recovery, and select the 2400258.zip you downloaded earlier.
END OF MJ5 RESTORE GUIDE - CONTINUE BELOW
Step 2. YOU ARE NOW ON MJ5 BE SURE TO DOWNLOAD AND INSTALL THE NB4 OTA UPDATE BEFORE CONTINUING!!!
Step 3. When you're finished the restore guide to MJ5 and updated to NB4 then delete any other files used from the restore guide so you don't mix them up and download the following 2 files:
1- Miata KitKat Fix v1
2- KitKat Ota ZipStep 4. Extract the Miata_KK_Fix_1.0.zip to the root of your BOTH your phone storage and your sd card. (make sure they are not in any folders!!!)
Step 5. Once both files in the Miata_KK_Fix_1.0.zip are extracted and copied to both your phone and the sd card... then reboot the phone.
VERY IMPORTANT TO REBOOT NOW
Step 6. Pick one of the follow options...
(Option A) - Wipes phone - I recommend this method
1. Rename 2400258.zip to update.zip and copy to EXTERNAL STORAGE (aka sd card)
UNPLUG USB CABLE BEFORE CONTINUING
2. Reboot into RECOVERY MODE (volume up + home) and select "Apply Update from external storage" and select your update.zip
3. It should start the update process and finish successfully! Enjoy!
If you made it this far and it fails or gives you an error then you did something wrong. Start from step 1 restoring your phone to MJ5
(Option B) - Doesn't wipe phone
1. You are going to need an ADB Side loader and it can be found here.
2. Extract to directory C:\Mini-SDK
3. Rename 2400258.zip to update. (DO NOT NAME UPDATE.ZIP, JUST "update".)
4. Place "UPDATE" into the same folder as your ADB C:\Mini-SDK
5. Hold shift and right click in the folder to "Open command window here"
6. Reboot your phone into RECOVERY MODE (volume up + home)
7. Select "Apply update from ADB"
8. Plug phone into usb on PC
9. In your command window type "adb sideload update" without quotes and enjoy!
If you made it this far and it fails or gives you an error then you did something wrong. Start from step 1 restoring your phone to MJ5
(Option C) - Untested
1. Settings, General, About, Software Update, Check for updates...
2. Download and install update
If you made it this far and it fails or gives you an error then you did something wrong. Start from step 1 restoring your phone to MJ5
Thanks @opsmgr3774 for the donation!
Thanks @Ciberious42 and @evilpotatoman and anyone else I forgot.
Q&A
1. Is this safe?
Yes it's using the same exploit from Root De La Vega to run a script that replaces the bad file that is stopping the OTA from installing.
What the script does:
Code:
mount -o rw,remount /system
rm /system/bin/mobicore-presetup.sh
cp /sdcard/mobicore-presetup.sh /system/bin
rm /sdcard/rldv.sh
2. It doesn't work for me!!!
Try it again from the very beginning and read step by step, slowly. Make sure you didn't miss anything! Download the files again also.
mazdamiata210 said:
Reserved
Click to expand...
Click to collapse
Im sure people would be a little more willing to try this is there was a little more info here.
What are these files fixing when flashed, how do i know that these good/ok files to flash that will not brick my device? Because you said it should work. Not nit picking or even saying that it doesnt work. BUT more info on what this is would be beneficial to everyone.
the2rrell said:
Im sure people would be a little more willing to try this is there was a little more info here.
What are these files fixing when flashed, how do i know that these good/ok files to flash that will not brick my device? Because you said it should work. Not nit picking or even saying that it doesnt work. BUT more info on what this is would be beneficial to everyone.
Click to expand...
Click to collapse
Well you're not flashing anything that isn't safe considering they're all the same files from different threads (that are safe) except for the script file in the miata fix zip that I made.
mazdamiata210 said:
Well you're not flashing anything that isn't safe considering they're all the same files from different threads (that are safe) except for the script file in the miata fix zip that I made.
Click to expand...
Click to collapse
Yes i understand have used the Evilpotato mans process. I was reffering to the miata Fix. Just want to know what we are flashing. I am not a dev i dont know how to look at a file and see if it will work/harm a phone.
the2rrell said:
Yes i understand have used the Evilpotato mans process. I was reffering to the miata Fix. Just want to know what we are flashing. I am not a dev i dont know how to look at a file and see if it will work/harm a phone.
Click to expand...
Click to collapse
It can't harm anything do not worry. If you followed this guide exactly it will work. Worst case scenario is that you will have to start over again. All it does is copy the missing file back onto the phone so it no longer fails at 27% it's a simple 3 line script you can open it in notepad and see what it's doing if you like.
I hope that posting this is not bad form, as I don't mean to sound skeptical of the OP....
Has anyone tried this method and had success?
TeldenW said:
I hope that posting this is not bad form, as I don't mean to sound skeptical of the OP....
Has anyone tried this method and had success?
Click to expand...
Click to collapse
Yes! Me! Lol it's completely safe
This fix is failing. Error appears that the device is not using NB4 update.
mazdamiata210 said:
It can't harm anything do not worry. If you followed this guide exactly it will work. Worst case scenario is that you will have to start over again. All it does is copy the missing file back onto the phone so it no longer fails at 27% it's a simple 3 line script you can open it in notepad and see what it's doing if you like.
Click to expand...
Click to collapse
thats all that i think most people will need to know just add that to the OP. the more info the better. if it will help people with the update then hey people need to be here testing/using this method.
TheChefSLC said:
This fix is failing. Error appears that the device is not using NB4 update.
Click to expand...
Click to collapse
Whoops I forgot to mention to take the ota update for nb4 before continuing! Sorry I'm running on 0 sleep... Try it again and after the mj5 restore update to nb4... then continue from step 2
mazdamiata210 said:
Whoops I forgot to mention to take the ota update for nb4 before continuing! Sorry I'm running on 0 sleep... Try it again and after the mj5 restore update to nb4... then continue from step 2
Click to expand...
Click to collapse
Indeed
after MJ5 restore, I was able to run the RDLV script in order to replace the system file needed, Then I ran the OTA update from recovery for NB4, Upon reboot, I was then able to install the KK update NC2
TheChefSLC said:
Indeed
after MJ5 restore, I was able to run the RDLV script in order to replace the system file needed, Then I ran the OTA update from recovery for NB4, Upon reboot, I was then able to install the KK update NC2
Click to expand...
Click to collapse
How do you run the script?
opsmgr3774 said:
How do you run the script?
Click to expand...
Click to collapse
It is part of the OP, the RDLV.sh file that you copy to the root of the internal storage. This is a script file that will replace the other .sh file on your system partition.
opsmgr3774 said:
How do you run the script?
Click to expand...
Click to collapse
When you finish the mj5 restore and update to nb4... As long as the miata fix files are on your internal memory and you reboot the script will run
mazdamiata210 said:
When you finish the mj5 restore and update to nb4... As long as the miata fix files are on your internal memory and you reboot the script will run
Click to expand...
Click to collapse
Thank you. I had done everything but the nb4 update and it failed so I of course panicked, then noticed TheChefSLC said they "ran" the script and wondered if I had missed a step. It's all squared away and fully updated now. It worked. Hooray.
This deserves a news page recommendation
Sent from my SAMSUNG-SM-N900A using XDA Premium 4 mobile app
I am getting a temporary error when trying to download the miata_kitkat fix. new link please
EDIT...It is working now. THanks
I can confirm this works. I just did it and I am now on 4.4.2 NC2. Thanks!!
This worked for me...
But I did have to use "(Option B) - Doesn't wipe phone", Option A did not work.
Now to wait for root...
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Setup, Preparation and Prerequisites
I know there are already a few root guides out there for this phone, but I found that they weren't very detailed. This guide is thorough and explains each and every step in a noob-proof manner.
Basic tasks that I may refer to throughout this guide:
Open command prompt - Press Window Key + R, type in "cmd" (without the quotes), and hit enter.
Enter fastboot mode- Turn the phone off. Hold volume up + power until the "fastboot" screen appears.
ADB and Fastboot Installation
Download the full Android SDK here (scroll to the bottom of the page>DOWNLOAD FOR OTHER PLATFORMS>SDK Tools Only) or get a slimmed version containing only the essential components here
Extract the zip and place the android-sdk-windows folder on your desktop.
**If you chose to download the slimmed sdk skip to step 5**
Only if you downloaded the full sdk: Go into the android-sdk-windows folder and run SDK Manager.exe. Install the following packages (there are a total of 4 packages):
- Tools > Android SDK Tools, Android SDK Platform-tools
- Extras > Android Support Library, Google USB Driver
Only if you downloaded the full sdk: Go back into the android-sdk-windows directory, and you should see a new folder named platform-tools. If you don't see this new folder, repeat the step above.
To confirm that it is indeed working, open a command prompt window and enter the following commands:
Code:
cd Desktop/android-sdk-windows/platform-tools
adb version
If it displays "Android Debug Bridge version x.x.xx" it is working. If it is gives an error saying that adb is not a recognized command, it has not been successful. Carefully repeat the steps above if this is the case. Close the command prompt window when you are done.
Show File Extensions - Open a command prompt window and run "Control folders" (without the quotes). Go to the View tab and uncheck the "Hide extensions for known file types" option. This will help avoid confusion when renaming files.
Battery - Ensure that your phone has at least 60% battery remaining, and that your PC is plugged in and wont shut down spontaneously during the process. The procedure doesn't take very long (5-15 minutes), but its best to have enough charge in case something goes wrong.
Backup (Optional) - Unlocking the bootloader will completely wipe all data from the device. This includes apps, settings and even the contents of the internal sdcard (pictures, music, etc.). Copy all important files off the phone onto a PC or upload them to a cloud.
Driver Installation - Download and install the Universal ADB Driver. Alternatively, use this method.
Downloads
Download a custom recovery and the SuperSU zip below. Place both files (recovery image and root zip) in the platform-tools folder located on your desktop within the android-sdk-windows folder.
Custom Recovery:
TeamWin Recovery Project (TWRP)
Root:
SuperSU
Information
Rooting this device is actually quite a simple and easy process. Before you begin, it is recommended that you at least try to understand what each part of the process will do. Although this guide will elongate each step in order to show all of the details, the method used can be broken up into 3 main steps: Unlocking the Bootloader, Installing a Custom Recovery and finally Rooting. Each new step relies on the previous step to have been completed, and a basic summary of each part is:
Unlocking Bootloader: Opens the door to the internal memory of the device to be written on to. This allows you to flash images onto the main partitions of the phone.
Installing a Custom Recovery: A custom recovery is flashed onto the recovery partition of the device and overwrites the stock recovery that exists by default. Custom recoveries bring lots of functionality and give you the ability to perform wipes, install flashable zips, create full backups of your NAND (Nandroid backup), and various other features. An unlocked bootloader is needed to install a custom recovery.
Rooting: You can gain root by either flashing via recovery a pre-rooted custom rom, or flashing a zip containing the SuperSU binaries. A custom recovery is necessary to do this.
After completing these steps your phone will be rooted, the phone will have a custom recovery installed, and the phones bootloader will be unlocked. This, in my opinion, is the most practical and beneficial method for rooting your phone. It gives you some basic adb/fastboot knowledge, and should hopefully help you have a decent understanding of what is going on. Also this method will work regardless of what android version your phone has.
If you are confused by anything in this guide, I would highly suggest getting it clarified being before moving on. Ask your question in this thread and I or someone else will likely answer. Also I'd suggest that you read over the whole thread a few times before actually doing anything to the phone.
Understand? Good...lets begin:
1. Unlocking Bootloader
Turn the phone off. Then boot it into fastboot mode by holding volume up + power. The phone will display "fastboot" text indicating that it has successfully entered fastboot mode.
Plug the phone into your PC, then open a command prompt window and type:
Code:
cd Desktop/android-sdk-windows/platform-tools
Code:
fastboot devices
This command will list the connected devices. If your phones serial number shows up you are good to go and may continue. If the phone is NOT listed this indicates that your drivers are not installed correctly. In order for you to continue you must fix your drivers so that your phone is listed under fastboot devices.
If the phone has been recognized by the command above, proceed to unlocking the bootloader with the following command:
Remember that this step will wipe EVERYTHING off the phone
Code:
fastboot oem unlock
After the above command has finished excuting, run the following
Code:
fastboot reboot
The phone will reboot. Wait until the phone has fully booted up into android, then adjust the following settings on the phone:
USB Debugging - On your phone go to Settings > About phone > Tap on Build number 7 times. This will enable Developer options. Now go back to Settings > Developer options > Enable USB debugging
Disable CM Recovery Protection - On your phone go to Settings > Developer options. Then disable the 'Update recovery with system updates' option.
Close the command prompt window and proceed onto the next section of the guide.
2. Installing a Custom Recovery
Turn the phone off. Then boot it into fastboot mode by holding volume up + power.
Rename the recovery file that you downloaded above to recovery.img. *Make sure that you rename it to recovery.img NOT recovery.img.img* Remember that this file should be placed in the platform-tools folder inside of the android-sdk-windows folder on your desktop.
Open a new command prompt and run the following commands:
Code:
cd Desktop/android-sdk-windows/platform-tools
Code:
fastboot flash recovery recovery.img
Once the flash has completed type the following command to reboot the phone:
Code:
fastboot reboot
After the phone has booted back up, turn it off. Now to enter your newly installed custom recovery, hold volume down + power. The phone should boot into recovery mode. Now that you have a custom recovery, you may continue to the final step.
Close the command prompt window.
3. Rooting
Now that your phone has an unlocked bootloader and a custom recovery installed you have a two options to gain root (Pick one or the other. You don't need to do both)
Option A) Flash SuperSU binaries which will give you root with the stock ROM
Confirm that you have downloaded the SuperSU zip from the downloads section above and that it is located in the platform-tools folder inside of the android-sdk-windows folder on your desktop.
Turn the phone off then boot into recovery mode by holding volume down + power. Leave the phone at the main screen of the custom recovery for now.
Open a command prompt window and run the following commands:
Code:
cd Desktop/android-sdk-windows/platform-tools
Code:
adb push UPDATE-SuperSU-v[COLOR="Red"]X[/COLOR].[COLOR="red"]XX[/COLOR].zip /sdcard/
This will copy the SuperSU zip onto your phone. Once the command has completed continue.
Instructions for TeamWin Recovery Project (TWRP):
Install > browse to SuperSU zip and select the it
Swipe to confirm the installation. Then reboot.
Instructions for ClockworkMod (CWM):
install zip from sdcard > choose zip from sdcard.
Next, browse to the location where you previously copied the SuperSU zip and select the it.
To confirm the installation, scroll down to "Yes" and select it. The installation shouldn't take very long, and once it has completed you may reboot.
Option B) Flash a custom rom which will come pre-rooted
Note that not all custom roms will be pre rooted, however the majority of them are. Read the OP of the ROM thread to see what the verdict is.
Copy a custom rom (you can find these in the ONE Android Development and ONE Original Android Development section) onto the phone (remember the location of where you copy it to)
Turn the phone off then boot into recovery mode by holding volume down + power. To install a custom ROM the general procedure to follow is: factory reset, wipe cache + dalvik cache, flash ROM, flash GApps. Here are the recovery specific instructions:
Instructions for TeamWin Recovery Project (TWRP):
Wipe > Swipe to Factory Reset
Install > browse to the location where you previously copied the ROM zip and select it > Swipe to confirm the installation
Install GApps using same process as ROM, then reboot.
Instructions for ClockworkMod (CWM):
wipe data/factory reset
wipe cache partition
advanced > wipe dalvik cache
install zip from sdcard > choose zip from sdcard > navigate to the location of the ROM > select the ROM > confirm the installation by selecting "Yes"
After that you may install the GApps using the same method for flashing the ROM, and finally reboot the phone.
Keep in mind that the first boot after installing a custom ROM & wiping the phone may take longer than usual, as the phone will need to rebuild the dalvik cache and initialize other first boot stuff.
Congrats! That is all! Your phone now has an unlocked bootloader, a custom recovery installed and is rooted. Enjoy
Reserved.
Thanks Dude For making this Helpful... Sure it will help us with our one plus one..........
Nice guide!!
Sent from Mallorca to your face
Great guide! Will definitely follow when my OPO arrives! :victory:
Thanks a lot for the thread sir ! Btw have some problems I m running and old XP and seems the commands don't work for me .. Would you show me a pics of your root folder on your desktop for the sdk please ?
And I have kies installed before .. Maybe drivers aren't working together ?
pro castinato said:
Thanks a lot for the thread sir ! Btw have some problems I m running and old XP and seems the commands don't work for me .. Would you show me a pics of your root folder on your desktop for the sdk please ?
And I have kies installed before .. Maybe drivers aren't working together ?
Click to expand...
Click to collapse
What do you mean the commands don't work? Could you explain if you are getting an error, what the error is, etc.
Chromium said:
What do you mean the commands don't work? Could you explain if you are getting an error, what the error is, etc.
Click to expand...
Click to collapse
Hum , so I will try to translate my commands from French lol
First I try to install 15 seconds adb installer and failed . Told me all files already copied and "stex" is missing .
After I install the sdk as you said , I put the folder on my desktop and try to get adb worked with the test entry . But my command said that there is a invalid way
pro castinato said:
Hum , so I will try to translate my commands from French lol
First I try to install 15 seconds adb installer and failed . Told me all files already copied and "stex" is missing .
After I install the sdk as you said , I put the folder on my desktop and try to get adb worked with the test entry . But my command said that there is a invalid way
Click to expand...
Click to collapse
Could you post a screenshot of the command prompt output? Thanks.
Chromium said:
Could you post a screenshot of the command prompt output? Thanks.
Click to expand...
Click to collapse
Yeah of course man , let me an hour I will show you all with pics . Thanks a lot again for helping us and for the thread sir ! I just received my One 64GB official this morning . Damn I love CM11S and this beast don't leave my hand since this morning ahah . Hope your like yours too ...
Can't wait for great PA , Carbon , Omni roms on dat crazy phone
pro castinato said:
Yeah of course man , let me an hour I will show you all with pics . Thanks a lot again for helping us and for the thread sir ! I just received my One 64GB official this morning . Damn I love CM11S and this beast don't leave my hand since this morning ahah . Hope your like yours too ...
Can't wait for great PA , Carbon , Omni roms on dat crazy phone
Click to expand...
Click to collapse
Nice, you're lucky I dont even have the phone yet...hopefully I can get my hands on it in the next couple of weeks or so, otherwise I'll probably have to go with a Nexus 5. Once you've installed a custom recovery check out my SlimRom build. I'm also planning on compiling Carbon, but first I'd like to make sure that Slim is functioning properly.
Chromium said:
Nice, you're lucky I dont even have the phone yet...hopefully I can get my hands on it in the next couple of weeks or so, otherwise I'll probably have to go with a Nexus 5. Once you've installed a custom recovery check out my SlimRom build. I'm also planning on compiling Carbon, but first I'd like to make sure that Slim is functioning properly.
Click to expand...
Click to collapse
Awesome man! Thanks for the help and ports ! If you need I should get like 3 invites this week or less so if you need one let me know , give me your mail address and I will send one your way to thank you
Hey man so here is the problem . I can recognize my One with adb , but can't fasboot after on my mac ...
Here are the commands :
macbook:android NikonografferZ$ ./adb devices
List of devices attached
51cf713e device
macbook:android NikonografferZ$ fasboot devices
-bash: fasboot: command not found
macbook:android NikonografferZ$
And if I plug my phone in Fastboot mode from start on my mac he don't recognize it ..
pro castinato said:
Hey man so here is the problem . I can recognize my One with adb , but can't fasboot after on my mac ...
Here are the commands :
macbook:android NikonografferZ$ ./adb devices
List of devices attached
51cf713e device
macbook:android NikonografferZ$ fasboot devices
-bash: fasboot: command not found
macbook:android NikonografferZ$
And if I plug my phone in Fastboot mode from start on my mac he don't recognize it ..
Click to expand...
Click to collapse
>macbook:android NikonografferZ$ fasboot devices
>fasboot
pro castinato said:
Hey man so here is the problem . I can recognize my One with adb , but can't fasboot after on my mac ...
Here are the commands :
macbook:android NikonografferZ$ ./adb devices
List of devices attached
51cf713e device
macbook:android NikonografferZ$ fasboot devices
-bash: fasboot: command not found
macbook:android NikonografferZ$
And if I plug my phone in Fastboot mode from start on my mac he don't recognize it ..
Click to expand...
Click to collapse
You are missing the "t" in fastboot. You wrote "fasboot", but it should be "fastboot". If that doesnt work, try adding the ./ prefix. ie: "./fastboot devices".
Chromium said:
You are missing the "t" in fastboot. You wrote "fasboot", but it should be "fastboot". If that doesnt work, try adding the ./ prefix. ie: "./fastboot devices".
Click to expand...
Click to collapse
Man I win i Unlock Bootloader and I flash TWRP but is it normal when I restart in recovery I still have the Cyanogen Simple Recovery ?? Damn .....
EDITED !!!! FINALLY ROOTED MY ONE PLUS ONE !!!!!!! Finally read read read 18536 threads and I win ahahha
pro castinato said:
Man I win i Unlock Bootloader and I flash TWRP but is it normal when I restart in recovery I still have the Cyanogen Simple Recovery ?? Damn .....
Click to expand...
Click to collapse
Open settings > developer options. Then look for an option that says 'Update recovery with system updates' and disable it.
Thank you for this guide, it was very easy to follow. I am now rooted and ready to spice this phone up
Sent from my One using Tapatalk
pro castinato said:
l
EDITED !!!! FINALLY ROOTED MY ONE PLUS ONE !!!!!!! Finally read read read 18536 threads and I win ahahha
Click to expand...
Click to collapse
Haha, nice. What got it to finally work?
Sent from my HTC Desire using XDA Free mobile app
Chromium said:
Haha, nice. What got it to finally work?
Sent from my HTC Desire using XDA Free mobile app
Click to expand...
Click to collapse
Some problems with the T of fastboot lol nope some drivers weird to install .. I needed to install driver even for fastbooted device with Pda.net app who work really fine !! I really thanks the pdanet software <3
*******************************
Last Update: 25. 5. 2016 * there was a typo in a command :/
*******************************
Hello everyone!
Are you lacking Y OTG cable, but still want to boot other OSes?
Do you want to choose which OS to use on the go?
Then continue reading.
\......../
....\/.... This is just for me176c/x. It might work on other tablets,
....O.... but I'm not responsible for you trying it.
What works:
touchscreen
WiFi
[*]Internal memory
more
And what does not:
sound
Bluetooth
GPS
sensors
charging (not sure if it works, but it doesn't display :/ )
backlight controll
YOU tell me
Prerequisities:
the tablet with UEFI (android 5.0+ on this device)
microsd card (faster is better) with Ext4 filesystem (can still be mounted manualy in Android)
(optional) Y OTG cable for peripherals
internet connection to download 900MB archive
keyboard now included
(optional) a boot selector to choose system at boot (twrp can be used to boot Lubuntu otherwise)
Step 1.
download ****UPDATED ARCHIVE (onscreeen keyboard, should be extract-able) ***** http://www.mediafire.com/download/nse5sju1n31zr56/microsd.tar.gz
unpack it in the root of your microsd
Step 2.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
download grub+cfg+kernel+initramfs archive
[*]add mmc_block.perdev_minors=20 to cmdline in grub.cfg make internal memory work
using root browser, move the Lubuntu folder (with kernel etc. within) to the root of data partition (/data)
mount ESP partition on /sdcard/ESP (data/ESP if you want)
create a folder called ubuntu and move grub AND grub.cfg inside
move the ubuntu folder to /EFI/ folder in ESP (sdcard/ESP/EFI or data/ESP/EFI) (alongside Intel and BOOT folders)
umount ESP
Step 3.
download efibootmgr: http://forum.xda-developers.com/showpost.php?p=62429430&postcount=2740
from a folder with efibootmgr (move it to system so you can add execute permission) run this:
!!!!!!!!There was a typo in command below. The /p was supposed to be -p!!!!!!!!!!!!!!
Code:
./efibootmgr64 -c -d /dev/block/mmcblk0 -p 3 -l \\EFI\\ubuntu\\grubx64.efi -L ubuntu
then look if it worked:
Code:
./efibootmgr64 -v
now, if you completed my previous tutorial, this option will be 0x003, otherwise 0x0000.
now, use
Code:
./efibootmgr64 -o 0001,0000
if you only have these two options or
Code:
./efibootmgr64 -o 0001,0000,0003
if you already have refind as 0x0000
Press the start button!
Now, to try it, use
Code:
./efibootmgr64 -n 0000
to set it just for next power up and press power off, then power the tablet on.
----------------------------------------------------------------------------
Start from TWRP
If everything works well, use
Code:
./efibootmgr64 -n 0000
from TWRP terminal, then power off and power on, everytime you want to start Lubuntu without starting android first
If you try it, make sure to post if it worked And if it did not, then post what happened and I will try to help you.
If you want to PM me about this, rather make a post here. I will probably reply soon (or someone else may help you
Downloading files, gonna try this now, thanks for the tutorial, and in the future will there be more OS'es?
Ruben Craveiro said:
Downloading files, gonna try this now, thanks for the tutorial, and in the future will there be more OS'es?
Click to expand...
Click to collapse
I'll see if people like this
Is there some OS you would like to see and why?
Mis012 said:
I'll see if people like this
Is there some OS you would like to see and why?
Click to expand...
Click to collapse
winxp, maybe, and also i made a step wrong and it only boots to grub... i have a powered hub, how to fix?
Ruben Craveiro said:
winxp, maybe, and also i made a step wrong and it only boots to grub... i have a powered hub, how to fix?
Click to expand...
Click to collapse
Cannot you just redo the step?
Of course it's important what did you do wrong?
I am pretty sure WinXP - although I already thought of that - cannot be booted in EFI mode. And also even Lubuntu is lagging a bit becouse the sdcard is not fast enough. Puppy linux would be way better also for healthiness, but multiple things didn't work. I think I could boot Lubuntu from iso, but then it wouldn't be permanent :/
Also onboard keyboard works well, but I don't want to upload the rootfs again, hopefully it can be installed without keyboard.
P.S I'm gonna make some pictures of it so everybody can see
Mis012 said:
Cannot you just redo the step?
Of course it's important what did you do wrong?
Click to expand...
Click to collapse
i set grub to boot first and i havent setup ubuntu well so it keeps booting to grub and tries to boot to ubuntu but it cant, is there a command in grub to remake boot entrys?
Ruben Craveiro said:
i set grub to boot first and i havent setup ubuntu well so it keeps booting to grub and tries to boot to ubuntu but it cant, is there a command in grub to remake boot entrys?
Click to expand...
Click to collapse
Although it would be a nice adventure, I refuse to tortue you.
Just spam F2 when you power the tablet on, if you press it while in Aptio Setup Utility just select NO, And in Aptio Setup Utility you will quickly find out what to do.
P:S !!!!!!!!!!!!!!!!!!!!!!!! If you didn't have an Y OTG cable you would be screwed hard..
Mis012 said:
Although it would be a nice adventure, I refuse to tortue you.
Just spam F2 when you power the tablet on, if you press it while in Aptio Setup Utility just select NO, And in Aptio Setup Utility you will quickly find out what to do.
P:S !!!!!!!!!!!!!!!!!!!!!!!! If you didn't have an Y OTG cable you would be screwed hard..
Click to expand...
Click to collapse
xD glad i had one, fixed, ill remake the steps, but they are a bit confusing on step2, and thanks
Ruben Craveiro said:
xD glad i had one, fixed, ill remake the steps, but they are a bit confusing on step2, and thanks
Click to expand...
Click to collapse
You can actually make the esp folder on /data/ESP , too. I will edit it
Mis012 said:
You can actually make the esp folder on /data/ESP , too. I will edit it
Click to expand...
Click to collapse
you made some steps weird because they look like some of them are in the images and some on the page, its confusing, i could get to grub and it said Lubuntu in boot order but it starts loading and goes to black screen whats missing?
Ruben Craveiro said:
you made some steps weird because they look like some of them are in the images and some on the page, its confusing, i could get to grub and it said Lubuntu in boot order but it starts loading and goes to black screen whats missing?
Click to expand...
Click to collapse
You have to power off then power on, not reboot. It's that simple, actually
Mis012 said:
You have to power off then power on, not reboot. It's that simple, actually
Click to expand...
Click to collapse
I know that... My only problem is where do i put the ubuntu OS, and if i need to extract..
Ruben Craveiro said:
I know that... My only problem is where do i put the ubuntu OS, and if i need to extract..
Click to expand...
Click to collapse
You extract it in the root of MicroSD.
Some pictures of it working:
The screen is actually nice-looking, the stripes are from camera (slow shutter?)
Mis012 said:
Some pictures of it working:
The screen is actually nice-looking, the stripes are from camera (slow shutter?)
Click to expand...
Click to collapse
i have a problem, each time i try extracting rootfs it gets stuck at gdebi.png (21%)...
As for an OS, I'd like to see Arch. I want to choose what's on my distribution, instead of going for Lubuntu, so I can make it as light weight as possible. I'm thinking a lightweight window manager like i3wm would do a lot of good.
Sent from my K013 using XDA Labs
jerbear294 said:
As for an OS, I'd like to see Arch. I want to choose what's on my distribution, instead of going for Lubuntu, so I can make it as light weight as possible. I'm thinking a lightweight window manager like i3wm would do a lot of good.
Sent from my K013 using XDA Labs
Click to expand...
Click to collapse
You can get it on flash disk and try it
Ruben Craveiro said:
i have a problem, each time i try extracting rootfs it gets stuck at gdebi.png (21%)...
Click to expand...
Click to collapse
Are you extracting using tar utility on linux?
Does it say anything specific about the problem?
Mis012 said:
Are you extracting using tar utility on linux?
Does it say anything specific about the problem?
Click to expand...
Click to collapse
Ive tried extracting on the tablet, using root browser and ZArchiver they both get stuck at same file
Ruben Craveiro said:
Ive tried extracting on the tablet, using root browser and ZArchiver they both get stuck at same file
Click to expand...
Click to collapse
I'm pretty mad at zArchiver for cutting of the top of every file extracted from iso.. Try using tar in terminal on tablet and see what it does. If you have an Y otg cable you can also do install it from a usb stick, abd then try if your rootfs unpacks well and eventually upload it. This tutorial was meant to be useful for people withrout y otg, too, but if you have one it's not that hard to install it yourself.
Press f2 while booting, choose flash drive , select install, custom mode, just select sdcard as rootfs (no data partition doesn't work) and install. Then grep dmesg for a missing txt file for wifi and use /system/etc/nvram.txt in it's place. Be aware it might rewrite your grub.cfg