Related
So, this is what has happened so far:
I googled for a small and easy to follow guide to unlock my phone so that I can later on install a custom rom. I followed the steps provided here:
http://nexusshacks.com/nexus-s-hacks/how-to-root-nexus-s/
What I didn't notice on the first place was the "UPDATE: DO NOT FOLLOW THIS GUIDE INSTEAD Please see new root method which works on all Nexus S and Nexus S 4G!" link. Don't ask why - really don't know.
The result was having my Nexus S stuck on a screen that shows Google logo on the middle and an unlocked padlock on the bottom.
It seemed, or to be exact, I figured out that, the problem was the .img file mentioned on some point in the middle of this.. tutorial.
So, I decided to follow the newer guide that can be found here:
http://nexusshacks.com/nexus-s-hacks/how-to-root-nexus-s-or-nexus-s-4g-new/
Although all went well (didn't have to go all over the same processes up to the .img installatin point), I ended up with the same screen that shows Google logo on the middle and an unlocked padlock on the bottom.
I figured out that I could just install a rom at this point, and decided that I should go back to stock. So, I followed this guide here:
http://nexusshacks.com/nexus-s-hacks/how-to-unroot-nexus-s-i9020ti9020ai9023/
But, when I choose to install the .zip file, I get this error:
assert failed: "getprop ("ro.product.device") == "crespo" || "getprop ("ro.product.device") == "crespo"
E: Error in /sdcard/i9020t_i9023.zip
(status 7)
Installation aborded
..let me add to this point that I have bought my Nexus S from EU, it is an i9023. Let me also add that all I wanted is to flash an ICS rom and I think I have ended with a f****d device I don't know what to do with!
Any help, really, would be so much appreciated since I need to use this phone. I have a backup for calls etc but I need some smartphone features!
I seriously doubt you killed your Nexus S. Temporarily disabled is more like it.
From off position, hold down Power + VOL-UP. You should be greeted with a screen with a green android and 4 options. If you can get there, that's the bootloader, and unless you manage to kill it (which is VERY hard to do), you can reflash everything from there via usb and adb.
What model Nexus S do you have? That's important for helping you to flash it.
nickmv said:
I seriously doubt you killed your Nexus S. Temporarily disabled is more like it.
From off position, hold down Power + VOL-UP. You should be greeted with a screen with a green android and 4 options. If you can get there, that's the bootloader, and unless you manage to kill it (which is VERY hard to do), you can reflash everything from there via usb and adb.
What model Nexus S do you have? That's important for helping you to flash it.
Click to expand...
Click to collapse
Yes, I can enter this menu - there already. My model is an i9023GSM.
OK, then you DONT have a dead phone. You just need to reflash it correctly.
I'm sorry I can't be helpful for longer, because I am at work,but follow this guide and make sure you follow every detail (take note of step 6 in particular).
I know it's a long guide, but it's VERY detailed, and should get you up and running.
On a side note, for ROM selection, are you looking for an Ice Cream Sandwich alpha ROM (android 4.0) (less stable) or the older Gingerbread ROMs (2.3.7)?
nickmv said:
OK, then you DONT have a dead phone. You just need to reflash it correctly.
I'm sorry I can't be helpful for longer, because I am at work,but follow this guide and make sure you follow every detail (take note of step 6 in particular).
I know it's a long guide, but it's VERY detailed, and should get you up and running.
On a side note, for ROM selection, are you looking for an Ice Cream Sandwich alpha ROM (android 4.0) (less stable) or the older Gingerbread ROMs (2.3.7)?
Click to expand...
Click to collapse
You gave me the good news so, thank you for that. Now, I should follow this guide and come back in case I have a problem.
As far as the rom, I wanted to flash an ICS since I cannot wait any longer for Google to release the official update. But right now, anything that can get my device up and running would be really good!
Edit: nvm. >_<
kijp15 said:
Why don't you just use shabby's one click root. Simple & much easier. Saves all sorts of troubles.
Click to expand...
Click to collapse
Will this solve the problem I'm facing? If yes, then it's fine by me.
Ok, just saw the edit, no worries!
nickmv said:
but follow this guide and make sure you follow every detail (take note of step 6 in particular).
I know it's a long guide, but it's VERY detailed, and should get you up and running.
Click to expand...
Click to collapse
OK, stuck already. On Part 2 what I understand is that I have to open the CMD and copy-paste the path to the "tools" folder? Because this is what I do, and after - since this is what I have understand - I type "fastboot oem unlock" and I get "'fastboot' is not recognized as an internal or external command,
operable program or batch file."
What do I do wrong?
EDIT:
Tottaly stuck on Part 2. It seems that there is no fastboot.exe file inside "tools" folder. I don't think the problem is something else - I'm sure I give the right commands since I tryied for fun another folder I have with fastboot.exe inside and it worked - to be exact it just gave me a FAILED messsage since device is already unlocked. Plus, regarding Part 3, Step 1, the first file for download is missing so I used the second link and downloaded 5023-cyan file. Hope this was a right move to do.
EDIT 2:
Ok, here is the story so far: I followed the guide given step by step. The USB drivers has been installed correctly so the device can be connected to the PC.
In the "tools" folder there was no such fastboot.exe file so I manually added one that I've found on the newer guide given on the 1st post. The unlocking process is failing because the device is already unlocked.
I did manage to install after this, the 5023-cyan.img file since this is the only link working from Part 3, Step 1. This gone well too!
Now, I couldn't go on with Part 4, I mean, I could not install the .zip file as it describes so through recovery mode I installed the .zip file succesfully (confirmation message to Nexus S screen).
I reboot and still get the same Google logo on the middle and an unlocked padlock on the bottom.
I cannot understand what I do so wrong? Oh, I'm so disappointed..
OK, people, head's up! I did manage to install the latest stable rom of cyanogenmod and the phone is up and running! It means that somehow everything went well! Now, how do I return back to OEM? Because I just need to make things as they where before..
..or should I give cyanogenmod a chance?
http://forum.xda-developers.com/showthread.php?t=1063664 or use ROM manager and select Stock ROM (you should then receive OTA upgrades to 2.3.6).
On the latter: You colud just back up different ROMs and switch between them using CW.
skatastamoutrasas said:
Will this solve the problem I'm facing? If yes, then it's fine by me.
Ok, just saw the edit, no worries!
Click to expand...
Click to collapse
If you are still facing problems. Try locking your bootloader again with this method. Then it will let you go back on stock. Use v3 it is stable solid and easy to use.
Nexus S + CM9 kangs = Awesomeness
mixtapes08 said:
If you are still facing problems. Try locking your bootloader again with this method. Then it will let you go back on stock. Use v3 it is stable solid and easy to use.
Nexus S + CM9 kangs = Awesomeness
Click to expand...
Click to collapse
Can you give me a CM9 kangs link since as new here, I'm kinda lost?
Ok new problem this time! After I installed my 3rd rom (probably, a totall noob thing to do) which was the OEM one, I tryied to re-enter recovery mode to wipe all data and re-install the rom I want. But now I get this mark of the small green android with a big exclamation mark on top of his head. What is this new hell that found me?
skatastamoutrasas said:
Ok new problem this time! After I installed my 3rd rom (probably, a totall noob thing to do) which was the OEM one, I tryied to re-enter recovery mode to wipe all data and re-install the rom I want. But now I get this mark of the small green android with a big exclamation mark on top of his head. What is this new hell that found me?
Click to expand...
Click to collapse
Try re-flashing the recovery. Either threw rom manager or fastboot.
Fastboot flash recovery "nameofrecovery".img
kijp15 said:
Try re-flashing the recovery. Either threw rom manager or fastboot.
Fastboot flash recovery "nameofrecovery".img
Click to expand...
Click to collapse
Worked just fine! Thank you!
skatastamoutrasas said:
OK, people, head's up! I did manage to install the latest stable rom of cyanogenmod and the phone is up and running! It means that somehow everything went well! Now, how do I return back to OEM? Because I just need to make things as they where before..
..or should I give cyanogenmod a chance?
Click to expand...
Click to collapse
Nice, glad to see you managed to get it working. Honestly, the hassle is kind of worth it, because you learn more about the process anyways.
That being said, give CyanogenMod a chance. There's also several other ROMs. Unless you need stock OS for warranty service, I'd recommend going with one of the many custom ROMs we have here.
There are several minimalistic AOSP-built ROMs that mimic the feel of the stock OS, but are optimized for speed, and still have some very nice tweaks that you may enjoy. Just take a look through the dev section, and you'll see we have tons of options.
nickmv said:
Nice, glad to see you managed to get it working. Honestly, the hassle is kind of worth it, because you learn more about the process anyways.
That being said, give CyanogenMod a chance. There's also several other ROMs. Unless you need stock OS for warranty service, I'd recommend going with one of the many custom ROMs we have here.
There are several minimalistic AOSP-built ROMs that mimic the feel of the stock OS, but are optimized for speed, and still have some very nice tweaks that you may enjoy. Just take a look through the dev section, and you'll see we have tons of options.
Click to expand...
Click to collapse
It did worth the hassle, that's for sure. Now I think it's so easy to unlock a Nexus plus I now have a little more knowledge regarding Android .
I will stick with CM 2.3.7 as it looks just fine. I don't care about warranty, I don't think I will ever need the official service for a software issue. Now I have to re-install my apps, re-sync my accounts and setup the phone the way I want it. It will take a little more time.
But I'm glad that I pulled this through - with your help of course! Guys, you rock!
I wish that I'll be as helpful as you at the near future.
Today's latest CM9/ICS kang is here
I'd also recommend getting a custom kernel.
For batt life, morfic's SEUV kernel.
For reg performance, perhaps Matrix's kernel
MAKE SURE THAT YOU HAVE CLOCKWORKMOD PERMANENTLY INSTALLED BEFORE DOING THIS. It saves time if you mess up. Also, make sure you get the latest gapps HERE
Instructions:
1. Go to clockwork recovery
2. Select data/factory reset/wipe
3. Select clear cache as well
4. Adv Mounts and Storage > wipe /system (note, this wipes android off the phone. It's a good idea since youre going from ver 2.x to 4.x)
5. Choose "flash from zip" (or whatever it's called.....NOT flash from update.zip)
6. Flash the cm9 update file first, then flash the kernel of your choice, then flash the gapps file.
7. Back out of the menu and select reboot.
Take note though, that the new ICS OS has incompatibilities with certain apps while GPU rendering is turned on, etc. It'll prob reboot on you sometimes, etc. For the most part it's stable, but that's completely subjective.
If you do run ICS, make sure you turn on GPU rendering in Dev Options. It takes full advantage of the GPU for UI animations, etc. Sometimes there's a stray app here and there that doesnt play nice, and you'll notice if the window looks really tiny or funny. Turning it off will fix the problem.
nickmv said:
Today's latest CM9/ICS kang is here
I'd also recommend getting a custom kernel.
For batt life, morfic's SEUV kernel.
For reg performance, perhaps Matrix's kernel
Click to expand...
Click to collapse
Two questions:
The link you give me to download the ICS rom keeps loading for ever. So, I choosed this one instead:
http://forum.xda-developers.com/showthread.php?t=1356228
Right or wrong thing to do?
It it essential to install a custom kernel? I ask because I forgot to copy/paste the .zip file and due to lack of time, I procceded without it, installing the ROM and G-APPS.
Hi i did go to Xperia Developer thread but it said i can only ask questions in General forums.
So here i am i really need help, i rooted my Xperia Arc and almost nothing is working, i can't turn on the Wifi, mobil network works for a second then the phone shuts down mobil netorks, keypad, etc.
When i start my phone i get: unfortunately, the process com.android.phone has stopped, when i try doing something else i get alot of "unfortunately" messages. please help.
I followed every instruction for rooting i have the 2.6.32.9- DooMKernel, almost all apps are gone and the superuser app have 0 apps in it.
Hi zobar,
There are General & Q&A forums for the Xperia Arc and you'll get users there with the same device, whereas this is a general forum for anything to do with any phone, regardless of make/model/os.
Do some reading in both the General & Q&A sections in this forum...
http://forum.xda-developers.com/forumdisplay.php?f=962
If you can't find an answer then start a thread in the Q&A forum, as that's where all questions should be posted. The only place you can't currently post are development forums, but they're only for releasing development work anyway.
Hope you get your problem sorted
Try rebooting
zobar said:
Hi i did go to Xperia Developer thread but it said i can only ask questions in General forums.
So here i am i really need help, i rooted my Xperia Arc and almost nothing is working, i can't turn on the Wifi, mobil network works for a second then the phone shuts down mobil netorks, keypad, etc.
When i start my phone i get: unfortunately, the process com.android.phone has stopped, when i try doing something else i get alot of "unfortunately" messages. please help.
I followed every instruction for rooting i have the 2.6.32.9- DooMKernel, almost all apps are gone and the superuser app have 0 apps in it.
Click to expand...
Click to collapse
Rebooting might help. Or you can restore an old ROM.
TrueXdaNoob said:
Rebooting might help. Or you can restore an old ROM.
Click to expand...
Click to collapse
Hi can you please explain how i can restor an old ROM? i made a thread here: http://forum.xda-developers.com/showthread.php?t=1838479
I rebooted and it's still the same, im sure i installed everything correctly as it all worked as instructed its just the end result im stuck with broken phone sort of, i can see my pictures in the widget picture thingy but there is no internet, no apps, i cant install any widgets as it tells me to install widget app.
Straightforward answer
Before a more experienced member rightfully closes this thread I will try to help you.
Download flashtool. A simple google search will sort that out.
Install it. The program will have a picture of a lightning bolt as its logo.
Find the stock firmware for your device. Search for that in google.
After downloading the firmware you should see it has a .ftf at the end.
Go into computer then flashtool then firmware. then drag and drop the .ftf into that folder.
Close the folder.
connect your arc.
Open the flashtool program.
Click the bolt icon in the top left.
select the name of the firmware you downloaded in the left panel. it will highlight blue.
Click ok (bottom right).
A box will appear telling you to put your device into flash mode. Follow the instructions it gives.
Once this is done the box will dissapear and firmware will flash.
Finally device will reboot and phone will be back to normal.
Hope it works for you. :good: Please thank me with the button if you appreciate my efforts. Please post in more appropriate places in future and someone will answer quicker. Sorry if this isn't what you wanted.
baddaman54 said:
Before a more experienced member rightfully closes this thread I will try to help you.
Download flashtool. A simple google search will sort that out.
Install it. The program will have a picture of a lightning bolt as its logo.
Find the stock firmware for your device. Search for that in google.
After downloading the firmware you should see it has a .ftf at the end.
Go into computer then flashtool then firmware. then drag and drop the .ftf into that folder.
Close the folder.
connect your arc.
Open the flashtool program.
Click the bolt icon in the top left.
select the name of the firmware you downloaded in the left panel. it will highlight blue.
Click ok (bottom right).
A box will appear telling you to put your device into flash mode. Follow the instructions it gives.
Once this is done the box will dissapear and firmware will flash.
Finally device will reboot and phone will be back to normal.
Hope it works for you. :good: Please thank me with the button if you appreciate my efforts. Please post in more appropriate places in future and someone will answer quicker. Sorry if this isn't what you wanted.
Click to expand...
Click to collapse
Thanks alot im going to try it out but, wil that make my phone normal? not root anymore?... if so that kinda sucks, i wish to have a rooted phone.
yes it will make it 'normal'. From there I suggest following a youtube tutorial about rooting properly. This way you will avoid bricking your device again.
baddaman54 said:
yes it will make it 'normal'. From there I suggest following a youtube tutorial about rooting properly. This way you will avoid bricking your device again.
Click to expand...
Click to collapse
DO you have any good new karnels? or any guides please? i followed one and bricked it so maybe the guide i used was bad? :S
-
Did my unbrick guide work? SO your device is ok now? I hope so.
Here is a mini guide about phone terms. Sorry if you know this already.
Rooting is simply giving your phone administrators rights. No roms or anything. Once rooted you could install clockworkmod which would allow you to install a rom that would work on you STOCK kernel (the one that comes with xperia).
A kernel is a set of instructions to a phone. different kernels or custom kernels (not stock) enable you to flash some more advanced roms as not all roms will work on STOCK kernel.
Also, in most cases, different kernels allow overclock and undervolt. These things allow you to make your device run faster.
Unlocking your bootloader is required to install a custom kernel. Unlocking a bootloader can be difficult and if done wrong, can brick your device completely.(make it useless like a brick) This is why I did not do it until a few days ago - because I was scared.
If I was to recommend a rom, I would say cyanogenmod (cm for short). They focus on getting the galaxy nexus android - pure version.
You flash kernels with flashtool. But you MUST have an unlocked bootloader to do this.
If your device is fixed now i would say google cyanogen mod 9(ice cream sandwich) or 10 (jelly bean). CM10 is less stable (not everything works) than cm9. but cm10 is more fun. make sure you look at guides for your device and not any random one.
Sorry for the lecture. Thank if you found this useful. I appreciate it. Sorry if this isn't what you wanted.
---------- Post added at 10:47 PM ---------- Previous post was at 10:45 PM ----------
if you do not understand anything or want to ask anything else please feel free. Also you can check out videos of roms for your device on youtube and choose one you like. then look for tutorials on xda or youtube.
baddaman54 said:
Did my unbrick guide work? SO your device is ok now? I hope so.
Here is a mini guide about phone terms. Sorry if you know this already.
Rooting is simply giving your phone administrators rights. No roms or anything. Once rooted you could install clockworkmod which would allow you to install a rom that would work on you STOCK kernel (the one that comes with xperia).
A kernel is a set of instructions to a phone. different kernels or custom kernels (not stock) enable you to flash some more advanced roms as not all roms will work on STOCK kernel.
Also, in most cases, different kernels allow overclock and undervolt. These things allow you to make your device run faster.
Unlocking your bootloader is required to install a custom kernel. Unlocking a bootloader can be difficult and if done wrong, can brick your device completely.(make it useless like a brick) This is why I did not do it until a few days ago - because I was scared.
If I was to recommend a rom, I would say cyanogenmod (cm for short). They focus on getting the galaxy nexus android - pure version.
You flash kernels with flashtool. But you MUST have an unlocked bootloader to do this.
If your device is fixed now i would say google cyanogen mod 9(ice cream sandwich) or 10 (jelly bean). CM10 is less stable (not everything works) than cm9. but cm10 is more fun. make sure you look at guides for your device and not any random one.
Sorry for the lecture. Thank if you found this useful. I appreciate it. Sorry if this isn't what you wanted.
---------- Post added at 10:47 PM ---------- Previous post was at 10:45 PM ----------
if you do not understand anything or want to ask anything else please feel free. Also you can check out videos of roms for your device on youtube and choose one you like. then look for tutorials on xda or youtube.
Click to expand...
Click to collapse
Hi almost everything worked out in the end just one problem left, the mobile network after rooting it tunring on and off like its droping the signal and after min it regains it, its a constant loop with network off and on.
Try switching on airplane mode and then switching off. This will restart your phone's radio and may fix this. Otherwise I am not sure. Great to hear it all went well
baddaman54 said:
Try switching on airplane mode and then switching off. This will restart your phone's radio and may fix this. Otherwise I am not sure. Great to hear it all went well
Click to expand...
Click to collapse
Somehow insalling he ROM you told me about the c9 fixed my network connection but now this ROM has no Google Play store in it =/ what do i do? i wanted to download youtube.
Thank you so much for all the help just need google play and im all good.
zobar said:
Somehow insalling he ROM you told me about the c9 fixed my network connection but now this ROM has no Google Play store in it =/ what do i do? i wanted to download youtube.
Thank you so much for all the help just need google play and im all good.
Click to expand...
Click to collapse
Try browsing to http://play.google.com from your phone.
mf2112 said:
Try browsing to http://play.google.com from your phone.
Click to expand...
Click to collapse
Thanks everyone for being such undersanding community i finally managed to do everything i wanted, i installed Google play from Gapps: http://goo.im/gapps
Im loving the Cyanogenmod 9, its so cool
Just fyi I think he forgot to wipe data possibly, this can be the cause when the roms are 'half compatible'
Also, it wasn't bricked because it actually turned on
Sent from my ARCHOS 80G9 using Tapatalk 2
Great to hear my friend! need anything, just PM me.
Good to see you offer support
PCD Chaser/ LG Chaser
I can't find a thing on this phone at all and im trying to figure out a way to root my LG Chaser..
nickmahuta said:
I can't find a thing on this phone at all and im trying to figure out a way to root my LG Chaser..
Click to expand...
Click to collapse
Good to hear. Try SuperoneClick. Have to say that I am surprised that this thread wasn't closed.
all good now.
Deftone said:
Good to hear. Try SuperoneClick. Have to say that I am surprised that this thread wasn't closed.
Click to expand...
Click to collapse
I have found a root method now.
you use Poot-debug.apk and Ministro II.apk
Ladies and Gentlemen,
It is my pleasure to present the latest stock Oreo 8.1 (Beta) ROM for Xiaomi Mi A1. Up till now, only a handful of testers were able to use the stock beta 8.1
But now, everyone has the opportunity to use it on their device.
Disclaimer:
If you are planning to flash the ROM on your device, you are on your own. I would not be responsible if anything happens to your device. Your warranty will be void after flashing the ROM. You need to go back to stock stable ROM with a locked bootloader for Warranty.
Requirements:
1. Xiaomi Mi A1 (Ofcourse)
2. A PC (I am using Windows 7 here)
3. The ROM file (Available on the link below)
4. MiFlash Tool ( Link: http://en.miui.com/thread-345974-1-1.html ) (A big thanks to Miui forum for making the tool available on miui forum)
5. ADB Platform tool (Search on google)
6. Patience
Installation Process:
1. Download the ROM file from the given link and unzip it.
2. You will see a folder with name as tissot_images_V9.6.2.0.ODHMIFE_8.1
3. Keep it on C drive
4. Install MiFlash Tool on your PC from the given link
5. Set up ADB driver properly on your PC (It's very important)
6. Now go to your device and enable Developers option by tapping on Build Number 7 times.
6. Open Developers Option and enable "OEM Unlocking" and "USB Debugging" option.
7. Now press and hold the power button and Volume down button for about 10 seconds until you see a small bunny on the screen.
Now connect your device to your PC and open a command box and type fastboot oem unlock
8. Once the bootloader is unlocked, put your device in fastboot mode again and connect it to PC. (BE WARNED!!! if anyone is on May security patch, unlocking bootloader will erase everything from the device and device will restart again. You will need to unlock developers option again and enable "USB debugging" option once more)
9. Now open MiFlash Tool and see if it reads your device serial number by clicking on "Refresh". Now, select tissot_images_V9.6.2.0.ODHMIFE_8.1 and click on "Flash". Make sure you are doing it in a proper way.
10. Wait until you see a "Flash Done" message on the screen. It may take around 5-10 minutes. Once done, your device will boot into system and Congrats! Now you have Oreo 8.1 on your device with June security patch.
N.B. It is best that you select "Clean all and lock" option on MiFlash tool.
Flashing Guide For TWRP & Custom Kernel:
1. Grab the latest twrp recovery image (Oreo) and twrp installer zip file.
2. Put the recovery image in ADB folder and the installer zip in your device.
2. Boot your device into fastboot mode and connect it to the PC.
3. Make sure the bootloader is unlocker.
4. Open a command box and type fastboot boot xxx.img (xxx= recovery image name)
5. Once your device is boot into twrp, flash TWRP installer zip file and reboot back to recovery.
6. Now flash the custom kernel of your choice and Magisk (optional).
7. Reboot back to system.
Important Note:
If anyone has any problem understanding the steps, I would recommend that you google or search on Youtube. There are lots of Videos showing on how to flash stock ROM on MiFlash tool. Please don't blame me if you skip any step or do it wrong. I have shared the standard steps that remain the same for flashing both stable and beta rom. It is advised that you STAY AWAY if you don't know what you are doing. I am certainly not going to take any blame for improper flashing. As you have decided to flash the ROM, I expect you to have a little knowledge about how to use MiFlash tool. A lot of newbees have problem at first, especially when flashing rom on MiFlash tool. That's because of selecting and flashing the rom file in an improper way. You need to first learn exactly which folder to flash or else you will always end up on a bootloop. Please don't blame me for not spoon feeding you.
Bugs Encountered:
I have been using the ROM for two days and I am yet to find any bugs except ctsProfile shows as false and Google Play Store shows Uncertified.
*For better battery life, you can try Void kernel (Choose the stock version).
ROM Download Link:
https://www.androidfilehost.com/?fid=818222786056041186
Credit:
Xiaomi, 4PDA, @topjohnwu for Magisk, @flex1911 for Void kernel, @CosmicDan & @mohancm for their work on TWRP.
Special Note:
I apologize to all for breaking any possible XDA rule and hurting anyone here!! Please note that I am not getting paid for sharing this post here. If anyone still feels something bad, you can either let me know or you can report it to the admin. But again, I am extremely sorry for breaking any rule here.
MiFlash Tool
Screenshots will be added shortly.
Screenshots
Already posted here https://forum.xda-developers.com/showpost.php?p=76813554&postcount=340
And fyi, i already been using this rom for past 2 days, back to AEX coz battery drain is fast, not recommended for daily usage.
exodius48 said:
Already posted here https://forum.xda-developers.com/showpost.php?p=76813554&postcount=340
And fyi, i already been using this rom for past 2 days, back to AEX coz battery drain is fast, not recommended for daily usage.
Click to expand...
Click to collapse
I can confirm battery drain with this rom.
Rowdyy Ronnie said:
Credit:
Xiaomi for allowing me to try their Beta ROM and allowing me to share it on XDA
N.B. Sharing the ROM file anywhere else without my permission will be considered as stealing and will be reported to XDA if found.
Click to expand...
Click to collapse
Did xiaomi give you the permission to share it on xda?
muruu said:
Did xiaomi give you the permission to share it on xda?
Click to expand...
Click to collapse
No, this is leaked beta. He just reshare from displax @ 4pda.ru
after sucessfully flashing using miflash it stucks on andriodone
N1ck474 said:
This update is leaked from weeks, why complaining here and now?
We're getting delayed updates cause Xiaomi is far away from Quick updates (MIUI or Stock, still Xiaomi).
Click to expand...
Click to collapse
Can we root it or when unlock bootloader cause erase all information like may update + is it good for daily use ?
joeniz said:
when unlock bootloader cause erase all information like may update?
Click to expand...
Click to collapse
Why would they remove a security feature they just recently added?
joeniz said:
Can we root it or when unlock bootloader cause erase all information like may update + is it good for daily use ?
Click to expand...
Click to collapse
It doesn't wipe data partition like what was happening on May security patch. And I haven't noticed any bug as of now. Some people said battery life is not that good. I can't comment on that as I use Void kernel.
Seems like a lot of people have some sort of issue with this post. First of all, this is not a custom rom and I didn't build it. So, if there is some sort of bugs on the ROM, that's not my fault. Second, yes I brought the file from somewhere else so that more people can use it. So, what is the problem here? Before you point your finger on me for a bootloop or bad battery life, you should read the disclaimer first. When you decide to do any experiment with your device, you should have a fair amount of knowledge of what you are doing. Before sharing the file on XDA, I flashed and tried it on my device and there was no bootloop or any other issue whatsoever.
dback31 said:
Why would they remove a security feature they just recently added?
Click to expand...
Click to collapse
Cause i found no phone that u can't root !!
---------- Post added at 09:18 PM ---------- Previous post was at 09:15 PM ----------
Rowdyy Ronnie said:
It doesn't wipe data partition like what was happening on May security patch. And I haven't noticed any bug as of now. Some people said battery life is not that good. I can't comment on that as I use Void kernel.
Click to expand...
Click to collapse
What about messenger fb in any rom i use i get animation lag in messenger when message appear things like that and if someone send me message while i using phone the phone animation lag .... Only in fb messenger i found this problem i hate this app .... Anybody have that issue because iam going mad .
Rowdyy Ronnie said:
Seems like a lot of people have some sort of issue with this post. First of all, this is not a custom rom and I didn't build it. So, if there is some sort of bugs on the ROM, that's not my fault. Second, yes I brought the file from somewhere else so that more people can use it. So, what is the problem here? Before you point your finger on me for a bootloop or bad battery life, you should read the disclaimer first. When you decide to do any experiment with your device, you should have a fair amount of knowledge of what you are doing. Before sharing the file on XDA, I flashed and tried it on my device and there was no bootloop or any other issue whatsoever.
Click to expand...
Click to collapse
If you just share a rom build by someone else, this is the wrong section of the forum to post it.
Too, you say (in op) you have permission from xiaomi to post it here in xda. This sounds unusual. Do you have any proof for this claim?
Thread cleaned.
Thread moved to the guides section where shared ROMs belong. The redirect from development section will expire in 24 hours.
:good:
Rowdyy Ronnie said:
N.B. Sharing the ROM file anywhere else without my permission will be considered as stealing and will be reported to XDA if found.
Click to expand...
Click to collapse
hahahah oh wow
the best joke i ever seen
seriously
copyright to leaked build? hahaha i can't stop
Closed beta ROM, so no point in "allowing" you to share it. They could open beta and do it themselves.
I call fake news on that
You share a rom from another forum. Okay. It was already been shared in XDA by the original poster in 4pda.
I call this reposting in the same forum.
You state that the ROM isn't yours and you "share" it with other people on XDA. And then you say reposting is stealing? Didn't you repost it as well? For you is not stealing but for others is?
Conclusion: Are you that desperate for attention?
Is this the official beta rom?
Rowdyy Ronnie said:
Credit:
Xiaomi for allowing me to try their Beta ROM and allowing me to share it on XDA
Click to expand...
Click to collapse
How did you manage to get permission from Xiaomi? Have some proofs?
Xiaomi released July security patch a couple of days back. However, as always, a lot of people didn't receive it yet. But the wait is over. Now everyone can update their device to the latest security patch.
Disclaimer:
If you are planning to flash the ROM on your device, you are on your own. I can not be held responsible if anything happens to your device. Your warranty will be void after unlocking the bootloader. You need to lock the bootloader for any warranty.
Requirements:
1. Xiaomi Mi A1 (Ofcourse)
2. A PC (I am using Windows 7 here)
3. The ROM file (Available on the link below)
4. MiFlash Tool ( Link: http://en.miui.com/thread-345974-1-1.html ) (A big thanks to Miui forum for making the tool available on miui forum)
5. ADB Platform tool (Search on google)
6. Patience
Installation Process:
1. Download the ROM file from the given link and extract it.
2. You will see a folder with name as tissot_images_V9.6.4.0.ODHMIFE_20180712.0000.00_8.0_735823083f
3. Double click on the folder and open it. You will see another folder with name as tissot_images_V9.6.4.0.ODHMIFE_8.0
3. Copy the folder into the C drive. Remember, you need to copy tissot_images_V9.6.4.0.ODHMIFE_8.0 and not the main folder.
4. Install MiFlash Tool on your PC from the given link
5. Set up ADB driver properly on your PC (It's very important)
6. Now go to your device and enable Developers option by tapping on Build Number 7 times.
6. Open Developers Option and enable "OEM Unlocking" and "USB Debugging" option.
7. Now press and hold the power button and Volume down button for about 10 seconds until you see a small bunny on the screen.
Now connect your device to your PC and open a command box and type fastboot oem unlock
8. Once the bootloader is unlocked, put your device in fastboot mode again and connect it to PC. (BE WARNED!!! if anyone is on May security patch, unlocking bootloader will erase everything from the device and device will restart again. You will need to unlock developers option again and enable "USB debugging" option once more)
9. Now open MiFlash Tool and see if it reads your device serial number by clicking on "Refresh". Now, select tissot_images_V9.6.4.0.ODHMIFE_8.0 and click on "Flash". Make sure you are doing it in a proper way.
10. It may take around 10-15 minutes (for me it took around 11 minutes) to get the process completed. Once done, your device will boot into system and Congrats! Now you have Oreo 8.1 on your device with July security patch.
N.B. It is best that you select "Clean all and lock" option on MiFlash tool.
Flashing Guide For TWRP & Custom Kernel:
1. Grab the latest twrp recovery image (Oreo) and twrp installer zip file.
2. Put the recovery image in ADB folder and the installer zip in your device.
2. Boot your device into fastboot mode and connect it to the PC.
3. Make sure the bootloader is unlocker.
4. Open a command box and type fastboot boot xxx.img (xxx= recovery image name)
5. Once your device is boot into twrp, flash TWRP installer zip file and reboot back to recovery.
6. Now flash the custom kernel of your choice and Magisk (optional).
7. Reboot back to system.
Important Note:
If anyone has any problem understanding the steps, I would recommend that you google or search on Youtube. There are lots of Videos showing on how to flash stock ROM on MiFlash tool. Please don't blame me if you skip any step or do it wrong. I have shared the standard steps that remain the same for flashing both stable and beta rom. It is advised that you STAY AWAY if you don't know what you are doing. I am certainly not going to take any blame for improper flashing. As you have decided to flash the ROM, I expect you to have a little knowledge about how to use MiFlash tool. All newbies have a problem at first, especially when flashing ROM on MiFlash tool. That's because of selecting and flashing the ROM file in an improper way. You need to first learn exactly which folder to flash or else you will always end up on a bootloop. Please don't blame me for not spoon feeding you.
Bugs Encountered:
LED notification stays still when a notification comes in. It doesn't blink.
ROM Download Link:
https://www.androidfilehost.com/?fid=5862345805528051162
Credit:
Xiaomi
Special Note:
I apologize to all for breaking any possible XDA rule and hurting anyone here!! Please note that I am not getting paid for sharing this post here. If anyone still feels something bad, you can either let me know or you can report it to the admin. But again, I am extremely sorry for breaking any rule here.
Occupied
Reerved
There is already a thread for stock roms which is alot nicer because everything is compiled by version. Why bother creating another?
barrack1 said:
There is already a thread for stock roms which is alot nicer because everything is compiled by version. Why bother creating another?
Click to expand...
Click to collapse
Basically, looking for attention and thanks.
He has been doing this for every update even though there are other threads that are much better and more organized
He even claimed that he was in the beta program when 8.1 beta was leaked even though he was asking around on where to get beta update.
Rowdy, you should honestly stop making pointless threads that already exist and start being more respectful to other members
In his defense. This link is AFH, while still not wonderful, it is usually SOOOO much faster than the damn MIUI links. (at least in my experience)
berezker said:
Basically, looking for attention and thanks.
He has been doing this for every update even though there are other threads that are much better and more organized
He even claimed that he was in the beta program when 8.1 beta was leaked even though he was asking around on where to get beta update.
Rowdy, you should honestly stop making pointless threads that already exist and start being more respectful to other members
Click to expand...
Click to collapse
Listen, this is the second time I am telling you not to be personal. If you don't like something, report it to the mods. XDA is not your personal property. So, you don't get to judge people here. I checked all the post for July OTA and then I posted it here. The particular post you are talking about, I checked it prior to creatingmine. He didn't have the ROM uploaded when I created my post. It's not my fault that he uploaded the July fastboot ROM without checking mine. I have already asked the mod to check both his and my post to see who uploaded the July fastboot ROM.
barrack1 said:
There is already a thread for stock roms which is alot nicer because everything is compiled by version. Why bother creating another?
Click to expand...
Click to collapse
Are you sure that post has the July fastboot ROM? I checked his post prior to creating one. He didn't have the ROM uploaded. If you see both my and his post, you can see who edited the post later. It was he who posted the July fastboot ROM later. I have already asked the mod to check both his and mine post to see who uploded the post first. Till then, you may wanna stop being sarcastic.
berezker said:
Basically, looking for attention and thanks.
He has been doing this for every update even though there are other threads that are much better and more organized
He even claimed that he was in the beta program when 8.1 beta was leaked even though he was asking around on where to get beta update.
Rowdy, you should honestly stop making pointless threads that already exist and start being more respectful to other members
Click to expand...
Click to collapse
And talking about attention and thanks, I am not going to be rich by getting a few thanks. You might have joined XDA for thanks, but I don't find any pleasure or point of getting thanks and attention on a software development community. You should think first before attacking someone. You might have forgotten about the "Report" option, but I didn't.
jareddlikewhoaa said:
In his defense. This link is AFH, while still not wonderful, it is usually SOOOO much faster than the damn MIUI links. (at least in my experience)
Click to expand...
Click to collapse
I checked all XDA post prior to posting mine. XDA gives you an option to check all similar posts while you are creating your post. I went to each post and checked if anyone had uploaded the July security patch.
https://forum.xda-developers.com/mi...-ota-links-t3718542/post74828108#post74828108 (I checked his post at first and when I created my post, he didn't have July fastboot ROM uploaded).
https://forum.xda-developers.com/mi-a1/how-to/download-opr1-170623-026-9-5-4-february-t3758090 (This guy gave a headline of July fastboot ROM. But I didn't find V9.6.4.0.ODHMIFE anywhere on his post)
Now, it's not my fault if someone uploaded the July fastboot ROM after I posted it here. I don't know why some people act violently (not you) towards others.
Rowdyy Ronnie said:
Disclaimer:
Your warranty will be void after unlocking the bootloader. You need to lock the bootloader for any warranty.
Click to expand...
Click to collapse
I dont think thats the case with xiaomi.
Thanks for uploading fastboot image.
.:Addicted:. said:
I dont think thats the case with xiaomi.
Thanks for uploading fastboot image.
Click to expand...
Click to collapse
Well, the warranty remains intact only if you use a miui based handset. But since Mi A1 runs on pure AOSP, Xiaomi doesn't provide any warranty after unlocking bootloader (confirmed with Xiaomi customer service).
Rowdyy Ronnie said:
Well, the warranty remains intact only if you use a miui based handset. But since Mi A1 runs on pure AOSP, Xiaomi doesn't provide any warranty after unlocking bootloader (confirmed with Xiaomi customer service).
Click to expand...
Click to collapse
ahh ok. good to know that
i am already rooted on custom rom but i want to flash stock 8.1, do i use mifalsh tool? and does it wipe all the internal data? or use the userdata (like apps etc)
faddys123 said:
i am already rooted on custom rom but i want to flash stock 8.1, do i use mifalsh tool? and does it wipe all the internal data? or use the userdata (like apps etc)
Click to expand...
Click to collapse
Hi, yes you need the MiFlash tool as this is a fastboot ROM. And it is not necessary (but suggested) to wipe the internal storage. You can select your desired option on the MiFlash tool. If you want to keep your apps and data, you can select "Save user data" on MiFlash tool and flash the ROM.
we only need one thread about stock roms. Let's make it easier on everyone and keep all the info in the same thread.
https://forum.xda-developers.com/mi-a1/how-to/mi-a1-monthly-updates-t3750419
https://forum.xda-developers.com/mi-a1/how-to/ota-xiaomi-mi-a1-ota-links-t3718542/
Hey,
youyim123 recently made his TWRP build available that I was trying to compile myself. So without further ado, here is a more or less working TWRP for the Nubia Z18 with instructions of how to install it.
Link to recovery.img
How to install it:
Boot into bootloader using
Code:
adb reboot bootloader
Unlock the bootloader using
Code:
fastboot oem nubia_unlock NUBIA_NX606J
Flash the recovery.img using
Code:
fastboot flash recovery recovery.img
IMPORTANT! Navigate to "reboot to emergency recovery mode". Do not use
Code:
fastboot reboot recovery
as it might not work correctly!
I found disconnecting the device from USB to be more reliable, so do that for stability
If it gets stuck, repeat steps 1 and 4. No need to reflash, just be patient
Language will be Chinese, so change that by using the settings button (second from below on the right)
That's it, you have a working TWRP now Enjoy!
EDIT: DO NOT TRY FLASHING MAGISK AS IT WILL DAMAGE DM-VERITY AND YOU'LL HAVE TO BOOT RESCUE YOUR DEVICE! YOU CAN USE MY recovery script in the bloat remover thread to fix your device
In case you get stuck in a bootloop, repeat the installation guide, then use
Code:
adb push stock.zip /data/media/0
and reflash stock firmware as a last resort until a custom ROM is available.
All credit for this goes to youyim123 and his amazing work! I know he struggled releasing this because his work is often used or redirected without his consent or giving him credit, so I'm grateful he decided to release it.
*reserved*
Can i use this to flash Gapps
aqblwd said:
Can i use this to flash Gapps
Click to expand...
Click to collapse
In theory, yes. In practice, it somehow doesn't give me any GApps when flashing it. I'm trying to cooperate with the OpenGapps team to fix this.
any update info for flashing gapps ? i really want to use my nubia z18 with google environment on it. tks
shevaman7 said:
any update info for flashing gapps ? i really want to use my nubia z18 with google environment on it. tks
Click to expand...
Click to collapse
None yet. I'd say community involvement isn't exactly one of the OpenGapps team's good points
See the Gitter thread for tracking updates here: https://gitter.im/opengapps/general
If you know of any other way to contact them, feel free to do so and send them the logs I attached in the gitter post (same username as here)
shevaman7 said:
any update info for flashing gapps ? i really want to use my nubia z18 with google environment on it. tks
Click to expand...
Click to collapse
You can use google xspace
elnas1369 said:
You can use google xspace
Click to expand...
Click to collapse
EDIT: Okay I tried the app and it's doing something that looks like installing play services? @elnas1369 would you mind explaining what you did in detail? Because most of us probably can't speak chinese and it's not intuitive unfortunately
curtisy said:
EDIT: Okay I tried the app and it's doing something that looks like installing play services? @elnas1369 would you mind explaining what you did in detail? Because most of us probably can't speak chinese and it's not intuitive unfortunately
Click to expand...
Click to collapse
I did it on my Nubia X and it works pretty good, you just have to follow the steps, i've found some tutos on youtube it's very easy. You can search for google xspace installing or something like that
curtisy said:
Hey,
youyim123 recently made his TWRP build available that I was trying to compile myself. So without further ado, here is a more or less working TWRP for the Nubia Z18 with instructions of how to install it.
Link to recovery.img
How to install it:
Boot into bootloader using
Code:
adb reboot bootloader
Unlock the bootloader using
Code:
fastboot oem nubia_unlock NUBIA_NX606J
Flash the recovery.img using
Code:
fastboot flash recovery recovery.img
IMPORTANT! Navigate to "reboot to emergency recovery mode". Do not use
Code:
fastboot reboot recovery
as it might not work correctly!
I found disconnecting the device from USB to be more reliable, so do that for stability
If it gets stuck, repeat steps 1 and 4. No need to reflash, just be patient
Language will be Chinese, so change that by using the settings button (second from below on the right)
That's it, you have a working TWRP now Enjoy!
EDIT: DO NOT TRY FLASHING MAGISK AS IT WILL DAMAGE DM-VERITY AND YOU'LL HAVE TO BOOT RESCUE YOUR DEVICE! YOU CAN USE MY recovery script in the bloat remover thread to fix your device
In case you get stuck in a bootloop, repeat the installation guide, then use
Code:
adb push stock.zip /data/media/0
and reflash stock firmware as a last resort until a custom ROM is available.
All credit for this goes to youyim123 and his amazing work! I know he struggled releasing this because his work is often used or redirected without his consent or giving him credit, so I'm grateful he decided to release it.
Click to expand...
Click to collapse
any news update about stable TWRP for Z18. I have Z18, a very beautiful and strong device
md07 said:
any news update about stable TWRP for Z18. I have Z18, a very beautiful and strong device
Click to expand...
Click to collapse
It is stable. Just make sure to unplug your phone after flashing it as otherwise it will probably get stuck after a few seconds. If you need to have your device connected to your pc, do the following:
Start adb sideload in TWRP, connect your phone to your pc, stop sideload. That way you have a working connection with adb again
Hope this helps!
curtisy said:
It is stable. Just make sure to unplug your phone after flashing it as otherwise it will probably get stuck after a few seconds. If you need to have your device connected to your pc, do the following:
Start adb sideload in TWRP, connect your phone to your pc, stop sideload. That way you have a working connection with adb again
Hope this helps!
Click to expand...
Click to collapse
i read somewhere in Nubia forums (chinese language), some dev is going to release TWRP for Z18, but it need poll to decide.
So that, i dont know this version on XDA is official or unofficial ? And as you said, if it is stable, so can i flash Gaap package to get full Goolge and service for Z18? have you tried ?
Already try few weeks ago, not working...!
The only temperary solution is "Google Space", or just wait for the global version release
As one Dev which working on LOS fot this machine point out that Lineage is very hard to compile since there's no other Dev help him, the System is block by something call AVB2...pretty ironic as this twrp not even let us using Magisk at all!
md07 said:
i read somewhere in Nubia forums (chinese language), some dev is going to release TWRP for Z18, but it need poll to decide.
So that, i dont know this version on XDA is official or unofficial ? And as you said, if it is stable, so can i flash Gaap package to get full Goolge and service for Z18? have you tried ?
Click to expand...
Click to collapse
sky104hk said:
Already try few weeks ago, not working...!
The only temperary solution is "Google Space", or just wait for the global version release
As one Dev which working on LOS fot this machine point out that Lineage is very hard to compile since there's no other Dev help him, the System is block by something call AVB2...pretty ironic as this twrp not even let us using Magisk at all!
Click to expand...
Click to collapse
I tried Gplay space. But all app installed from there seem work slowly and not appear on home screen (must go Gplay space and run app)
md07 said:
i read somewhere in Nubia forums (chinese language), some dev is going to release TWRP for Z18, but it need poll to decide.
So that, i dont know this version on XDA is official or unofficial ? And as you said, if it is stable, so can i flash Gaap package to get full Goolge and service for Z18? have you tried ?
Click to expand...
Click to collapse
Please read the first post precisely and then the post in the nubia forum again. Youyim is the guy who made the poll and he made it public. I simply brought it to a wider audience and link to his official GitHub for the img.
You cannot flash Gapps with this because it errors. I said so a couple of times before and would appreciate a bit of effort reading before asking. You probably spent more time on writing this than you would've reading the first three post entries here, disregarding the fact that I'm trying to reply in detail. It's all in the first post, please read that before asking next time..
To sum up:
- It's the "official" TWRP from youyim, all credit goes to him
- You can not install Gapps with this, I haven't found a resolution for this but am working on an alternative. See my other thread or post #3 here
sky104hk said:
Already try few weeks ago, not working...!
The only temperary solution is "Google Space", or just wait for the global version release
As one Dev which working on LOS fot this machine point out that Lineage is very hard to compile since there's no other Dev help him, the System is block by something call AVB2...pretty ironic as this twrp not even let us using Magisk at all!
Click to expand...
Click to collapse
It's the same dev I'm the guy working on LineageOS as well and yes AVB2 (Basically think of it as Android's answer to secure boot on Computers) is a pain in the a** to deal with. Compiling itself is rather easy compared to the pain that comes after it, it's just killing lots of time and I unfortunately don't have that with a full time job. That's why I tried getting more people involved but (again) failed apparently.
TWRP doesn't have anything to do with Magisk either. Magisk is modifying the boot partition as far as I'm aware (don't hate me topjohnwu) and it relies on either no AVB/DM-Verity or a flag that doesn't work here either. TWRP in contrast just modifies/overrides the boot partition and is (mostly) used to flash many things including Magisk.
I think Z18 not have a global version, so we'll never see international firmware for this product. The only way I hope is some one or some dev support official method for install Google. And hope good news come soon.
Thanks all!
md07 said:
I think Z18 not have a global version, so we'll never see international firmware for this product. The only way I hope is some one or some dev support official method for install Google. And hope good news come soon.
Thanks all!
Click to expand...
Click to collapse
Isn't a global release coming in like 2 weeks or something? At least that's what I read last time I checked
I can tell you an official method. Root your phone and rewrite google services to system. Otherwise wait until developers can take a look at Rom building like I do now or even better, get involved. Being a one man show isn't helping the cause even if you have a couple spectators because it makes you feel more or less like a monkey in a cage
curtisy said:
Isn't a global release coming in like 2 weeks or something? At least that's what I read last time I checked
I can tell you an official method. Root your phone and rewrite google services to system. Otherwise wait until developers can take a look at Rom building like I do now or even better, get involved. Being a one man show isn't helping the cause even if you have a couple spectators because it makes you feel more or less like a monkey in a cage
Click to expand...
Click to collapse
Where did you read about global version Z18??? I checked only on Nubia website, in some global region (like India...) they are only going to release global Red Magic Mars.
I know method get Google and service by rooted and I read in Nubia forums they released tool to root current Version Z18, but I can not download
md07 said:
Where did you read about global version Z18??? I checked only on Nubia website, in some global region (like India...) they are only going to release global Red Magic Mars.
I know method get Google and service by rooted and I read in Nubia forums they released tool to root current Version Z18, but I can not download
Click to expand...
Click to collapse
https://www.gadgetsnow.com/mobile-phones/Nubia-Z18 for instance. India isn't global lol. They mostly just buy masses of phones and then resell. And yeah I can understand they won't release a global version anytime soon. The phone is great but looking at the source code, it's horrible. I even had to submit a patch so they get their build fixed!
As for the download, try the second one. Baidu is blocking anything non China by now afaik. It will also be included in the LineageOS ROM whenever I'll get that done..